← All clips · Uncategorized

Buy a ticket on a phone

PASSING GATE GuestMember 10 steps · 27.7s · recorded Aug 30, 10:02 AM · b690bff

Viewing an archived run (20260830T170219Z-b690bff). Back to the current run.

This run has no video.

Speed

Source: e2e/scenarios/test_wf_buy_a_ticket_on_a_phone.py:1 · run 20260830T170219Z-b690bff · steps carry start_ms/end_ms offsets into the video

Steps

  1. 390x844 — the screen most members actually use.

  2. The measurement IS the note. Everything else moved one tap away.

  3. Times, venue, lineup and share are one tap away — never removed. It is a real <details>, so find-in-page can open it too.

  4. Open by default: a desktop has the room, and hiding detail there is only cost.

  5. Reserve → checkout, untouched. This plan moved markup, not money.

  6. The other half of the note: 'hard to read and enter data into on mobiles — can we setup the look and feel like we did the schedule show time calculator.'

  7. One press fills the whole table, sized to this room by the SERVER. `name:price:capacity`, typed six times on a phone, was the thing the guided-input rule names as the violation.

  8. Precision stays possible; it stops being the default cost. The manual rows are the escape hatch, and the shape's rows are sitting in them, editable.

  9. 70ch, flex-wrap, min-width:0 — filed as a bug, fixed as a rule.

Notes

Sign in to leave a timestamped review note. Notes land in the same review backlog as in-page annotations.

  1. No notes on this clip yet.
Run history (6)