The problem is that nobody really does "mobile-first". ~everybody designs/builds on desktop, and few know about or use chrome://inspect as they core of their workflow: https://developers.google.com/web/tools/chrome-devtools/remote-debugging …https://twitter.com/adactio/status/1180144204871327744 …
-
Show this thread
-
Replying to @slightlylate
Was thinking about this after your talk. One thing that would be AMAZINGLY helpful is if the Chrome DevTools shipped with a Median Device Mode, which opened the page in Chrome on a median Android device w a median data connection in a dc somewhere (tunneling to localhost).
2 replies 0 retweets 1 like -
Replying to @rakshesha
This would be great! Years ago, I asked DevTools team for this, and if not possible, enabling existing (low-fidelity) CPU and network throttling when a device is selected to emulate. Was told "no" so often I stopped asking. /cc
@paul_irish@aerotwist@expatdanno@dalmaer1 reply 0 retweets 3 likes -
Replying to @slightlylate @paul_irish and
It doesn't HAVE to be built in to DevTools, the big cost is the infra and support. Peanuts, really, and the alternative is… letting Search die. It seems categorically insane to me that G would do that, but perhaps the right folks aren't thinking about it in those terms.1 reply 0 retweets 1 like
The good news is that Chromium now powers the crawl (which means we can drop "SSR" and framework bloat), and speed as a ranking factor (driven by real-world perf data) has changed some behaviour. But not enough. Not nearly enough:https://webmasters.googleblog.com/2018/01/using-page-speed-in-mobile-search.html?m=1 …
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.