Apps designed for the hand that's holding them.

A mobile app is used one-handed, in bad light, with a notification covering half the screen. That context sets every constraint. I design apps that work at that moment — not only in a clean mockup.

Start a project

DesignBuildGrowScale

One continuous process. One partner.

Not four services — four stages of the same product.

01 — Scope

What this covers

One engagement, not a menu. Take the whole thing or the part you're missing.

02 — Fit

For launch, or for retention.

Teams launching a consumer or field app, or fixing one that installs well and retains badly. The work so far spans agritech used outdoors on low-cost Android phones, women's health where onboarding asks for sensitive data, and food scanning done in a supermarket aisle.

03 — Work

Where this has shipped

Live projects that were mostly this kind of work.

Mobile AppsAgricultureLive

An agritech app putting crop guidance, soil health, weather, inputs and expert consultation in the hands of Indian farmers.

50K+ downloads · 4.0★ from 398 reviews on Google Play

Mobile AppsWomen's healthLive

A women's health app pairing cycle and symptom tracking with health FAQs and an AI assistant — designed for questions people would rather not say out loud.

4.9★ from 34 reviews on Google Play

04 — Questions

Common questions

iOS, Android or both?
Both, designed together. The component system is shared; the platform conventions that genuinely differ are respected.
Do you design the store listing too?
Yes. Screenshots and the feature graphic are part of the conversion path, not an afterthought — they're included.
Can you build the app?
I build React Native and web front-ends. A fully native build I'd design for and hand to your engineers.
What about an existing app that isn't retaining?
That's a diagnosis engagement first — where the drop-off is, why, and the smallest set of changes that moves it.