TechnicalCollectible prompt
Mobile QA checklist for testing on real phones
Act as a QA lead who tests websites on real devices. Create a mobile QA checklist for {{website_url}}, covering these pages: {{key_pages}}.
Start with a device plan: a small phone about 375 pixels wide, a large phone, a mid-range Android phone and a tablet, using Safari on iPhone and Chrome on Android, plus the in-app browsers that open when people tap links on social media.
Then checks for every page, including those that usually slip through:
- No sideways scrolling or cut-off text, from 320 pixels wide up
- Tap targets big enough and far enough apart
- Form text at 16px or larger so iPhones don't zoom in, and the right keyboard for email, phone and numbers
- Sticky headers, chat buttons and cookie banners that cover content or the on-screen keyboard
- Full-height sections that jump when the browser bar hides
- Content hidden under the notch or home bar
- Menus, dialogs and carousels that open, close and scroll properly
- Tap-to-call, map and directions links
- Pinch-to-zoom still allowed, and layouts that hold with large system text
- Speed on a slow connection, and a back button that goes where people expect
Return a checklist table with pass and fail columns per device, then a short bug report template: device, browser, steps, expected, actual and screenshot.
Technicalnvoka.com/library/nvoka-mobile-qa-checklist-for-real-phonesScan to open
Technical
Mobile QA checklist for testing on real phones
A page-by-page checklist for testing on real phones, including the bugs that usually slip through.
Curated by Nvoka
ChatGPTClaudeGemini
Make it yours
Fill in the blanks and change any word. Only your copy changes, never the card.
Fill in the blanks
0 of 2 filledYour prompt
Act as a QA lead who tests websites on real devices. Create a mobile QA checklist for {{website_url}}, covering these pages: {{key_pages}}.
Start with a device plan: a small phone about 375 pixels wide, a large phone, a mid-range Android phone and a tablet, using Safari on iPhone and Chrome on Android, plus the in-app browsers that open when people tap links on social media.
Then checks for every page, including those that usually slip through:
- No sideways scrolling or cut-off text, from 320 pixels wide up
- Tap targets big enough and far enough apart
- Form text at 16px or larger so iPhones don't zoom in, and the right keyboard for email, phone and numbers
- Sticky headers, chat buttons and cookie banners that cover content or the on-screen keyboard
- Full-height sections that jump when the browser bar hides
- Content hidden under the notch or home bar
- Menus, dialogs and carousels that open, close and scroll properly
- Tap-to-call, map and directions links
- Pinch-to-zoom still allowed, and layouts that hold with large system text
- Speed on a slow connection, and a back button that goes where people expect
Return a checklist table with pass and fail columns per device, then a short bug report template: device, browser, steps, expected, actual and screenshot.