PWA isn’t as bad as electron but it’s similar. No local storage or offline capability - which is fine for a weather app, but not fine for something with persistent data like email or chat or a word processor. My computer has loaded up an entire GUI, with local storage and RAM, make use of it in an intelligent way instead of just loading a browser instance and assuming I don’t mind latency.
PWA is 100% better than an “App” that’s just a data collection unit showing the website. Which is all too common too.
PWAs can do both of these. In fact, the definition of a PWA includes that it has some functionality offline. (Though this criteria can be met by serving a simple “sorry, you’re offline right now” page. So long as it isn’t the browser’s default “no connection” error.)
PWA isn’t as bad as electron but it’s similar. No local storage or offline capability - which is fine for a weather app, but not fine for something with persistent data like email or chat or a word processor. My computer has loaded up an entire GUI, with local storage and RAM, make use of it in an intelligent way instead of just loading a browser instance and assuming I don’t mind latency.
PWA is 100% better than an “App” that’s just a data collection unit showing the website. Which is all too common too.
PWAs can use local storage and they can have service workers, which allows them to run offline, at least in theory.
Yeah, this is 100% wrong. They definitely can use local storage and have offline capabilities.
They even have an object store: https://developer.mozilla.org/en-US/docs/Web/API/IndexedDB_API
PWAs can do both of these. In fact, the definition of a PWA includes that it has some functionality offline. (Though this criteria can be met by serving a simple “sorry, you’re offline right now” page. So long as it isn’t the browser’s default “no connection” error.)
Okay I think I get it. Yeah the PWA I save are usually websites I frequent but don’t want to install their app.