It feels like since a bunch of new stuff has come out, people forget that we were building fast web apps that worked offline, even in Safari, for years. Like history’s been erased and all the effort we expended a decade ago to make a fast web was worthless.
-
-
I don’t mean to trivialize the newer efforts on PWAs, but at the same time I don’t think it’s a good idea to ignore the past.
1 reply 0 retweets 1 like -
-
Replying to @kennethrohde @jamesuriah
The front-end developer community at large seems to be under the impression that a PWA without a SW, manifest, etc isn't a PWA. The reason I responded was because it came across as aligning with that view.
1 reply 0 retweets 0 likes -
Replying to @jamie_gaskins @jamesuriah
PWA is basically a marketing term and it works well for that, just like HTML5 was and people associated a lot more with it then the HTML5 spec, like CSS3 specs, geolocation etc etc. It worked well for getting people to adopt web tech at that point, and the same goes for PWA today
1 reply 0 retweets 1 like -
Replying to @kennethrohde @jamesuriah
This is not the same situation, though. HTML5 was seen as the next iteration of the web: - HTML was synonymous to the web for a lot of people, even web devs, who primarily mutated the DOM by setting innerHTML - it included a version number
1 reply 0 retweets 0 likes -
The fact that the term PWA is understood as being a particular set of implementation details (SW, manifest, etc) instead of having a particular set of qualities (as originally defined) signals that no SW indicates "not progressive".
2 replies 0 retweets 0 likes -
Replying to @jamie_gaskins @jamesuriah
A lot of people associate "add to home screen/install" experiences with PWA, which is even what Chrome
@____lighthouse is looking at when rating the PWA score. In order to be considered able to "install/add to homescreen" in Chrome or the Microsoft Store (soon) you need to follow1 reply 0 retweets 0 likes -
Replying to @kennethrohde @jamie_gaskins and
a certain set of criteria, like have some sort of offline experience, having certain values set in the manifest. You can say that is not progressive, but sites living up to these criteria can work fine without serviceworker and manifest, so they are progressive cc/
@slightlylate1 reply 0 retweets 1 like -
Replying to @kennethrohde @jamie_gaskins and
meaning, they work fine in browsers not supporting these technologies.
1 reply 0 retweets 1 like
There are some core problems with the tech that Safari (and Chrome) had previously shipped. The result was experiences that couldn't really compete: https://infrequently.org/2016/05/service-workers-and-pwas-its-about-reliable-performance-not-offline/ …
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.