Open to select freelance projects
Muhammad AdnanProduct Design
I design digital products end to end: research the problem, map the flows, build the system, then sit with the engineers until it ships pixel-accurate. Most of my work is mobile-first — consumer apps, marketplaces, fintech and health products — plus the dashboards the teams behind them run on.
What I do
A beautiful screen that cannot be built, or that nobody tested, is a mood board. I work in the space between what users need, what the business is trying to earn and what the team can realistically ship this quarter.
The full arc of a product: understanding the problem, structuring the experience, designing every screen and state, and staying involved until it ships.
What this includesInterviews, competitive teardowns, journey maps and usability testing — run at whatever depth the timeline allows.
What this includesTokens, components, variants and the documentation that keeps them being used correctly.
What this includesThe majority of the 150+ interfaces I have designed are mobile.
What this includesAdmin panels, analytics platforms and operations tools.
What this includesAI features fail on interface far more often than on model quality.
What this includesSelected work
31 products in this portfolio — mobile apps, marketplaces, dashboards and AI tools. Here are the ones with the fullest story behind them.
Audio-first learning, on the commute
An audio summaries app for people who want the substance of a long read in the length of a drive. I designed the full listening experience — discovery, player, queue, offline library and the subscription flow behind it.
Property search without the noise
A property marketplace connecting buyers, renters and agents. I designed the search, listing and enquiry experience for buyers, plus the listing-management side agents work in every day.
Energy operations, made legible
An operations platform for energy asset monitoring. I designed the dashboard, alerting and reporting experience used by control-room teams — dense information without the wall-of-numbers effect.
Point, scan, decide — in three seconds
A barcode and label scanner that tells people whether a product fits their diet. I designed the scan-to-answer loop, the confidence and correction states, and the onboarding that teaches the app's limits honestly.
An AI assistant that shows its work
A workplace AI assistant. I designed the conversation surface, the source-citation pattern and the workspace where teams organise prompts, so answers can always be traced back to where they came from.
Group trips that survive the planning
A trip-planning app built around the part that actually breaks: group agreement. I designed shared itineraries, split expenses and a decision flow that stops a trip dying in a group chat.
Capabilities
Pick the one that sounds like your problem. Each is something I have done end to end, more than once.
The standard I hold
Anyone can produce an attractive screen. The work that matters is everything around it — the research that proved it was the right screen, the states nobody asked for, the system that makes the next twenty consistent, and the QA pass that makes the shipped version match the file.
How I work
Six phases, the same order every time. A tight deadline changes the depth of each phase — never whether it happens.
Business goals, user problems, constraints and success metrics — captured before anyone opens Figma.
Flows, information architecture and low-fidelity wireframes. Cheap to change, brutal at exposing gaps.
High-fidelity UI, a clickable prototype, and usability sessions that decide what changes before build.
Tokens, components, annotated handoff, design QA on staging, then iterate on what real usage shows.
Why work with me
None of this is exotic. It is just what happens when a designer treats the build as part of their job.
Empty, loading, error, offline, no-permission, first-run, too-much-data. Engineers stop inventing screens at 2am, and QA stops filing tickets about them.
Even on a two-week timeline there is room for five user interviews and a competitive teardown. That week of research usually removes a month of rebuilding.
Handoff is not a Figma link and a wave goodbye. I stay through the build, review the staging environment and do a design QA pass before release.
Everything ships as tokens and components. The tenth screen takes a fraction of the time the first one did, and the twentieth still looks like the same product.
Contrast, tap-target size, focus order, labels and text scaling get checked while designing — not retro-fitted after an audit fails.
Every meaningful decision comes with the why: the user problem it solves, the alternative that was rejected and how we would know if it worked.
Client feedback
Attributed by role — names are added only once each client agrees to be referenced publicly.
He asked harder questions in the kickoff than we had asked ourselves in three months of planning. Half the features we thought we needed never made it into the design, and the product is better for it.
Our engineers stopped filing 'what happens if this is empty' tickets. Every state was already designed and annotated. That alone took a week out of the sprint.
The usability sessions changed our roadmap. Watching five people fail at the same step was more persuasive than any deck could have been.
Design notes
Short pieces on craft, research, systems and designing for AI — written for the people who have to build the thing.
The difference between a design that ships smoothly and one that generates a hundred build questions is rarely the main screen. It is the eleven states nobody drew.
12 July 20266 min readResearchYou do not need a research department. You need five people, a prototype and the willingness to be told you were wrong.
3 June 20265 min readDesign SystemsMost design systems fail the same way: a beautiful component library that nobody knows when to use. Rules are the product.
21 April 20267 min read“A screen is finished when someone who has never seen the product can complete the task without asking a question. Everything before that is a draft.”
Send me the problem — not a spec. I will tell you honestly whether design is the right lever, and what I would do first.
madnansakhi@gmail.com