honestly, if I were seriously targeting mobile for anything heavy duty, I'm inclined to lean on native mobile, not the web.
-
-
Replying to @BenLesh
: yep. Lots of folks have made this call and many are failing (at a business level). But at least their tech works on these devices.
2 replies 0 retweets 4 likes -
Replying to @slightlylate
I'm not sure it's as lop-sided or black and white as what you're portraying.
2 replies 0 retweets 0 likes -
Replying to @BenLesh @slightlylate
I mean, I'm sure Netflix would love to "write once and deploy everywhere" but it's currently not practical for everything.
1 reply 0 retweets 3 likes -
Replying to @BenLesh
: right. And Netflix is unique in a lot of ways (already market leader, strong BD & big team).
1 reply 0 retweets 4 likes -
Replying to @slightlylate
: I actually think this contributes to the Silicon Valley blindspot about the web.
2 replies 0 retweets 2 likes -
Replying to @slightlylate
sort of. Netflix does have web-based UIs that are running on under powered hardware on third-world networks. It's a concern
2 replies 0 retweets 1 like -
Replying to @BenLesh @slightlylate
and when I say underpowered, I mean that every phone you talked about is probably orders of magnitude faster. Haha. It's crazy
2 replies 0 retweets 1 like -
Replying to @BenLesh
: this one is my "make 'em cry" device:pic.twitter.com/53IOAUK3pH
1 reply 0 retweets 2 likes -
Replying to @slightlylate
: '14 Android One; 2 cores (lawlz slow), 512MB RAM, w/ a GPU-ish-sorta-kinda. And we regularly see slower in-market.
2 replies 0 retweets 3 likes
: I show folks this using the internal (throttled) 2G-representative EM wifi network and they don't know what to say.
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.