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 …
-
-
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.
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
The fact that we broke chrome://inspect in Chrome 77 and I didn't immediately get inundated with bug reports is telling.
-
Why doesn't Google make a nice/professional looking web page test and have it integrated in devtools?
End of conversation
New conversation -
-
-
Speaking of low-powered devices: Which one would you recommend to test on?
- 1 more reply
New conversation -
-
-
added page to bookmarks
I thought you talk was incredible! Even though it was a bit depressing for someone who is just starting out, thanks for that
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Which is a better test case - a recent model cheap one, or an older second hand one at that kind of price point?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.