A product designer working quietly out of Kathmandu — building digital things with the patience of someone who believes the small decisions are the whole story.
I’m Amulya — a Sanskrit word meaning precious; something whose value cannot be measured in money. It’s a name I didn’t pick, but it has become the standard I design against.
I make digital products the way someone might make a hand-bound book — slowly, with attention to the parts most people won’t notice. The cursor on a disabled button. The pause before a modal closes. The way a sentence lands at 2am when nothing else is working.
“I didn’t choose design. Design kept choosing me.”
— A note to my younger self
What follows isn’t a résumé. It’s closer to a field journal — the places, habits, and quiet obsessions that shape the work I make.
A city of overlapping centuries — and the quiet reason my work looks the way it does.
Kathmandu is a city of overlapping centuries. A temple from the 5th century shares a wall with a café that opened last month. A tempo driver streams a podcast. A grandmother prays at a shrine older than most countries. Nothing is resolved, and yet everything coexists.
I grew up in that tension — between the inherited and the invented, the spiritual and the practical, the hand-carved and the machine-cut. It teaches you, quietly, that the new doesn't have to erase the old. Contrast is not a problem to solve; it's often the point.
That sensibility is what I bring to an interface. I want products to feel composed, not manufactured — made by someone, for someone. A little warmth in a cold medium. A little intention in a space that rewards shortcuts.
Three habits, practiced enough to feel like instinct. Not a framework. Just what the good days look like.
Before a single frame, the question. Who is this for, on what kind of day, holding what tension? Most design problems are mis-labeled clarity problems. I start with the quiet interview and the uncomfortable “why.”
Every pixel, copy line, and transition should be able to defend itself. If I can remove it and lose nothing, I remove it. The goal isn't minimalism — it's a finished object where nothing is accidental.
A design is only real when it's shipped and lived with. I stay close to engineering, copy, and QA — not to supervise, but because the last 10% is where taste is actually tested.
I don’t keep score, but the numbers do exist. Stamped and filed — so we can stop talking about them.
Three small confessions, pinned to a wall. Usually I’d cut them — this time they stay, because the work doesn’t make sense without them.
I keep returning to The Bhagavad Gita. Not for the religion — for the posture. The idea of doing the work without clinging to the outcome has quietly restructured how I handle critique, revisions, and the long middle of any project where nothing is beautiful yet.
— a.I collect micro-copy the way some people collect stamps. Empty states, error messages, the tiny sentence under a password field. A single well-chosen word can carry a product’s whole tone. Most of my best ideas arrive while re-reading someone else’s “Oops, something went wrong.”
— a.Ideas are cheap; execution is the whole game. I’d rather ship a flawed thing on Tuesday than polish a perfect thing forever. The taste, the rigor, the point of view — those only really show up in the finished object. Everything else is a mood board.
— a.A designer crafting intentional, human-centered digital experiences. Passionate about products that feel precious and made by people, not templates.
