So you want to make a website in 2016... Step 1: buy an unlocked mid-tier android Step 2: chrome:inspect + USB Beware desktop devtools
-
-
Replying to @slightlylate
The devices I carry with me stretch from "low end 2 years ago" to "mid tier last year". Amazing how real hardware defeats your assumptions.
2 replies 1 retweet 8 likes -
Replying to @slightlylate
Even these are probably too rosy; networks hate you (also, *everyone*), devices throttle thermally, and real-world is more memory contended
1 reply 3 retweets 6 likes -
Replying to @slightlylate
One thing while I'm at it: what the heck are Android OEMs *doing*? Too many pixels, not enough L2/L3, big.LITTLE is a practical joke.
2 replies 2 retweets 4 likes -
Replying to @slightlylate
Phones need to be in balance. Other sorts of computers can get away with (some) spec chasing, but phones can't.
1 reply 3 retweets 3 likes -
Replying to @slightlylate
The industry needs an "effective MIPS per pixel" measurement that takes into account dark silicon. Headline #'s are screwing users.
1 reply 3 retweets 6 likes -
Replying to @slightlylate
This number should not allow the OEM/SOC vendor to take credit for transistors that shut down 2 minutes after using a phone heavily
3 replies 2 retweets 2 likes -
Replying to @slightlylate
@fakebaldur Android N will have "sustained performance mode." Could ask reviewers to include that mode benchmarked1 reply 0 retweets 2 likes -
although the top number is also valid, much of what we do is bursty.
1 reply 0 retweets 0 likes
: even if that's true, it's unreliable. No dev or user can count on it, and the cliff face is steep.
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.