I recently had to create a new Raspberry Pi image, and thankfully you can now do it without the need to ever plug the Pi into a keyboard or monitor!
Do you want to serve a localized experience for your Progressive Web App (PWA) depending on the users language?
Unfortunately today, there’s no built in mechanism for localizing your web app manifest. There’s some work being done in the spec, but it hasn’t landed in any browser yet. But, it’s possible to do with a little server side code.
Are PWA users more engaged than browser-tab users? Do they convert more? Spend more time on site? How can you tell the difference between users who opened your PWA up via the launcher (standalone/installed users) vs users in a browser tab? Great question! The easiest way to do it is by using a dimension to track standalone vs browser.
QuotaExceededError when writing to IndexedDB or the Cache
Storage API can cause user data loss. That’s why it’s critical to
handle them properly. But,
because modern computers typically have large hard drives, exceeding your
quota can be hard to test.