Shared plans. Personal space.
From personal planning to partner suggestions: a mobile product for two people coordinating their day.
Keep my day organized. Coordinate with one other person.
Toochi started with a coordination need a colleague and I encountered in our daily collaboration: sharing plans while keeping our own work organized. I shaped the first product around that two-person relationship.
Two people need to coordinate work while retaining control of their own plans.
A proposal becomes a personal task only after the recipient accepts it.
Product specification, a documented refinement and working app screens. Real-user pilot underway.
- My role
- Co-founder · Product & UI/UX Designer.
- My contribution
- Product structure, user flows, interface design and refinement through successive builds.
- Collaboration
- Design and development worked together to turn the product into a mobile PWA.
- Stage
- Working product · currently in real-user pilot testing.
Two collaborators with personal tasks and shared commitments.
Study or language partners may share this need. For the first product, the focus remains one-to-one coordination.
A suggestion becomes a commitment only when the other person accepts.
I designed the shared interaction around proposing work. A suggestion stays separate from a task until the recipient accepts it. Acceptance creates a task in the recipient's own plan; declining leaves the suggestion as a recorded response.
Selected interaction flow, redrawn from the product specification.
Acceptance adds a step, but it prevents a proposed task from silently becoming someone else's obligation. Personal planning also works while a partner invitation is pending.
Sharing has more than one level.
Separate controls let a person allow their partner to view non-private tasks, suggest work or edit non-private tasks. The private-task boundary is stated directly beneath the controls.
Interface detail: each permission explains what the partner can do, followed by an explicit Save changes action.
Three independent permissions: view, suggest and edit. Private tasks remain visible only to their owner.Tap image to inspect ↗
A suggestion crosses between two personal plans.
The task “Content creation planning” connects the pending suggestion, review screen and recipient’s Today view. These product screens make the handoff visible: a proposal first, then a decision, then a task the recipient can manage.
The progress state says the suggestion and prepared files are being submitted. It asks the sender to keep the page open until the operation finishes.Tap image to inspect ↗
The recipient’s Partner page separates the pending incoming suggestion from the partner’s own daily schedule. “Content creation planning” is marked as waiting.Tap image to inspect ↗
The recipient can inspect the sender, task, date, category and priority before choosing. Accept and Decline are explicit actions at the bottom.Tap image to inspect ↗
“Content creation planning” appears among the recipient’s Today tasks, labelled as suggested by Mohi, with completion, edit and delete controls.Tap image to inspect ↗
The task retains a visible connection to the person who suggested it. The recipient can understand its origin without leaving their daily list.
The partner’s mood and suggestion action occupy one compact card. Accepted work is managed alongside the recipient’s other tasks.
System feedback · suggestion notifications
Make the response visible.
The notification list distinguishes a new suggestion from an accepted one, using a message icon and a confirmation icon alongside text.
This screen shows multiple notification events; it illustrates the feedback pattern separately from the task sequence above.
“New suggestion” and “Suggestion accepted” communicate different events through text and icons.Tap image to inspect ↗
Today needed partner context without becoming a second partner page.
The early prototype centered on Today and Add Task. The Phase 1 refinement brief identified a missing partner mood/status card and specified where it belonged in the hierarchy.
Add the partner card after the greeting and before today's tasks, with mood, optional note and a last-updated cue.
Keep it compact and consistent with the existing design system. Preserve the approved task cards and their visual priority.
Step 04 above shows the current Today screen, with partner context above the recipient’s personal tasks.
Inspect the accepted task on Today ↑Context fits into the daily routine.
The product screen shows the partner information as one compact block. It gives the relationship a place on Today while leaving the personal task list as the main working area.
This was a design refinement during development. The current pilot is where its usefulness in daily coordination is being explored.
The Calendar specification reused Today's task-card component and ordering. Moving between a day view and a month view should not require learning a second way to read or act on a task.
A working product, now being tested in everyday use.
The selected date leads directly to its tasks.
The month and daily list remain connected, while the task cards carry the same actions and visual language used on Today.
Evaluate the handoff, the permissions and the return visit.
Ask one person to suggest a task and the other to accept it. Observe whether it appears in the recipient’s plan without help; repeat with a declined suggestion and check both people understand the status.
Before revealing the settings, ask each person which tasks their partner can see or change. Record mismatches between expectations and permissions, especially private tasks.
Across repeated use, note whether pairs return voluntarily and follow through on accepted tasks. Ask what caused abandoned suggestions or a return to their previous coordination method.
These are evaluation questions for the pilot; findings will be added as they are collected.
One relationship shaped the whole product.
Toochi grew from a need in our daily collaboration into a working mobile PWA. I shaped the product structure and interaction model around one principle: shared coordination should fit into a person’s own plan. Personal tasks, partner permissions, suggestions and the calendar now form one daily experience.
Separate a suggestion from a commitment. The recipient's acceptance gives the task a clear owner and a place in their own plan.
Does this extra control feel helpful or slow in real use? Pilot observations should determine where the flow needs to become simpler.
Explore Toochi.
Visit the product website to learn more and find the app.
Visit toochi.ir ↗