How andifishman/eldertech6 works
ElderTech is a resident-facing mobile app backed by an API, with a separate administrative backoffice. Residents use the app for schedules, learning content, messaging, assistant chat, requests, and leisure; staff manage residents and these services in the backoffice. The backend exposes domain APIs and integrates with persistence and external providers. The tree and sampled files support the overall feature map, but no README was supplied and most feature-specific implementations were not sampled, so uncertain internal wiring is omitted.
Main entry points: ProviderManager.ts Provider manager · assistant.controller.ts Assistant controller · AssistantService.ts Assistant service · app.ts API application
Components 24
Resident app
- App navigation
app/_layout.tsx - Resident features
app - Mobile services
src/services - API client
src/services/apiClient.ts
Backend API
- API application
backend/src/app.ts - Assistant routes
backend/src/routes/assistant.routes.ts - Assistant controller
backend/src/controllers/assistant.controller.ts - Assistant service
backend/src/services/assistant/AssistantService.ts - Hablemos controller
backend/src/controllers/hablemos.controller.ts - Hablemos service
backend/src/services/hablemos/HablemosService.ts - Domain services
backend/src/services - Repositories
backend/src/repositories - Provider manager
backend/src/core/provider/ProviderManager.ts - External search
backend/src/services/search/SearchService.ts
Admin backoffice
- Backoffice routes
backoffice/src/App.tsx - Management features
backoffice/src/features - Backoffice API client
backoffice/src/lib/apiClient.ts
Data and providers
- Supabase
src/services/supabase.ts - AI providers
backend/src/providers/chat - Tavily search
backend/src/providers/search/TavilySearchProvider.ts - Push notifications
backend/src/providers/notifications/ExpoPushProvider.ts
Other components
- Resident
- Staff administrator
- Expo notifications
Connections 23
- Resident → App navigation: uses
- App navigation → Resident features: routes to
- Resident features → Mobile services: uses
- Mobile services → API client: requests
- API client → API application: calls API
- API application → Assistant routes: mounts
- Assistant routes → Assistant controller: dispatches
- Assistant controller → Assistant service: calls
- Assistant controller → Hablemos service: calls
- Hablemos controller → Hablemos service: calls
- Assistant service → Repositories: persists and reads
- Domain services → Repositories: uses
- Staff administrator → Backoffice routes: uses
- Backoffice routes → Management features: routes to
- Management features → Backoffice API client: requests
- Backoffice API client → API application: calls API
- Repositories → Supabase: reads and writes
- Assistant service → Provider manager: delegates
- External search → Provider manager: executes through
- Provider manager → AI providers: dispatches
- Provider manager → Tavily search: dispatches
- Domain services → Push notifications: sends notifications
- Push notifications → Expo notifications: sends pushes