← Back to Mobile application starters · project planning pack
See how it helps
Mobile usability prototypes
Tests whether a proposed mobile journey supports realistic tasks while distinguishing observations from prototype assumptions.
mobile-prototyping-usability
Agents using this skill
When is it useful?
Use before committing to a flow based only on attractive screens.
What does it help you do?
- Defines user tasks and success or failure criteria.
- Observes comprehension, navigation and interaction friction.
- Records prototype limitations and prioritizes evidenced changes.
Try asking this
Evaluate a booking prototype with rescheduling and cancellation tasks, reporting observed confusion separately from assumptions. Give participants a conflicting appointment and ask them to reschedule. Record where they hesitate or fail, without treating prototype limitations as production defects.
Detailed documentation
Read the skill’s original instructions, examples and checks in their authored language.
Show less
Prototyping & Usability Evaluation
Validate mobile flows against realistic tasks and real-world usage constraints before and during implementation.
Task-Based Flow Evaluation
- Evaluate end-to-end tasks, not isolated screens: Walk through the complete user journey from entry point to completion, plus at least one error/recovery path and one interruption/back-navigation path.
- Realistic data & stress cases: Test layouts with realistic copy, long localized strings, missing optional fields, zero-data states, and large item counts rather than idealized placeholder text.
- Ergonomic & visual check: Verify thumb reachability for primary actions, visual hierarchy at arm's length, tap target spacing, and keyboard/safe-area overlap.
Evidence vs Assumptions
- Distinguish observation from hypothesis: Clearly separate verified facts (existing product behaviour, documented requirements, observed usability findings) from design assumptions that still require validation.
- Turn uncertainty into testable questions: When user behaviour or edge-case frequency is uncertain, formulate specific, answerable usability questions and define what a prototype walkthrough or test should observe.
- Honest prototype boundaries: Explicitly label simulated interactions, mocked data, and browser-based prototype limitations. Never claim native on-device verification based solely on a static mockup or web preview.
Included files 1
SKILL.md