Check the journey from a fresh starting state
Ask a new participant what the product helps them do before showing the main action. Observe whether they can understand the instructions, choose a sensible next step and finish a first task. Note when they rely on help from the person running the test. A returning account with saved preferences may hide first-use problems, so record the starting state instead of treating a familiar team member's smooth experience as universal proof.
Test recovery as well as the happy path
Decline an optional permission and inspect the available next step. Save dummy work, restart and look for the same item. Use a safe offline or failed-request state and inspect the explanation and retry behavior. Keep the task within approved test access; purchase checks belong in the provider's sandbox. Record expected and actual behavior, including uncertainty when a failure cannot be reproduced. These observations make a useful bug report rather than a vague low grade.
Review interaction on supported devices
Check the important text on a smaller supported screen and with larger text settings. Try the chosen controls with the input and accessibility features relevant to the participants. Look for clipped instructions, missing labels, confusing focus order and controls that cannot be reached. Preserve the device and settings with the report. A quick review can identify follow-up work, but a formal accessibility audit needs broader coverage and appropriate expertise.
Working example
Example finding: 'On the recorded device and build, declining notification access leaves the next button unavailable. The task was to save one dummy note. Expected: continue without optional notifications. Actual: onboarding could not continue. Reproduction: three attempts from the same fresh state.' This fictional report identifies a condition to investigate; it is stronger evidence than assigning the whole app a low score without context. Retest the changed journey before declaring the issue resolved.
Create a grading scorecardYour next steps
- Choose a supported device and explicit starting state.
- Observe one outcome before explaining the interface.
- Record recovery behavior and reproduction steps.
- Retest the same condition after a verified change.
Official sources
Sources checked October 2, 2026. Review the current provider documentation before acting on requirements.
Turn the next test into something useful.
Publish a focused brief on RateMyApp. Credits fund approved private reports; public store reviews are voluntary and unrewarded.
List your app for feedback