Simplify mobile navigation and update progress plan

This commit is contained in:
Rijad Zuzo
2026-02-15 14:34:26 +01:00
parent ac9577c759
commit d708aa58d9
6 changed files with 359 additions and 47 deletions
+51 -1
View File
@@ -2,6 +2,11 @@
Updated: 2026-02-15
## Workflow Rule
- After every sensible change, the final step is a Git commit with a clear message.
- Keep changes in small, logical commits so future sessions can revert or continue safely.
## Latest Milestone (2026-02-15): Product UI Flow Implemented
The app now has a real multi-screen user experience on macOS (and other platforms), not just a placeholder screen.
@@ -10,7 +15,8 @@ Delivered UI architecture:
- App shell with responsive navigation:
- desktop: left sidebar + content pane
- compact: bottom navigation
- compact: bottom navigation (reduced to 4 primary tabs)
- compact secondary actions (`Sync`, `Settings`) moved into a `More` menu to avoid tab overload on iOS/mobile
- Views implemented:
- Dashboard
- People
@@ -52,6 +58,50 @@ Validation status after UI milestone:
- `flutter analyze` -> pass
- `flutter test` -> pass
## Current Gap Analysis (2026-02-15)
### What we have now
- Backend gateway architecture with REST + fake implementations, typed DTOs, retries, refresh, and tests.
- OpenAPI + ADR documentation baseline.
- Product UI shell with responsive desktop/mobile navigation and key views.
- Offline-safe default behavior with fake backend mode.
### What is still missing
- Local database persistence and repository wiring (currently demo in-memory data).
- Full CRUD flows (create/edit/delete) for people, captures, reminder rules, gift/event ideas.
- Auth UX flows (sign-in, session-expired recovery, sign-out confirmation).
- Real sync orchestration layer (queue, cursor lifecycle, conflict policy UI).
- Notifications/reminders delivery and scheduling integration.
- End-to-end and integration tests for app flows beyond unit/widget basics.
## Implementation Plan (Next)
### Phase 1: Data Foundation
1. Introduce local DB schema + repository interfaces for core entities.
2. Replace `LocalRepository` demo data with persisted data access.
3. Add migration/test coverage for DB reads/writes.
### Phase 2: Core Product Flows
1. Build People CRUD and detail editing screens.
2. Build Moments/Captures create-and-list workflows.
3. Add Ideas and Reminder Rule management.
### Phase 3: Sync + Auth UX
1. Add sync queue service and cursor management use cases.
2. Add conflict handling strategy and UI states.
3. Implement sign-in/session lifecycle screens and provider state.
### Phase 4: Quality + Release Readiness
1. Add CI for analyze/test and optional build smoke checks.
2. Expand widget/integration tests for primary user journeys.
3. Add observability hooks and production hardening pass.
## Current Status
The Flutter app now includes a production-grade backend integration scaffold with an offline-first posture: