March 8th. First commit. Initialize project using Create React App.
That is the whole entry. No fanfare. No announcement. Just a project folder, a blank screen, and an idea that had started with a conversation about WhatsApp chats and yoga students.
The first week
The first real features went in on March 9th — onboarding tour, global search, birthday reminders, bulk attendance, revenue goals. It was not clean code. It was momentum. When you are building alone and the idea is clear in your head, the first few days feel like the fastest you will ever move.
By March 11th there was a working app. By March 12th it had a theme system, schedule conflict detection, and support for 120 countries.
What actually took time
Attendance counting. Two sources of truth — an attendance log and a counter on the client record — kept drifting out of sync. A client would show 19 sessions attended against a total of 12. I fixed it multiple times. It kept finding new ways to break.
The APK. March 17th and 18th were the first real Android builds. Ten APK releases in two days. One day the build went from 5MB to 88MB because old APKs were being bundled into the new build. Found it. Fixed it. Back to 7.1MB.
Notifications. Push notifications looked straightforward. They were not. The token was never being saved due to a race condition that only showed up on real devices. Then a Samsung S24 blocked all notifications from apps on the testing track.
The name that almost stuck
For the first month the app was called UFCM. Universal Freelance Client Manager. Practical name. Completely unbrandable. I came back to something I had been thinking about — the Sanskrit word prabandhan. It means management. Prabandhan became Prabzo.
April 7th: rebrand: UFCM → Prabzo, new logo, v3.0.0. One commit. Four weeks of building under a different name, erased from the front end in a single push.
shri
I built a local intent engine first. It handles the most common actions — marking attendance, checking balances — without touching any external AI at all. Only genuinely complex queries go to an external AI, with multiple fallback providers.
The local engine worked first try. I typed "mark attendance," shri asked "who for?", I said "Amrita," shri confirmed, attendance marked. That moment was the moment I knew the app was real.
April 11th, 4am
I submitted Prabzo to the Play Store for the first time. Play Store requires a closed testing phase with at least twelve testers for fourteen days before production access. Twelve testers. Fourteen days. Then production access on April 28th. App registered on May 3rd. Marketing started May 7th.