Beginner

Mobile QA Checklist

A rigorous mobile QA pass: layouts, touch, keyboards, and the full core journey on phone-sized screens.

5 steps15 verify checks45-60 minutesWorks with: emergent · chatgpt · claude · cursor

Start Guided Walkthrough

#mobile #qa #responsive #touch #viewport

The Route

0/5 verified

Layout pass at phone widths

Find every layout break at real device sizes.

3 checks 02

Fix layout breaks

Make every page flow correctly in a single column.

3 checks 03

Touch and gesture pass

Fingers are not cursors - verify tap targets and touch behavior.

3 checks 04

Keyboard and input pass

The on-screen keyboard breaks more mobile apps than anything else.

3 checks 05

Core journey on mobile

The final proof: complete the app's main task entirely on a phone-sized screen.

3 checks

Every step ends at a Verify Gate. Do not continue until every check passes.

Context Pack

Paste this first. It briefs the AI on requirements, constraints, and the Definition of Done before your first build prompt.

Context Pack

PROJECT CONTEXT:
Before users hit my app on phones, I want a systematic mobile QA pass that catches real usability failures.

GOAL:
Verify and fix the app at mobile widths: layout integrity, touch usability, input behavior, and the complete core journey.

REQUIREMENTS:
- Layout audit at 375px and 414px on every page
- Touch target and gesture verification
- Keyboard and input behavior checks
- The core journey completed entirely on mobile
- All failures fixed and re-verified

CONSTRAINTS:
- Interact - do not just look at screenshots
- Hiding features on mobile is not a fix

DEFINITION OF DONE:
- Zero horizontal scroll on all pages
- All controls comfortably tappable
- Forms usable with the on-screen keyboard
- The core journey passes end to end at 375px

COMMON FAILURES TO AVOID:
- Overflow from fixed-width elements
- Modals with unreachable buttons under the keyboard
- Hover-dependent features unusable on touch
- Tables and long content breaking the viewport

Paste this into your AI builder first. It teaches the AI what you want before you give it the build prompt.

Related routes

More QA flows that share ground with this one.

Auth Flow QA

Dedicated auth testing: signup, login, sessions, guards, reset, and the edge cases that expose fake auth.

01Test the signup surface

02Test the login surface

03Test the session lifecycle

+2 more steps to Done

Best forbuilders who have shipped a basic app before

5 steps45-75 minutesIntermediate

Start Route Details

Evidence Checklist

Prove your app works with evidence: build a claim-by-claim verification pack with receipts.

01Inventory every claim

02Define verification procedures

03Execute and collect evidence

+2 more steps to Done

Best foryour first pass at this - no prior setup assumed

5 steps45-60 minutesBeginner

Start Route Details

Payment Flow QA

Trust-level testing for payments: success, decline, cancel, idempotency, and state consistency.

01Audit the money path

02Verify the success path

03Verify decline and cancel paths

+2 more steps to Done

Best forproduction-grade builds with strict verification

5 steps60-90 minutesAdvanced

Start Route Details