Glance
One piece of orientation: status, next appointment, saved draft or simple confirmation.
PANTRY DOOR / MOBILE APP DEVELOPMENT
Every screen
should earn
its ingredient.
Mobile products for ordinary repeated tasks: made with fewer, clearer decisions so a person can get the useful thing done and return to their day.
Open the pantrySERVICE / 01
01 / INGREDIENT COUNTER
Start with what
the person needs
to do.
An interface is easier to make when its ingredients have a clear role. Choose one to see what it contributes to a complete mobile task.
02 / ONE-PLATE FLOW
Serve one
complete task,
not a buffet.
A useful mobile flow gives a person a clean plate: enough context to choose, a direct action, an understandable state and a practical finish.
- 01Arrive
Show the point of the task before the person has to search for it.
- 02Choose
Offer the smallest meaningful set of choices and make the consequence clear.
- 03Finish
Confirm the result, show the relevant state and give a calm exit or return.
03 / PORTION CARDS
The right
amount of
interface.
Short task
One action with a small choice and a clear end. It should survive a busy hand and a changing attention span.
Careful task
More context, disclosure and review—but still divided into legible portions with a useful escape route.
04 / GESTURE KITCHEN
Let touch
feel like a
choice.
Move the portion dial to see how a touch interaction can remain discoverable while still respecting the space and attention of a small screen.
TAP / DIRECT AND NAMED
Use a clear label and a comfortable target when the action matters. A tap earns trust when the person can predict what it will do.
05 / MESSAGE MENU
Make the
state easy to
swallow.
06 / ACCESSIBLE TABLE
Invite more
people to the
table.
Accessibility is not a garnish. It affects the order of focus, the confidence of a tap, the clarity of a message and whether an ordinary mobile task remains possible for someone with a different way of seeing, touching or concentrating.
- Keep labels explicit and state changes understandable.
- Make tap targets comfortable and visually distinct.
- Test with assistive technology and the actual task context.
07 / REPAIR SHELF
Put friction
where the team
can see it.
The task contains too many steps.
Separate a necessary review from a repeated setup request. Keep the person’s prior choices visible so a short task does not become an exercise in filling the same details again.
The error language says nothing useful.
State what happened, whether work was preserved and the safest next action. A generic error notice is rarely enough context for a person to recover confidently.
A useful feature is difficult to discover.
Return to the task moment. A feature can be visible yet still be misplaced, unnamed or irrelevant to the person’s immediate intent.
08 / FAQ RECIPE BOX
Answers for
the product
being made.
Define one end-to-end task with a tangible outcome and test its normal, interrupted and return states. If a screen cannot support that task without a second unfinished idea, keep the second idea for a later portion.
It has a clear contribution to the person’s task: it orients, enables, confirms or supports a return. Decorative complexity and duplicated choices do not become useful simply because they are familiar in other products.
Start with the state, then give the next useful action. Add more explanation only when it changes a person’s decision or ability to recover. Plain, specific language is usually shorter than a vague generic message.
At the beginning, when the task, audience, devices and conditions are being defined. It affects information order, content, interaction and error handling—decisions that are costly to revise once a finished interface exists.
09 / SERVICE ORDER
Bring the
next task to
the counter.
Bring a product concept, a repeated task that has grown difficult, a release that needs clearer ingredients or a mobile interaction that needs to work with more care.
10 / KITCHEN LIGHT