Complete platform with unified design system and real API integration. Apps: Dashboard, Fitness, Budget, Inventory, Trips, Reader, Media, Settings Infrastructure: SvelteKit + Python gateway + Docker Compose
885 B
885 B
Platform Architecture
Goal
One frontend product with two sections:
/trips/fitness
Separate backend services remain in place:
services/tripsservices/fitness
The legacy frontends stay runnable during migration for fallback and comparison.
Service Boundaries
- Trips backend remains independent.
- Fitness backend remains independent.
- Trips and Fitness keep separate SQLite databases.
- Platform frontend owns the shared shell and explicit API proxy layer.
Proxy Contract
/api/trips/*-> Trips backend/api/fitness/*-> Fitness backend
Frontend code should call these proxy paths, not raw backend URLs.
Migration Order
- Keep both legacy frontends alive.
- Build platform shell.
- Add explicit proxy/API clients.
- Migrate one product area first.
- Migrate the second area.
- Retire legacy frontends only after full coverage.