,
5 tweets,
2 min read
Read on Twitter
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:
developers.google.com/web/tools/chro…
~everybody designs/builds on desktop, and few know about or use chrome://inspect as they core of their workflow:
developers.google.com/web/tools/chro…
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.
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.
Ground truth is a $100-200 Android, attached over USB via chrome://inspect, or automated via @patmeenan's genius webpagetest.org/easy
Anything else is just lying to yourself.
Anything else is just lying to yourself.
@patmeenan 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.
