How thomasvtf/zentheris-prototype works
Zentheris is a Colombian household energy-monitoring and reduction app: the Expo client presents household consumption and advice, calls a FastAPI REST API, and the API uses Supabase. The domain spans household setup and membership, simulated readings by household and zone, consumption history, goals and tariffs, and alerts and tips. The README documents those product capabilities; the sampled backend shows router-to-service delegation, while several service implementations remain skeletal or unsampled, so their storage and simulation links are not asserted as verified calls.
Main entry points: services Use-case services · main.py API application · users.py User and onboarding · members_invitations.py Households and members
Components 21
Mobile app
- Expo client
app/src/app/_layout.tsx - Consumption dashboard
app/src/screens/DashboardScreen.tsx - Feature screens
app/src/app - API client
app/src/api/client.ts
REST API
- API application
api/app/main.py - User and onboarding
api/app/routers/users.py - Households and members
api/app/routers/members_invitations.py - Consumption and history
api/app/routers/consumption.py - Goals and tariffs
api/app/routers/goals_tariff.py - Alerts and tips
api/app/routers/alerts_tips.py - Use-case services
api/app/services - Authentication and permissions
api/app/security/dependencies.py - API schemas
api/app/schemas
Energy domain
- Simulated readings
api/app/domain/simulator - Consumption rules
api/app/domain/alert_rules.py - History calculations
api/app/domain/history.py
Persistence and identity
- Database sessions
api/app/data/database.py - Supabase PostgreSQL
- Supabase Auth
- Supabase Storage
Other components
- Household user
Connections 29
- Household user → Expo client: uses
- Expo client → Consumption dashboard: presents
- Expo client → Feature screens: presents
- Consumption dashboard → API client: requests data
- Feature screens → API client: requests data
- API client → API application: calls REST API
- API application → User and onboarding: registers
api/app/main.py - API application → Households and members: registers
api/app/main.py - API application → Consumption and history: registers
api/app/main.py - API application → Goals and tariffs: registers
api/app/main.py - API application → Alerts and tips: registers
api/app/main.py - User and onboarding → Use-case services: delegates to
api/app/routers/users.py - Households and members → Use-case services: delegates to
api/app/routers/members_invitations.py - Consumption and history → Use-case services: delegates to
api/app/routers/consumption.py - Goals and tariffs → Use-case services: delegates to
api/app/routers/goals_tariff.py - Alerts and tips → Use-case services: delegates to
api/app/routers/alerts_tips.py - User and onboarding → Authentication and permissions: requires identity
api/app/routers/users.py - Households and members → Authentication and permissions: requires identity
api/app/routers/members_invitations.py - Consumption and history → Authentication and permissions: requires identity
api/app/routers/consumption.py - User and onboarding → API schemas: validates with
api/app/routers/users.py - Households and members → API schemas: validates with
api/app/routers/members_invitations.py - Consumption and history → API schemas: validates with
api/app/routers/consumption.py - Use-case services → Database sessions: may access
- Use-case services → Simulated readings: may use
- Use-case services → Consumption rules: may apply
- Use-case services → History calculations: may apply
- Database sessions → Supabase PostgreSQL: connects to
- API application → Supabase Auth: uses
- API application → Supabase Storage: uses