pwa-module VS i18n

My go-to is https://pwa.nuxtjs.org/ + pwabuilder. You can have the barebones scaffolding made in 1 minute. Then just add your custom UI/logic, and deploy, and point the PWA Builder at the deployed Nuxt site, and it will generate your App store package.

In terms of stack I would recommend taking a look at Vue and Nuxt. There is a PWA module for Nuxt, which handles everything for you, so you literally only need to add 5 lines of config (implementing service workers yourself can be tedious).

Note that if your original project is built with Nuxt (a Vue meta-framework), you have a better-suited solution readily available in the Nuxt PWA module. Nuxt and its ecosystem of plugins are a bit much to tackle in the scope of this post, but the same PWA general principles we’ll cover here apply there, too. The difference is how the config options are entered. So, while the concepts translate, if you’re using Nuxt, I’ll refer you to the Nuxt PWA module docs for the details.

Documentation

The stack behind Journalistic is Django and Nuxt. The nuxt/pwa module takes care of everything PWA-related on the app side: manifest, service worker, etc. Easy peasy.

It's Nuxt.js with @nuxtjs/pwa, BTW.

Nuxt.js modules: Progressive Web App (PWA)

For more, check out https://i18n.nuxtjs.org/

There is Nuxt 3 i18n - https://v8.i18n.nuxtjs.org/

GitHub repo

hostname (string) If you define the hostname, it will be overridden for all the routes, regardless of the application domain. Module logic is that if the hostname is not defined, the application checks if the current request is HTTPS or not, and gets the current application domain. Then, the module builds a hostname based on that. If you use nuxt-i18n and your app has several domains, the module should clearly define the current application based on the requesting domain.