I expect Mark Zuckerberg to be an absentee landlord of a growing empire...that's capitalism. But where's @cbeard or @MitchellBaker?
The future is mobile. Where-the-AF-are-you, @mozilla? We need you in this fight.
-
Show this thread
-
There will be all the "you've drunk the Google kook-aid" flack on this thread. Nerp. I work places that have serious, legitimate plans to make the web something other than a desktop-only, legacy-centric OS. So I work on
@googlechrome.7 replies 0 retweets 12 likesShow this thread -
Replying to @slightlylate @googlechrome
I like to think we have a lean, mean engine here in WebKit. Actually the most lean-n-mean.
Do your frustrations apply to us too or is this Mozilla-specific? Have I missed some context? Are we talking evangelism or engine work here?1 reply 0 retweets 5 likes -
Replying to @johnwilander @googlechrome
I like me some modern
@webkit! More of that, less of the other ;-)1 reply 0 retweets 1 like -
OK, we’ll focus on modern rather than legacy then. But let’s talk mobile web in emerging markets. I get the push for offline and more device APIs. But where are we on: 1) Power consumption? 2) Data consumption? 3) Safety of non-curated apps? 4) UI consistency? 5) Accessibility?
2 replies 0 retweets 2 likes -
Power: hard (both to measure and control). Data: web often the winner; PWAs are frequently a (tiny) fraction the size. Safety: web sandbox beats unlatched Android! Consistency: it's an open platform. a11y: not as good
1 reply 0 retweets 0 likes -
Power: Hard problems need love too. Could we come up with something? Data: If we could agree on incentives we could probably shave it down significantly. Safety: I don’t know enough about Android curation. Especially not outside Google Play Store.
3 replies 0 retweets 0 likes -
On Data, we're looking at incentives. I've often advocated for a "slow script warning", but for heavy content (coupled to the Reporting API). Search moving to real-world speed rankings will also help: https://webmasters.googleblog.com/2018/01/using-page-speed-in-mobile-search.html …
2 replies 0 retweets 1 like -
Replying to @slightlylate @johnwilander and
But for experiences that users engage with frequently, the web (and PWAs specifically) are often *hugely* better: https://developers.google.com/web/showcase/2017/twitter …
1 reply 0 retweets 0 likes -
Replying to @slightlylate @johnwilander and
Data-sensitivity, BTW, is what causes people to side-load apps (which undermines security). Native app platforms fail to serve these users well as a result.
1 reply 0 retweets 0 likes
Android users in EM can frequently side-load bloated native apps; but only to a point. Low-end devices have very little storage. The web's design creates subtle (but effective) pressure to do better.
-
-
Replying to @slightlylate @johnwilander and
iOS has always been for rich users (for whom the network is cheap); even when I got my first iPhone, the unlimited data cap signaled that the ecosystem wasn't for people who couldn't afford data. That has played out predictably: https://blog.timac.org/2017/0410-analysis-of-the-facebook-app-for-ios-v-87-0/ …
0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.