Files
rippr/docs/feedback
uhryniuk 1a2e69cbf3 FB-08: reflow HUD row widgets when a metric is hidden or shown
setVisible now calls a new _reflowRow helper on the toggled metric's row,
spreading the remaining (or newly added) visible widgets evenly across the
4-column grid instead of leaving a blank cell where a hidden metric used to
be. Reflow is scoped to setVisible only; drag/resize behavior is unchanged.
2026-08-24 23:33:05 -05:00
..

Post-launch feedback tickets

Same shape as docs/ui-redesign/: one file per ticket, Goal · Context · Design · Implementation · Acceptance criteria · Tests · Risks · Out of scope, written before implementing, with an Outcome section appended after.

Source: docs/FEEDBACK.md — hands-on feedback after using the redesigned app. Turned into 5 tickets, each independently completable (self-contained enough for a fresh subagent with no prior context to implement correctly).

The tickets

# Ticket Size Depends on Status
FB-01 Live, street-level map everywhere L — Done
FB-02 Hide the idle Speed panel until recording starts S — Done
FB-03 Grid-snapped HUD widgets with auto-fit text L — Done
FB-04 Fix Route Planner's map failing to render + zoom M FB-01 (shared zoom constant) Done
FB-05 Closed-loop routes in Route Planner M FB-04 (same file) Done

Dependencies / dispatch order

Wave 1 (parallel): FB-01, FB-02, FB-03
Wave 2 (after Wave 1 lands): FB-04 — reuses FB-01's ambientZoom constant
Wave 3 (after Wave 2 lands): FB-05 — heavily edits the same file FB-04 just touched

FB-02 and FB-03 both touch lib/src/ui/record/record_screen.dart, but disjoint regions (the idle-state Column vs. _HudMetricValue) — low conflict risk.

Working method, per ticket

  1. Implement against the ticket's own Implementation section.
  2. flutter analyze clean, flutter test green — count must not regress (374 passing before this batch starts).
  3. Outcome section appended to the ticket file: what shipped, deviations, test counts.
  4. Commit, status flipped to Done in both the ticket file and this table.

Android-emulator verification is best-effort only for this batch — lean on widget tests as the primary bar; don't get stuck fighting emulator flakiness.