uhryniuk
cf6b9d1d73
Turns docs/FEEDBACK.md into five self-contained tickets, each grounded in exact current code and a concrete implementation approach, so they can be handed to independent subagents with no prior context.
42 lines
2.1 KiB
Markdown
42 lines
2.1 KiB
Markdown
# 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](FB-01-live-street-level-map.md) | Live, street-level map everywhere | L | — | Not started |
|
|
| [FB-02](FB-02-hide-idle-speed-panel.md) | Hide the idle Speed panel until recording starts | S | — | Not started |
|
|
| [FB-03](FB-03-grid-snapped-hud-widgets.md) | Grid-snapped HUD widgets with auto-fit text | L | — | Not started |
|
|
| [FB-04](FB-04-route-planner-map-render-fix.md) | Fix Route Planner's map failing to render + zoom | M | FB-01 (shared zoom constant) | Not started |
|
|
| [FB-05](FB-05-closed-loop-routes.md) | Closed-loop routes in Route Planner | M | FB-04 (same file) | Not started |
|
|
|
|
## 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.
|