bubblewrap VS Nuxt.js

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.

According to Node Package Manager (NPM), Next.js has about 3.9 million weekly downloads while Nuxt.js has about 438,000. Although Next.js has a significantly higher number of weekly downloads, Nuxt.js still has a robust number of users. We can conclude that both frameworks are relevant and will stand the test of time.

Nuxt team themselves pointed that out [in first release](https://www.npmjs.com/package/nuxt/v/0.0.1) as well as you can see that statement in [Nuxt's wikipedia article](https://cdn.domin.pro/K2Qa). I completely agree with how Nuxt is better for an amount of features.

Node is basically back-end Javascript. While powerful alone, almost exclusively you will use a back-end framework like Next.js or Gatsby when using React, and then maybe Nuxt or Gridsome in Vue.

Both Vue.js and React have their own set of tools and libraries to help developers build and maintain their applications. Vue.js has Vue CLI and Nuxt.js, while React has Create React App and Next.js.

Nuxt.js is a free and open-source JavaScript framework based on Vue.js that helps you develop modern web applications using SSR (server-side rendering) which provides a faster load, better SEO (search engine optimization), and better caching capabilities.

We made a LiveChat Next.js App template. Using Next.js as a foundation for the project, we have a front-end app with built-in routing, Server Side Rendering (SSR), and Server Side Generation (SSG) built with React, but on top of that, ready-to-use API routes built in the form of Serverless functions. If you prefer Vue.js or Svelte, you can choose similar frameworks, like Nuxt.js and SvelteKit.

Not oc, but maybe give Nuxt a look?

Vue's docs are some of the best I've ever read. Nuxt and Craft are pretty great too. I especially like how Craft's docs are bifurcated into the docs which give you the 20/80 + code snippets, and the class reference, which is complete documentation of every method, type, param, etc of the platform.

Nuxt - the Vue alternative to NextJS - supports both static site generation and SSR.