SabkiApp

SabkiApp set out to serve a fast-growing, media-heavy audience across both web and mobile. The hard part wasn't any single feature — it was doing all of it from one small team without the codebase fragmenting or the experience slowing down as traffic and content volume climbed.

I treated the backend as the single source of truth and let the clients stay thin. A Django API owns the data and the rules; Flutter renders it natively on web and mobile from one codebase. Every heavy path was measured before it was optimized, so effort went where latency actually lived.

A Django REST backend on PostgreSQL serves Flutter clients for web and mobile, with media in object storage and releases automated through Git-based CI/CD.

The admin layer is modeled on India's real administrative hierarchy — state, district, and below — so permissions map to how the organization actually works instead of an ad-hoc list of roles.

Keeping response times flat under media-rich, high-concurrency traffic meant hunting down N+1 queries and pushing work into the database with the right indexes.

The permission model had to be granular enough to mirror a real administrative hierarchy without becoming impossible to reason about — and releases had to stay safe while a small team shipped quickly.

Measure before optimizing; most of the latency hid in places intuition would never have guessed. And a permission model that mirrors the real-world org chart is far easier to extend than one invented for the database.