Establish what is happening
Capture the first screen
Record viewport width, device orientation, page heading, visible setup action, navigation state, and project context using synthetic data. Note clipped text, horizontal overflow, tiny controls, and whether the primary action appears before explanatory content. Do not treat a tall page as a failure by itself.
Exercise touch and focus
Tap each core setup action, open the keyboard, submit a valid and invalid field, scroll, refresh, and return from a link. Record focus position, error visibility, control movement, and whether the next step remains apparent. Keep device and browser versions with the fixture.
Compare durable progress
After each action, compare the mobile page with saved workspace, project, key metadata, and built-in check state. A clipped button and a failed save are different findings. Mark any uncontrolled mobile browser or processing behavior as an evidence boundary.
What to carry forward
Triage is complete when the narrow viewport, first action, responsive symptom, setup state, and durable outcome are recorded. Classify a presentation blocker separately from a domain failure and preserve the exact device and browser conditions that reproduce it.
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