A tweetstorm digestion by Alex & Owen.

Why would someone add this banner to their website?!” asks Ada Rose Edwards:

That question spawned a ~40 tweet conversation that some folks asked to see written up here.

Before we get to that, and by way of disclaimer, we don’t have any insight into the specific thinking of the Tumblr team. For all we know they’ve done all the experiments and found the native app a better investment. …

Andrew Betts has called the Progressive Apps pattern “a bag of carrots” and, at some level, he’s right: the notion that something is an App does boil down to UI treatment and providing UI in return for developer effort is something browsers are in the business of doing.

He’s also right that what browsers give users and developers by implementing support for Progressive Apps (like Chrome and Opera have and which Mozilla is considering) is access to this differentiated UI treatment. …

This post is about vendor prefixes, why they didn’t work, and why it’s toxic not to be able to launch experimental features. But mostly this post is about what to do about it. The argument and implications require nuance and long-term thinking. That is to say, despite diligent efforts to clarify and revise, this post is likely to be misunderstood.

Vendor prefixes are a very sore topic, and one where I’ve disagreed with the overwhelming consensus. In the heat of the ‘11–12 debate (a.k.a. “prefixpocalypse”) I tried to outline a rough hierarchy of the web platform’s concerns:


Alex Russell

Dragging the web platform into the mid-naughties, one spec at a time. Progressive Web Apps are my jam.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store