Lekhit
Your UPI history, sorted automatically. A private personal finance and budgeting app built for UPI, with splits built in.
- Expo
- React Native
- Tamagui
- Reanimated
- Gesture Handler
- Supabase
- Postgres RLS
- Turborepo
Read the decision log
Frontend & Mobile Engineer · Pune, India
I build web and mobile products that feel fast, and I write down why every decision was made.
01About

I'm a frontend engineer who got here by caring about the product first. Before I write a component I want to know who it's for, what it's replacing and what happens when it fails. The code tends to get simpler once those answers are clear.
Most of my week is spent inside a large, long-lived React codebase, with years of decisions made by people who've since moved on. I like that kind of work. Improving a system people depend on, without stopping it, teaches you more about trade-offs than any greenfield project.
Outside of that, I'm building Lekhit on my own, on my own time: a private money tracker for India that sorts your UPI history and splits expenses with friends. It's where I get to own every layer, from the design system to the database, and where I keep sharpening my product judgement.
02Experience
Pune, India
Full-time
Frontend engineering on a large, long-lived, multi-tenant B2B web application.
Pune, India
Full-time
Full-stack product engineering, mostly on the frontend.
03Selected work
Your UPI history, sorted automatically. A private personal finance and budgeting app built for UPI, with splits built in.
Read the decision log
Where it started. A MERN app for patients, doctors and admins, built in college.
React · Node.js · Express
04Skills
05How I work
Product decisions start with evidence: app-store reviews, competitor teardowns, the forums where people complain. Lekhit exists because that research found a gap.
A short written spec before code: the problem, the constraints, what's out of scope. If I can't write it down, I don't understand it well enough to build it.
Break the spec into steps that can each ship and be reverted on their own. Big migrations go out in phases, not in one heroic PR.
Claude Code does the typing; I do the judgement. CLAUDE.md conventions, custom skills and parallel git worktrees let several streams of work run at once, and review stays human.
06Now
Updated
Watching how the first users import their statements, fixing what confuses them, and getting the app ready for a public launch.
Writing design docs before code, studying how large frontends split ownership, and getting better at the decisions that are expensive to undo.
Turning what works in Claude Code into reusable skills, conventions and guardrails, so speed never comes at the cost of code I'd be happy to review.