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.
An unhandled 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.
I hate that using SSH & 2-factor auth means I have to auth even for for a git pull. But there’s an easier way! Change the remote used for fetch to the HTTPS url. First, verify that both push/fetch are using SSH by running git remote -v it should output something like: origin git@github.com:petele/squoosh.git (fetch)origin git@github.com:petele/squoosh.git (push) Then use git remote set-url origin to set the remote URL for fetch to the HTTPS url. Your repo will now push via SSH and pull via...
Reading is critical to my mental health. Ever since I was a kid, I read, at least a little bit before I fall asleep. In fact, it’s almost a trained behavior now. If I start reading during the day, I get sleepy! What I like about reading is that it gives me an opportunity to stop thinking about the day, put all of that aside and focus on something else. Almost like “parking” my brain for the evening. I want a good book, not a great book. It needs to be something I enjoy, but easy enough to put down. If...