Eight years across government ration counters, dairy delivery routes, hospital front desks and music streaming. Kotlin, Java and Dart — plus the fingerprint scanners, iris readers and Bluetooth scales those apps have to talk to.
Tap an icon — real apps, real screens
Mobile engineer who's comfortable being the only developer in the room and the one leading fifteen of them.
I started out parsing JSON and wiring up SQLite on plain Android apps. Eight years later the JSON is still there, but it's coming off a Bluetooth weighing scale in a ration shop, or an Aadhaar biometric SDK that has to work on a five-year-old device with patchy signal — no retry button, no "try again later."
That's the thread through everything I've built: government POS terminals, a dairy delivery platform, a hospital check-in system, a music streaming app, and GoFixKart — a repair-and-parts platform I own and run end to end. Different domains, same discipline — the app has to be right the first time, because the person using it isn't a developer and doesn't get a second attempt.
Along the way I moved from writing every line myself to leading a team of fifteen doing the same — architecture calls, code review, and still shipping features when the schedule needs it.
Tagged by platform and the domain it shipped into. Orange marks the ones wired to physical hardware, mint marks the ones you can visit live.
JECRC University · 2016 – 2018
Open to senior mobile roles and contract work. Fastest reply is email — phone works too, IST hours.