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
-
When you build with desktop-era frameworks, to desktop resource limits, only occasionally (if ever) marking your experience to the market reality of the median or P90 device, you lay down a structurally broken experience, one brick at a time.
3 replies 0 retweets 9 likesShow this thread -
Browser DevTools (including Chrome's) don't do nearly enough to highlight how bad the situation really is, and how deeply unrepresentative the developer devices are, even when "emulating" slower CPUs & Networks.
4 replies 2 retweets 9 likesShow this thread -
Ground truth is a $100-200 Android, attached over USB via chrome://inspect, or automated via
@patmeenan's genius http://webpagetest.org/easy Anything else is just lying to yourself.5 replies 0 retweets 22 likesShow this thread
Free idea: there should be a service like BrowserStack that builds a DevTools extension that lets you subscribe to see/experience your dev environment on real hardware by default. Opening DevTools should never reflect your local device capabilities by default.
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.