Society-management platform

Housing societies ran their gates and their residents on paper registers and phone calls. Nobody could audit who came in, a person the society had banned could still talk their way through, and nothing kept working when the gate lost its connection. Every society also needed its own branded deployment.

• I joined after the first release. The original developer built the core: signed QR passes that validate offline, the offline scan queue, the licence check and the audit log. Since June I have been the platform's main developer.
• Admin roles: I consolidated the platform to four roles and added scoped sub-admins. A super-admin grants sections, and the database enforces each grant through row-level security, so a sub-admin cannot read or write a section it was not given, even by calling the API directly.
• A gate blocklist: a society can flag a person or a vehicle, and the database refuses to issue them a pass, through a trigger on manual entries and a check in the event-arrival function. Gate phones keep a copy of the list, so the guard is warned even offline.
• Gate-mounted scanners: I added USB scanner input, so drivers hold their phone up to a fixed reader and the scan runs through the same pipeline as the camera.

• Live with its first housing society, each society on its own Supabase project, web build and mobile build.
• Every grant, revocation and blocklist change is written to the audit log.
• I fixed a refetch storm in the gate app's list of people inside, which set in at around 310 people.
• I reskinned every gate-keeper screen to the new design system with no change to its behaviour.

• Enforce permissions in the database. A hidden button is not access control.
• Make a ban a database rule, so no app version can skip it.
• Keep what the gate needs on the device. The network fails at the worst moment.