Keep the lesson for the next incident
Write the narrow contract
Document target widths, heading and action order, overflow expectations, form focus, error placement, keyboard recovery, and setup context. State the core project, test-key, and built-in check actions without promising device or producer coverage beyond the fixtures.
Keep mobile fixtures
Save synthetic traces for first screen, touch action, invalid form, keyboard open, refresh, back navigation, narrow breakpoint, and completed sample links. Assert visible action, saved progress, focus, route, and labels. Record device and browser limits with each fixture.
Define recurrence signals
Reopen review when a core action clips, horizontal overflow appears, errors move offscreen, saved input disappears, or mobile links lose workspace context. State tested widths and OS limits and assign an owner for new responsive branches.
What to carry forward
Close learning with tested widths, interaction and resume fixtures, setup context, and recurrence signals. A responsive improvement is durable when it preserves the same honest setup state and next action as desktop after interruption with named coverage.
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