Find the live question.
We identify the moment, pressure and person behind a request. A feature name alone rarely tells us what should happen next.
Mobile product development
Sodureqavi designs mobile product surfaces around the decisions people make while moving. We turn a vague feature request into a clear signal: what someone needs now, what can wait, and what must remain understandable after the handoff.

01 / Route notes
A product route has to fit the person holding the phone, the information arriving late and the team maintaining the work. We make those agreements visible before treating a screen as finished.
We identify the moment, pressure and person behind a request. A feature name alone rarely tells us what should happen next.
We organise hierarchy, language and feedback around the action that matters now, without hiding the information needed to decide.
State, uncertainty and recovery are part of the product. The person should not have to start over just because a small condition changed.
02 / Product question map
The right question changes as a product moves from first contact to everyday use. These prompts keep the work specific enough to test and calm enough to understand.
What is already true for the person arriving here? Start with their setting, not a blank ideal journey.
What can be read in one glance, and which detail deserves a slower moment of attention?
What needs to remain visible so the person can trust what changed and safely find their way back?
03 / Studio shelf
A mobile experience is not only pixels on glass. We use objects, flows and real interaction contexts to test how the product behaves when attention is partial, fingers are busy or the question shifts.




04 / Field test
Lens / Arrival
We look at the first useful detail, the label that feels familiar and the point where a person can safely continue. Arrival is working when the product does not ask the person to learn its private structure before making an ordinary move.
05 / Surface checks
Confirm a practical outcome in a way that can be read quickly and revisited later, instead of leaving people to infer whether their action worked.
Errors, interrupted steps and uncertain inputs should not make the person feel punished for using a mobile product in a real environment.
Give people a way to return to a choice, inspect context and continue with confidence when a route gets interrupted.
06 / Handoff clerk
The team should inherit a usable record: what was tested, where the product is still uncertain and what to check when the next release changes the route.

07 / Questions
08 / Open a product note
Share a context, route or product moment that needs a clearer next move. This form stays in your browser and does not send a message.