OTP Phone Authentication for Indian Consumer Apps in Django

Fri, 20 Mar 2026 10:00:00 +0530

The first real product decision I made on this veterinary clinic-management platform — one I built solo for the Indian market back in 2019 — had nothing to do with clinics. It was this: the login is a phone number and a six-digit code, not an email and a password.

That sounds obvious now. It wasn’t the default I reached for. Django hands you username + password out of the box, djangorestframework-simplejwt assumes the same, and every tutorial I’d read wired auth that way. But the users were pet owners in Indian towns. A lot of them don’t have an email they check. All of them have a phone number, and they already expect “enter your number, get an OTP” because that’s how every app they use — payments, food, ride-hailing — logs them in. Phone is the identity here. Building email auth and bolting phone on later would have been solving the wrong problem first.

Splitting Celery Workers by Queue, Not by Scale

Sun, 15 Mar 2026 10:00:00 +0530

Here is the bug that never happened, which is the whole point.

A user opens the app, taps “log in”, and waits for a six-digit code to land on their phone. At the same moment, a clinic receptionist somewhere else hits “export” on a year of billing history — a fat Excel file that takes a while to build. On a naive Celery setup, those two tasks go into the same queue and get picked up by the same pool of workers. If the export grabbed a worker first, the OTP sits behind it. The user stares at a blank code field. To them, login is broken. Nothing threw an exception. The export was doing exactly what it was told.

Otp on Kuldeep Pisda

OTP Phone Authentication for Indian Consumer Apps in Django

Splitting Celery Workers by Queue, Not by Scale