Notes | Back to the Voter List
# Townhall Voter List Software: UI/UX sample, one page (2026-11-06, revised)
Local only. Folder `C:\ct\aoa-rwa-demo4` (copy of demo3; demo, demo2, demo3 untouched). Run `start-demo.cmd`, open http://127.0.0.1:4176/ . Stop with `stop-demo.cmd` (port 4176 only). Sample society: Sample Heights RWA, 120 flats, 151 owner rows. Sample data only, nothing saved, no deploy, no push, no payment. Guide: `NAVIGATION-GUIDE.md`. Screenshots: `screens\` (10 PNG).
## The design: ONE page
The whole product is a single page (`/`, also `/v`). The user never changes page. A sticky step bar shows progress and jumps (smooth scroll) to each section; finished sections fold into a one-line summary with Edit (reopens in place); Checks updates in place; Save is locked until clean; after Save the same page shows "Saved as the Voter list" with Your Voter list (tabs) and What next?. Old `/v/...` addresses redirect to the matching section.
## Sections
| # | Section | Owner rule it answers |
|---|---|---|
| 1 | Society details | body type (5 + Others with a box to write it), Country (India first), State / Region, registration no. + registering office (recorded, not verified), optional bye-laws. No authority tick |
| 2 | Upload or paste + template | columns incl. Weight; name, mobile and e-mail required for every owner (e-mail may repeat); unit unique; many owners per unit; one voter per unit |
| 3 | Who may vote | five rules (Owner only, Owner or tenant, Owner or authorised proxy, Owner tenant or proxy, Member only), bye-law clause, proxy tied to one event, state-differences note |
| 4 | Weightage | equal by default; unequal = the society gives each unit its own weight (editable, paste or upload a Weight column), total and % update live. No area / sq ft |
| 5 | Checks (free) | counts, 8 things mended in place (missing or badly formed e-mail now among them), 2 reminders, save locked until clean, names masked outside working tables |
| 6 | Save | "Save as the Voter list" = Version 1 of your Voter list, plain summary, Rs 199 / $3 slot "to be confirmed by the owner" |
| 7 | Your Voter list (tabs) | versions, edit and save new version, freeze a copy for an event, printable register, change history, second organizer, sign in again by mobile code |
| 8 | What next? | other four products, "already filled in", price-difference slot |
The sticky bar keeps the demo3 pattern: Attendance and End to End greyed with a padlock and an Upgrade-style note until the list is saved.
## Rules the sample commits to (all for owner confirmation)
- Errors (stop the save): empty unit, duplicate unit, missing or bad mobile, unit with two voters, unit with no voter. Warnings (do not stop): same mobile on two units ("holds two votes, confirm"), duplicate names.
- Names full only in working tables (Checks, Edit); masked everywhere else. Registration number is recorded, never called verified.
- Each event freezes its own copy of the list; edits of the Voter list make a new version.
- Price: upload and check free; first paid step = Save as the Voter list, Rs 199 / $3 (slot, unconfirmed). Payee only IT SERVICES BY RAJAT AGARWAL via Razorpay.
## Checked
`node tools/smoke.js` against port 4176: 231 of 231 green (one-page structure, each section's content, 14 old addresses redirect and open, links, masking, presets, weight and lock logic, sample numbers only, no key words). The in-page behaviour (steps fold, mend in place, save locks then unlocks, saved panels open) was also clicked through once in the in-app browser. Phone width checked for sideways overflow (none). Screenshots by headless Edge, one at a time (the phone one at 500 px). Not checked: a real phone, screen readers, any real upload, SMS or payment (all sample buttons).
## Open questions for the owner
1. Price ladder: is saving Version 1 Rs 199 / $3? Are later versions (edits) free, paid, or limited per year? How much is deducted when moving to Attendance or End to End?
2. Order: upload comes before the voting rule and weights (as listed). Is that right, or should the rule be chosen before the upload?
3. Should a "same mobile on two units" warning require a tick before saving, or only a glance (sample: glance, with an optional confirm)?
4. Weights are given by the society unit by unit (no area). A Capacity column (Owner / Co-owner / Tenant / Proxy) was added so the rule can be checked; a proxy is shown as an event item, not a list row. OK?
5. Who may be a second organizer (any mobile, or only people named in the society papers)? Can an organizer remove another?
6. Which states and body types get ready-made rule choices first (Karnataka RWA is shown)? Wording on state differences needs the owner's lawyer's eye.
7. After Save, the earlier sections can still be reopened with Edit. Should that be allowed, or only through "Edit and save a new version"?
## Latest owner changes (applied)
Kind of body has an Others option; Country dropdown (India default) and State / Region added; e-mail is required for every owner (missing or badly formed e-mail is an error, 8 things to mend in all); the whole page was re-read and unsettling wording softened (no "how a person is reached", "problems" became "things to mend", masked names are "shown in a short form to keep them private", history is a simple record).