Check whether the outcome improved
Replay the original mobile workflow
Use the same device class, operating system, viewport, connection profile, account shape, route, and tap sequence as the baseline. Record tap-to-feedback, request waterfall, first useful content, completion, and errors. Repeat cold and returning states when caching or startup work could change the result.
Compare stronger and weaker connections
Run the workflow on a normal mobile connection and a deliberately slower profile while keeping the device fixed. Check whether the change reduces blocking requests or merely improves one ideal case. Confirm progress feedback, retry controls, and cancellation remain understandable when transfer takes longer.
Check touch, navigation, and content integrity
Exercise back navigation, repeated taps, form entry, scrolling, and the first decision after content appears. Confirm no fields, images, errors, or status changes are omitted and no duplicate request changes state. Record any device-specific layout or focus regression alongside timing results.
What to carry forward
Classify the result as improved, regressed, unchanged, or inconclusive with device, connection, workflow, and timing evidence attached. It passes only when the intended mobile action becomes usable sooner, slow conditions recover correctly, and content and touch behavior retain their original meaning.
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