Every browser has a device mode. Open DevTools, pick "iPhone" from a dropdown, and the page shrinks to phone size. It's quick, it's free, and it catches a lot of layout problems.
It also misses a lot. Device mode changes the size of the page. It doesn't change the browser, the keyboard, the touch screen, or the network. Plenty of mobile bugs live in exactly those gaps.
What device mode gets right
To be fair, it's good at:
- Catching layouts that break at narrow widths.
- Checking that your mobile menu appears at the right breakpoint.
- Spotting text that overflows or images that don't scale.
Use it constantly while building. Just don't treat it as the final check.
What it misses
The on-screen keyboard. On a real phone, tapping a field brings up a keyboard that covers half the screen. Submit buttons, error messages, and fixed footers end up hidden behind it. Device mode has no keyboard.
The real browser engine. In Chrome's device mode, an "iPhone" is still Chrome. Real iPhones use Safari's engine for every browser, and it handles some things differently: date pickers, video autoplay, certain CSS features, and how the page height changes when the address bar hides.
Touch, not clicks. Hover menus that work with a mouse may need two taps or not open at all on touch. Small tap targets that are easy to hit with a cursor are frustrating with a thumb.
Viewport height surprises. On phones, the visible height changes as the browser bars appear and disappear. Full-height sections and fixed elements can jump or get cut off in ways device mode doesn't reproduce.
Real performance. Your laptop is much faster than a mid-range phone. Animations that feel smooth on desktop can stutter, and heavy pages can take noticeably longer to become usable.
Autofill and paste. Phones autofill names, emails, and one-time codes differently. Forms that validate on every keystroke sometimes break when a whole value arrives at once.
A quick real-device routine
You don't need a device lab. Most teams can cover the important cases with two phones:
- One iPhone with Safari.
- One Android phone with Chrome, ideally not the newest model.
Then, for each important page:
- Load it fresh, not from a link you've already opened.
- Scroll the whole page slowly, then quickly.
- Open and close the menu.
- Fill out any form, including tapping into each field.
- Rotate once.
Ten minutes on two phones will find bugs that hours in device mode won't.
Let your users test the rest
You'll never own every phone your visitors use. That's fine, as long as the people who hit mobile bugs can tell you about them easily.
A feedback widget that works well on touch screens turns every visitor into a tester for their own device. When someone on an older Android phone taps a dot on a broken button, the report includes their exact device, browser, and screen size, so you can see the bug's conditions even if you can't hold the phone.
Next Wednesday: how to read console errors when you're not a developer.