Portfolio · [Grade 12 / Class of 2027] · [Podar International School]

I build software that has to work outside the lab — in clinics and in villages.

I’m a student developer who designs, builds and ships real tools with the people who will use them — a physiotherapist, an NGO, a team of field volunteers. This site is a closer look at my two main projects and how I think about building them.

The short version

In 30 seconds

I built ADAPT
A camera-based physiotherapy game for Android, designed with a practising physiotherapist. Now preparing for release on Google Play.
I built Gaav Tithe Sau’s system, solo
The end-to-end system the Sau Foundation uses to manage its village volunteers, keep records of the people they help get welfare schemes, and measure its impact — overseen by Maharashtra’s Assistant Commissioner of Social Welfare. In closed testing on Google Play.
What ties them together
Depth over breadth. Two long projects, each built alongside the people who use it and designed around real limits: clinical safety, low-end phones, a pilot that had to run on a free server plan.
What I want next
[Intended major, and one sentence on what you want to explore at university.]

Focus

Health tech · Civic tech

Builds with

Kotlin & Jetpack Compose, Flutter, Supabase, on-device ML

Right now

Preparing ADAPT for release on Google Play

Depth over breadth

Two projects, built for real people

Two long-running builds, each with a full case study: the problem, the decisions, and what I learned.

What they show

Three habits I bring to everything

01

Build with the person who’ll use it

A physiotherapist shaped ADAPT’s exercises, angle settings and even its platform. Gaav Tithe Sau’s rules come straight from the foundation and the commissioner’s office that oversees it.

02

Design around the constraint

Budget phones, patchy village internet, a free-tier server: I treat limits like these as the brief, not an afterthought.

03

Write the decision down

Both projects keep a numbered decision log and task list, so every choice has a reason I can point back to — and someone else could pick up the work.

About me

[Photo of you]

[2–3 sentences in your own voice: where you’re from, what first got you building software, and why you keep choosing problems in health and public services.]

[What you want to study, and one thing you hope to build or understand in college.]

Outside of code

[Other activities, interests, languages spoken]