Why We Create Progressive Web Apps: A Conversation with Jeremy Keith
This is a really nice write-up by Sydney of the chat we had on her podcast.
Here’s a nice one-sentence definition for the marketing folk:
A Progressive Web App is a regular website following a progressive enhancement strategy to deliver native-like user experiences by using modern Web standards.
But if you’re talking to developers, I implore you to concretely define a Progressive Web App as the combination of HTTPS, a service worker, and a Web App Manifest.
This is a really nice write-up by Sydney of the chat we had on her podcast.
I really enjoyed talking to Sydney Lai about progressive web apps, resilient web design, and all my other hobby horses.
Alas, there’s no transcript and I can’t find a direct link to the RSS feed or the individual audio file on the podcast website so it’s not huffduffable.
There’s a good discussion here (kicked off by Jen) about providing different theme-color values in a web app manifest to match prefers-color-scheme in media queries.
Automatically generates icons and splash screens based on Web App Manifest specs and Apple Human Interface Guidelines. Updates manifest.json and index.html files with the generated images.
A handy command line tool. Though be aware that it will generate the shit-ton of link elements for splash screens that Apple demands you provide for a multitude of different screen sizes.
Here’s the opening keynote I gave at Frontend United in Utrecht a few weeks back.
How I’m letting people know they can install The Session to their home screens.
Browsers are still trying to figure out how to highlight progressive web apps.
How do we let people know what the web can do?
You have nothing to lose but two oversized native apps on your home screen.
Trying to get the balance right between discoverability and intrusiveness.