If you've ever built a website for mobile but never heard of PWAs (Progressive Web Apps), I recommend checking them out. In essence, adding 2 files can make the

If you've ever built a website for mobile but never heard of PWAs (Progressive Web Apps), I recommend checking them out. In essence, adding 2 files can make the site installable from a mobile browser and define caching behavior for offline functionality. 1. manifest.json: a JSON file that defines the app's name, icons, theme colors, and how it should launch when installed. 2. Service worker: a JS file that controls things like resource caching for offline usage Unfortunately PWAs don't receive first class support compared to native apps. Still, I still hope to see wider adoption. I think for many not-too-complex apps, they can significantly lower the cost of development, and the development experience could be as simple as - Building with HTML + JS + CSS. No clunky SDKs, reduced need to test on painfully slow emulators or expensive physical devices - Installable from a browser. No need to maintain a listing in the Playstore/App Store, avoiding policy headaches, rent, etc. https://developer.mozilla.org/en-US/docs/Web/Progressive_web_apps/Tutorials/CycleTracker https://developer.mozilla.org/en-US/docs/Web/Progressive_web...