You check your new landing page on your laptop. Big screen, fast wifi, a mouse. It looks great. Then a customer opens it on a phone, on a train, with a thumb. This is a short routine for checking the phone version before you send a campaign.
What changes on a phone
Six things are different:
- The screen is small.
- People tap instead of click.
- The on-screen keyboard covers part of the page.
- The network is slower.
- The processor is slower.
- An iPhone runs Safari, which is a different browser from Chrome.
Test on a real phone first
The cheapest test is a real phone with the live site open. Turn wifi off and use mobile data, because that is what many customers have. Then do the one job the page exists for: fill the form, book the slot, place the order. If you can borrow both an iPhone and an Android phone, use both.
The usual suspects
The viewport tag. Without a viewport tag, a mobile browser draws your page at a desktop width, usually about 980 pixels, and shrinks it to fit. The text comes out tiny and people have to pinch to read it. The recommended tag is <meta name="viewport" content="width=device-width, initial-scale=1">.
Button size. The WCAG 2.2 guideline for target size says tap targets should be at least 24 by 24 CSS pixels, with some exceptions for spacing. Bigger is easier to hit.
Form fields. An email field should bring up the email keyboard and a phone field should bring up number keys. The inputmode attribute lets the browser show the right keyboard, and autocomplete hints let the phone fill in a name or address. inputmode does not validate anything. It only changes the keyboard.
Device mode is not a phone
You do not always need a phone in your hand. Chrome DevTools has a device mode that resizes the window, acts like a touch screen, and can slow the network and processor. Chrome's own documentation calls it a first-order approximation: your page is not running on a phone. Tools that emulate devices with the WebKit engine, such as Playwright, are close to Safari but are not Safari itself.
Which check to use
- A spacing tweak or a new banner: device mode is enough.
- A form, a checkout, or a booking page: finish it on a real phone before you send the campaign.
Where DebuggAI fits
DebuggAI is not a phone. You describe a check in plain language, such as "open the booking page and book a slot", and a browser agent runs it on your live page, using Chrome on your own machine or a cloud browser. It reports back with the result. Use it after each change to confirm the whole journey still finishes, and keep the real phone for the last look.
One question
Which three pages make you money, and when did you last finish each one on a phone?
Sources
- web.dev, "Responsive web design basics": https://web.dev/articles/responsive-web-design-basics
- W3C, "Understanding Success Criterion 2.5.8: Target Size (Minimum)": https://www.w3.org/WAI/WCAG22/Understanding/target-size-minimum.html
- MDN,
inputmode: https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Global_attributes/inputmode - MDN,
autocomplete: https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Attributes/autocomplete - Chrome DevTools, "Simulate mobile devices with device mode": https://developer.chrome.com/docs/devtools/device-mode
- Playwright, "Emulation": https://playwright.dev/docs/emulation
