Jeremy, on how he thinks about building progressive web apps:

In my opinion, the term “progressive web app” can be read in order of priority:

1. Progressive—build in a layered way so that anyone can access your content, regardless of what device or browser they’re using, rewarding the more capable browsers with more features.
2. Web—you’re building for the web. Don’t lose sight of that. URLs matter. Accessibility matters. Performance matters.
3. App—sure, borrow what works from native apps if it makes sense for your situation.

He also links to Jason Grigsby’s Designing Responsive Progressive Web Apps which is another great read.

Jeremy throws cold water on Brian’s bookmarklet article I linked to yesterday.

Bookmarklets are not dead. They may, however, be pining for the fjords.

Like Jeremy, I have a simple bookmarklet for saving links to my own site. My bookmarklet opens a new window/tab, passing via URL parameters the URL and title of the current window/tab to a page on my site. If I’ve highlighted some text in the page, the bookmarklet will grab that and insert it into the body field on my link form, prepended with a > (the Markdown syntax for a <blockquote>).

Easy peasy.

Not-so-humorously, that last piece doesn’t work on overly-clever sites like Medium that monkey about with browser-native user interface. Neutral face emoji.

I’ve come to realise that the real power of the web lies in its ubiquity. Just as Tim Berners-Lee first intended, a website can be accessed on any device with any browser as long as there’s some kind of internet connection. That still amazes me. And it continues to break my heart when I see people choose to deliberately ignore that superpower and build sites that only work for a subset of people.

Mr. Keith likes The Orchid and so should you!