The Website vs. Web App Dichotomy Doesn’t Exist | jakelazaroff.com
If there’s one takeaway from all this, it’s that the web is a flexible medium where any number of technologies can be combined in all sorts of interesting ways.
The web on mobile (a response) | Clagnut by Richard Rutter
Rich suggests another reason why the UX of websites on mobile is so shit these days:
The path to installing a native app is well trodden. We search the App Store (or ironically follow a link from a website), hit ‘Get’ and the app is downloaded to our phone’s home screen, ready to use any time with a simple tap.
A PWA can also live on your home screen, nicely indistinguishable from a native app. But the journey to getting a PWA – or indeed any web app – onto your home screen remains convoluted to say the least. This is the lack of equivalence I’m driving at. I wonder if the mobile web experience would suck as badly if web apps could be installed just as easily as native apps?
Related links
Web Apps on macOS Sonoma 14 Beta
It’s great to see how (progressive) web apps are being supported on both iOS and macOS …I just wish the discovery were better.
In Defence of the Single Page Application | William Kennedy
This is very convincing.
Why Safari does not need any protection from Chromium – Niels Leenheer
Safari is very opinionated about which features they will support and which they won’t. And that is fine for their browser. But I don’t want the Safari team to choose for all browsers on the iOS platform.
A terrific piece from Niels pushing back on the ridiculous assertion that Apple’s ban on rival rendering engines in iOS is somehow a noble battle against a monopoly (rather than the abuse of monopoly power it actually is). If there were any truth to the idea that Apple’s browser ban is the only thing stopping everyone from switching to Chrome, then nobody would be using Safari on MacOS where users are free to choose whichever rendering engine they want.
The Safari team is capable enough not to let their browser become irrelevant. And Apple has enough money to support the Safari team to take on other browsers. It does not need some artificial App Store rule to protect it from the competition.
WebKit-only proponents are worried about losing control and Google becoming too powerful. And they feel preventing Google from controlling the web is more important than giving more power to users. They believe they are protecting users against themselves. But that is misguided.
Users need to be in control because if you take power away from users, you are creating the future you want to prevent, where one company sets the rules for everybody else. It is just somebody else who is pulling the strings.
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.
Related posts
Going Offline is online …for free
Read the book I wrote about service workers. It’s all yours.
Space dock
A bug report for Safari on Mac’s add-to-dock feature.
Read-only web apps
It’s fine to require JavaScript for read/write functionality. But have you considered a read-only mode without JavaScript?
The principle of most availability
Reframing the principle of least power.
Progressive web app store
I’ve got a business proposition for you.