bubblewrap VS SvelteKit

I think it's not correct to conflate the App Store and the Play Store like this. Apple is very hostile to PWAs in the App Store, whereas Google wrote a tool to easily package your PWA for the Play Store https://github.com/GoogleChromeLabs/bubblewrap

So for me, I publish to the Play Store to get some free users who find my app that way. App Store, not worth the headache of trying to skirt Apple's rules.

Ideally I think app stores should allow listing PWAs directly, rather than banning them (like Apple) or forcing them to use a wrapper (like Google). Whatever complaints people have about that (app can change without review, etc) also apply to the current situation in the Play Store. Once your wrapper PWA is accepted, you can change the website however you want. So what's the point of the wrapper?

After some research, I felt fairly confident going into the Google Play review process. Google Play makes PWA a first class member and they even offer bubblewrap to help you convert your PWA into an app you can submit. I also read that people had success with using PWABuilder for their apps (which uses bubblewrap internally). I figured my Capacitor app would have a decent chance to pass.

Of course, it doesn't use any native framework, it's a pure Progressive Web App (PWA) wrapped as Trusted Web Activity. The advantage with this is you do not need to bundle it every time there is an update, you just deploy it to the PlayStore once and then it stays up-to-date with the web app automatically. You also do not need to worry about users using old versions, aka. your backend needs to handle only the latest version. I used bubblewrap for the bundling, but there is also a GUI from Microsoft called PWA Builder.

The Django backend is not packaged, it just exposes an API to sync and process data, only the Nuxt frontend is packaged. It is more or less straight forward and works out of the box with the nuxt/pwa package for PWA and bubblewrap or PWA Builder for TWA.

If you don't like PWA Builder I'd look at Bubblewrap it's made by Google to make an Android app out of a PWA.

Another inexpensive way of getting an app is by creating a PWA and building an app by using tools like https://github.com/GoogleChromeLabs/bubblewrap

Progressive Web Apps (PWAs) are great and you can even publish them — with limitations — to most of the app stores out there via tools like bubblewrap or PWA Builder. See also Trusted Web Activities (TWAs) and my previous post Publishing a Progressive Web App (PWA) on the PlayStore — What works and what doesn’t (in 2021).

I directly used bubblewrap, but it's the same thing which PWABuilder.com use too.

Svelte Kit for the fullstack framework It has first class support for Cloudflare Pages Svelte is a very elegant framework, and Svelte Kit is a very good meta-framework for Svelte. Svelte was probably the reason that…

This AI-powered Story Card Maker is built as a SvelteKit application with Typescript. Using Flowbite Svelte component library, the whole application was laid out. The layout for the Story Card (emulating the size of a postcard - 4" x 3") is created as an HTML Canvas using Fabric.js.

Svelte kit

These adapters, for example, were built by the community: https://github.com/sveltejs/kit/tree/master/packages/adapter-vercel https://github.com/nuxt/vercel-builder If somebody builds a working one for Angular Universal, we will gladly add it to our Framework Presets → https://vercel.com/docs/concepts/deployments/build-step#framework-preset.

UPDATE: If you liked this project and are curious to see what it might look like as a SvelteKit app, check out this blog post by Tim Smith where he converts this existing app over.

I've played around with several platforms in the last year or so. I've landed on the following setup that works very well for me and ticks all your boxes:

A SvelteKit[0] app hosted on Cloudflare pages. The repo is hosted on GitHub and hooked up to the Cloudflare Pages app [1]. On PRs, I get preview environments. On merge, the changes get deployed to my "production" website. I write blog posts and other content in markdown, which is then processed by mdsvex[2] with very minimal setup.

Mostly, my requirements were more focused around getting the actual framework, hosting, etc. out of my way so that I could focus on writing. Gatsby and Next.js were too configuration heavy and turned me off once I scratched beyond the surface.

[0] https://kit.svelte.dev/

Behind the scenes is a simple Sveltekit-powered server function to fetch a Spotify client token then find a user's recommendation playlist and its track information. A Deno edge function to performs this data fetch and renders server-side Svelte.

It’s 2024, and you are about to start a new project. Do you reach for React, a framework you know and love or do you look at one of the other hot new frameworks like Astro, Enhance, 11ty, SvelteKit or gasp, plain vanilla Web Components?

From part 0 to part 4, we built out CryptoFlow's backend service. Though we can quickly use Postman, VS Code's ThunderClient or automated tests to see the endpoints working easily, this isn't all we want. We want to actively interact with the backend service via some intuitive user interface. Also, a layman wouldn't be able to "consume" the service we've built in the last parts. This article introduces building out the user interface of the system. We will be using SvelteKit, a framework that streamlines web development, and TailwindCSS, the utility-first CSS framework. Let's dig in!