Start with the hand.
We map one-handed use, attention, grip changes, sunlight, motion, and interruptions before polishing a screen.
Field kit / mobile product studio
Apps that hold up when life moves.
Dorunafeli designs and ships mobile products for teams whose customers are out in the world—not parked at a desk. We turn demanding journeys into calm, dependable hand-held tools.
Built for motion.iOS, Android & progressive web
Studio signalTaking one focused build brief
TerrainField, home, transit
CoverageOffline considered early
Primary instrumentThe phone in a hand
Response windowTwo working days
01 / field rulebook
A useful app earns its place in the pack.
A field guide is designed to be opened, marked up, and used again. We give products the same discipline: clear cues, durable decisions, and no ornamental detours.
Make the route visible.
We reduce every flow to its next trustworthy marker, so people know what happened, what matters, and where to go.
Plan for recovery.
Weak signal, stale data, lost context, and a changed plan are product conditions—not edge cases to defer.
The field notebook / evidence before opinionNotebook entry / 14Build method
Offline & online are one conversation.
A connection may disappear, but confidence should not. We make states understandable at a glance and make sync feel like a continuation, not a rescue.
Keep the essential job moving.
- Intent is saved on-device.
- Status stays honest without a signal.
Let the connection add capability.
- Fresh context appears without drama.
- Teams see the same route markers.
Show the next safe step.
- Conflicts are named in plain language.
- Nothing important vanishes silently.
02 / hand-position explorer
The screen is only half the interface.
Explore three common conditions. Each one changes the job of the UI—from reachability to readable feedback.
Walking / one hand
Place the primary decision inside the thumb arc; defer dense comparison until the user is still.
Route markerindex / 03
03 / route-marker index
Every state should point somewhere.
A good mobile flow feels less like a maze and more like a well-marked route. We set the visual language early, then make it carry real product meaning.
Position
Where am I, and what changed around me?
Decision
What is the single useful action from here?
Return
What can I revisit without starting over?
04 / task packer
Pack the smallest release that proves the trail.
Use this miniature release pack to see how we choose what belongs in a first field-ready slice. Check items and watch the pack settle.
Field readiness2 of 4 packed
05 / recovery compass
When plans change, show the bearing.
Mobile products are used between meetings, at the curb, in poor reception, and in moments that do not forgive ambiguity. We design recovery as a primary route.
- 01Name the situation
Use specific, human language instead of a generic failure label.
- 02Protect the work
Tell people what has been saved, queued, or needs their attention.
- 03Offer one calm next move
Keep the choice visible and the path back short.
06 / test-flight log
We test the route, not just the release.
01Signal check
Sketch in context
We take the smallest believable prototype to the actual moment of use and collect the language, workarounds, and hesitation it reveals.
02Route rehearsal
Make the journey repeatable
We turn observations into a compact flow, prototype its feedback, and tune the edges where attention and confidence get thin.
03Launch bearing
Ship with a learning loop
We identify what the first release must teach the team, then give the product enough instrumentation to answer without distracting its users.
What we bring to the table
A small senior crew, from first bearing to shipped build.
We partner with product teams who want a compact, deeply involved studio—not a handoff line. Strategy, UX, visual direction, prototype, and implementation decisions stay connected.
Clarity is a feature, especially under pressure.07 / working agreement
Close collaboration. Few grand gestures.
“The strongest mobile products respect the environment their customers are actually in.”
Dorunafeli works best with teams who have a consequential problem, access to the people living with it, and the will to make a clear first move. You work directly with the people doing the thinking and making.
2–3weekly working sessions
1shared decision trail
0throwaway theater decks
Dorunafeli is especially useful when a phone supports a meaningful task away from a stable desk: coordinating a service visit, documenting a place, guiding a member, managing a route, or making a time-sensitive decision. We can also help consumer products, provided the team wants to understand the context around the screen rather than simply add more features.
Yes. We often join an existing product and engineering group to clarify a problem, prototype a new workflow, establish a mobile design system, or shepherd a focused release. We make decisions visible in shared artifacts and work in the tools your team already trusts, so implementation knowledge accumulates instead of being trapped in a presentation.
We begin by identifying the smallest action that still needs to succeed when a connection is slow, interrupted, or absent. Then we describe what is stored locally, how the user can tell, what will synchronize later, and how conflicts are handled. The goal is not to pretend the network is always present; it is to keep people oriented when it is not.
A concise description of the people you serve, the moment they reach for their phone, and the consequence of getting that moment wrong is enough. Existing research, screenshots, analytics, or a prototype are welcome but not required. We will use the call to decide whether a short discovery, a prototype sprint, or a delivery partnership is the honest next step.
08 / dispatch card
Tell us where the route gets difficult.
Send a short note about the product moment you want to improve. We read every message and reply within two working days with a clear next step—or an honest reason we are not the right crew.
[email protected]