3 ms·
This seems rather pointless given HTLM5 ServiceWorkers. All of the benefits they're claiming with respect to local prefetching content for offline, instant use
by cromwellian 11y ago
This seems rather pointless given HTLM5 ServiceWorkers. All of the benefits they're claiming with respect to local prefetching content for offline, instant use can be done with that spec. Even push-message content updates when the mobile browser isn't even running can be achieved. The only missing component is IOS support which might be possible to polyfill in via a hybrid.
I'm pretty sure Facebook knows about this, it seems like a platform lockin play.
- emodendroket 11y agoAbsolutely nobody is avoiding reading articles because they take too long to load but they have to have some sort of positive way of describing it.
- wf 11y agoWhat? In my experience this has always been true on mobile. If something takes longer than a few seconds to load it gets closed or restarted.
- emodendroket 11y agoHow many news articles take longer than a few seconds to load?
- prezjordan 11y agoMany.
- ascagnel_ 11y agoThrough Facebook's in-app browser? Most. And you must at least start the load in the in-app browser to get the option to open it in the device's native browser.
- ovulator 11y agoSome people may be on mobile devices, but obviously it isn't the articles that is taking to long to load. It is the layers and layers of blocking JavaScript used for tracking and serving up ads that are taking forever to load.
- emodendroket 11y agoI think Slate is the most egregious offender there.