How flowsensus-dev/flowsensus-frontend works
FlowSensus is a React portal frontend with a sign-in screen and a routed deployment-management shell. The visible workflow is user sign-in through Supabase, then navigation among dashboard, applicants, agencies, finance, and forecasting routes; those route bodies are placeholders in the sampled source. The frontend also provides an Axios client that attaches a Supabase session token to backend requests, though no caller of that client was present in the sampled files. The README gives only a high-level product description, so deeper domain behavior is not evidenced.
Main entry points: App.jsx Route registry · LoginPage.jsx Sign-in page · supabase.js Supabase client · api.js Authenticated API client
Components 10
Portal Routing
- React bootstrap
src/main.jsx - Route registry
src/App.jsx - Portal layout
src/layouts/AppLayout.jsx - Portal pages
src/App.jsx
Authentication
- Sign-in page
src/pages/LoginPage.jsx - Supabase client
src/lib/supabase.js
Service Clients
- Authenticated API client
src/lib/api.js
Other components
- Portal user
- Supabase Auth
- FlowSensus backend
Connections 12
- Portal user → React bootstrap: opens portal
- React bootstrap → Route registry: renders
- Portal user → Sign-in page: submits credentials
- Route registry → Sign-in page: routes to
- Sign-in page → Supabase client: requests sign-in
- Supabase client → Supabase Auth: authenticates
- Sign-in page → Route registry: navigates on success
- Route registry → Portal layout: renders portal shell
- Route registry → Portal pages: routes to
- Portal layout → Portal user: presents navigation
- Authenticated API client → Supabase client: reads session
- Authenticated API client → FlowSensus backend: sends authenticated requests