Reach feature parity with the iPhone app #1
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/ios-parity"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Audit of ContentView/SettingsView/Watch/LiveActivity against the port found ~25 gaps; this closes them.
Day view: 17-day strip (a week behind, ten ahead) with drawn marks, paged swipe between days, pull-to-refresh, Bonjour/Bonsoir and dated titles, end-of-day copy and card, next-duty line on rest and unpublished days, day message banner, documents menu, the iPhone's overview ruler, comments on the hero and per leg, vehicle-change markers, tap-a-run itinerary sheet, long-press share/save of the day or what is left of it, a real Aide sheet, one-sentence TalkBack rows.
Behaviour: refetch on every foreground, keep-awake only during a duty (default on, like iOS), midnight window rollover, current-duty feed kept apart from per-day rosters (today never shows tomorrow's duty), cached days dropped when the server changes, delivered alerts cleared on open.
Settings: first run shows the server alone, resolved URL echoed, test connection, cancel and back, watch-vibration toggle carried to Wear, alerts read back as a sentence.
Landscape: comments, progress, shift end, per-step girouette, stale line. Notification: system chronometer countdown, "Fin de service à …". Wear: Bientôt / Terminé / Repos.
Verified on a Pixel 3a (API 32) against the live server and the debug fixtures; README status updated accordingly. Not exercised: the stops sheet (no itinerary data available), Wear at runtime, the notification chronometer during a live duty.
🤖 Generated with Claude Code