Think of your shopping cart as something that would benefit from having a URI because you can send your spouse a link to it
2
1
@markusvoelter @stevevinoski @pavlobaron Might be old news to you, but I just discovered and like “Magnolia” by “The Pineapple Thief”
1
“[Twitter’s] longstanding inability and/or refusal to deal with trolls and harassment is sinking the company” daringfireball.net/linked/20…
4
3
Recommended, as always: @adactio's take on the PE/offline debate adactio.com/journal/11354
3
7
"Web development has two flavors of graceful degradation" – good post. I disagree with almost everything it says :) seldo.com/weblog/2016/10/14/…
4
1
16
Großes Kino: „Darf das Fernsehen elementare Rechtsfragen solange verdrehen, bis ein Film daraus wird?“ zeit.de/gesellschaft/zeitges…
7
7
+1: “Just because this isn't an issue of inaccessibility that doesn't make it OK” scottohara.me/article/is-it-… (via @DesignedByBlind)
1
3
Finally: To like server-side HTML does not at all mean you don’t like JS as the way to extend it for greatly increased usability 8/8
2
2
11
But don’t claim people who advocate for classic, fast, small, minimal, universally accessible apps that work on any device hurt users 7/
1
4
And if you have a good use case for offline support in your web app, by all means add it, progressively. The acronym “PWA” is a good hint 6/
3
If I’m just an occasional user of your web app, I don’t want to pay for offline support by being punished for a simple one-time access 5/
3
While you might have good reasons to support offline use cases, these are typically not the default for web apps 4/
2
Surprise, surprise: The thing your browser can render faster than anything else is good old-fashioned HTML 3/
1
10
Note that only very few of your web app’s users are writing an app themselves and want to consume your API – most will use a browser 2/
1
3
Here’s an idea: Build a fast web app, i.e. one where the actual *content* your users are interested in is the most important thing 1/
2
6
