Village Records Portal
What this demo shows: a user signs in, manages their own village records, sees a personal dashboard, and watches a record sent from the field app appear on it.
Dashboard
Population by district
Recent entries
Simulate the Android app
The field app would send a record to the API. Press the button to send the next sample record and watch the figures above change.
No requests yet.
Villages
| Village | District | Population | Source | Actions |
|---|
Your profile
API contract
The portal and the Android app would talk to one backend. These are the endpoints this prototype simulates. Every endpoint except register and login needs a bearer token and only ever returns the signed-in user's own data.
| Method | Path | What it does |
|---|---|---|
POST | /api/register | Create an account, returns a token |
POST | /api/login | Sign in, returns a token |
GET / PUT | /api/profile | Read or update your profile |
GET | /api/villages?q= | List and search your villages |
POST | /api/villages | Add a village (the Android app uses this) |
PUT / DELETE | /api/villages/{id} | Edit or remove one of your villages |
GET | /api/dashboard | Totals, per-district figures, recent entries |
Demo data
Your changes are kept in this browser only. Reset to get the original sample records back (all accounts you created here are removed).