4 ms·
It's more about bridging the gap between mobile and web. Installable web apps that have as much access to the OS as a native app (through user-initiated consent
by apatheticonion 6y ago
It's more about bridging the gap between mobile and web. Installable web apps that have as much access to the OS as a native app (through user-initiated consent) is a great direction to move towards.
The browser can now run any language through web assembly, threads and all. The HTML/CSS layer is just a portable, expressive markup for visual assets.
I made a fitness goal tracking web app that worked completely offline. If you've used "strong" on android, it's basically a free clone that.
It stored all the records on the browser via indexeddb and the timer would ping you with a push notification when the rest timer would expire.
iOS erases the persisted storage after 7 days and doesn't let me use push notifications. I'd love it if iOS asked "hey this web app wants to store data long term" or whatever, but it doesn't.
- Leherenn 6y agoOr even just have an option somewhere you can manually toggle per site, to avoid the issue of being bombarded by permission requests.
- easton 6y agoI would be down with this if apps aren't allowed to ask for notification permissions until the user adds it to the home screen, the same way that game controller and full screen work now. Therefore the user consented for it to "become an app".