Aglet

How to verify a mobile first setup journey across states

Verification should prove that a new owner can see and complete each core setup action on a narrow device without losing input or context. Use a realistic width such as 390 pixels, then check a nearby width and desktop to catch fragile breakpoints without claiming every device is covered.

Check whether the outcome improved

  1. Verify the first screen

    Open a synthetic new workspace at the target narrow width and assert the heading, project or setup action, navigation, and result expectation fit without horizontal scrolling. Confirm the first action is visible or clearly reachable and that text remains readable at normal zoom.

  2. Verify interaction states

    Tap core controls, submit valid and invalid fields, open the keyboard, scroll to errors, refresh, and use back navigation. Assert focus and messages remain discoverable, values survive where expected, and each failure exposes a specific next action rather than a clipped control.

  3. Verify the full setup

    Complete project creation, test-key creation, built-in check, and links to labeled sample Signal and Work Item using synthetic records. Assert workspace context and role boundaries at each step. Test a nearby narrow width and mark unsupported device or assistive coverage partial.

What to carry forward

Accept when the core setup path is readable, tappable, recoverable, and tenant-scoped at the tested narrow widths. Mark untested devices or OS keyboard behavior partial; a single successful tap path does not prove all mobile states.

Keep the decision with the work.

Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.

Create an account See the product workflow