MoRo is a tablet app that helps families run daily routines, parents create and assign tasks, while children follow them independently through a simplified, accessible interface. I took it end-to-end: from user interviews and journey mapping, through wireframes and prototyping in Figma, to a working MVP. The core design challenge was serving two very different users on the same device: a management view for parents and a stripped-back and large-target mode for children with accessibility and clarity built in from the start.
UX designer & MVP Developer
April 2026 - ongoing
Figma, AI-assisted development, Claude Code, Vercel
User interviews, competitor analysis, persona, user journey map, wireframes, prototyping, usability testing, MVP development
User research, problem definition, information architecture, wireframing, prototyping, usability testing, UI design, AI-assisted MVP development, iteration planning.
Parents often spend a large part of the day reminding children about simple routines: brushing teeth, getting dressed, packing school items, completing chores, and preparing for bedtime.
For children, these routines can feel repetitive or unclear. For parents, constant verbal reminders create stress and take mental energy. Many existing task-management apps are designed for adults and are too complex, text-heavy, or not engaging enough for younger children.
The core problem I identified was:
Families need a simple, shared, and child-friendly way to manage daily routines so that children can complete tasks more independently and parents can reduce the need for constant reminders.
The goal of MoRo was to design and build a visual routine-management app for families that allows parents to create daily tasks and children to follow them with minimal guidance.
The product needed to be:
Simple enough for children to understand quickly
Useful for parents managing multiple daily responsibilities
Visual and engaging without being distracting
Flexible enough for different family routines
Clear enough to support independence and reduce repeated reminders
"How might we help busy families coordinate daily routines in a way that gives children more independence and reduces the need for constant parent reminders?"
User Interviews
I interviewed three families to understand how they currently manage daily routines, chores, and reminders at home.
The interviews focused on:
How parents organize daily routines
Which moments create the most stress
How children respond to reminders
What tools families already use
What makes an app easy or difficult for children
Competitive Analysis
I reviewed three existing to-do list and routine-management applications to understand common patterns and gaps.
The main findings were:
Most tools are optimised for adult productivity, not family collaboration
Child-oriented apps are often playful but limited in planning functionality
Few products balance parent control with a child-friendly daily view
Many interfaces rely too much on text and small tap targets
This helped define the opportunity for MoRo: a family routine app with a parent management view and a simplified child mode.
Persona & User Journey Map
Problem statement: Maria is a busy, organized parent of three with a demanding career who needs a simple, kid-friendly way to manage daily routines and coordinate schedules because she’s tired of constant reminders, missed tasks, and juggling too many tools to keep her family on track.
Maria’s user story: As a busy parent managing a full-time job and three kids, I want to create and share daily routines that my children can follow independently, so that I can reduce constant reminders, stay organized, and ensure the whole family is in sync—even when I’m not home.
Ideation
Based on the research, I focused on two main user experiences:
Parent view:
A management interface where parents can create, edit, assign, and review family tasks.
Child mode:
A simplified interface where children can see their own tasks, understand what needs to be done, and mark tasks as complete.
Morning, afternoon, and evening task sections
Visual completion checkboxes
Task assignment to specific family members
Rewards or positive reinforcement
Calendar or week view for upcoming tasks
Simple navigation between chores, rewards, child mode, and settings
Paper Wireframes
I started with paper wireframes to explore layout options quickly and focus on structure before visual design.
The main design question was how to make the interface useful for parents while keeping the child experience simple and focused.
The early sketches explored:
Task cards grouped by time of day
Large tap areas for children
Sidebar navigation for parent controls
A clear distinction between parent and child views
Simple progress and completion states
Digital Wireframes
After testing the basic structure on paper, I moved into digital wireframes in Figma.
The digital wireframes focused on:
Creating a clear dashboard for routine management
Making task cards readable and easy to scan
Using large controls for child interactions
Separating planning actions from completion actions
Keeping navigation simple and predictable
Design decision:
I grouped tasks into Morning, Afternoon, and Evening sections because families usually think about routines by moments of the day rather than by abstract task categories.
I created a separate child mode to reduce complexity and avoid showing children settings, editing controls, or parent-level actions.
The MoRo app prototype was designed as a tablet-based task management system tailored for children and families. The primary goal was to create an intuitive interface that supports task scheduling, rewards, and parental control, promoting responsibility and motivation for younger users.
Role-based Assignment: Tasks can be assigned to multiple family members, promoting collaborative participation.
Child-friendly Interface: The layout uses clear sections (Morning, Afternoon, Evening tasks) and bold visual cues for task completion. In this view, users can observe their assigned tasks and mark them as done by tapping completion checkboxes.
Gamification Elements: Integration of a rewards system to encourage task completion through positive reinforcement.
Accessible Navigation: Sidebar navigation allows quick access to Chores, Rewards, Child Mode, and Settings.
I conducted a usability test with one adult and two children aged 7 and 9.
The goal was to evaluate whether both parents and children could understand the main flows and complete core actions with minimal guidance.
Testing goals:
Assess ease of use for both parent and child views
Observe task creation, editing, and task completion interactions
Identify any usability challenges or confusion points in the navigation and task flow
Check whether children understood how to mark tasks as complete
Evaluate whether the visual hierarchy supported quick understanding
Key Observations:
Children understood the task completion flow: Both children were able to identify their tasks and mark them as completed
Parents understood task creation and editing. The parent participant was able to create and edit tasks without major confusion
Navigation required minimal guidance. Users were able to move between the main views with limited support
Visual grouping helped comprehension. Morning, Afternoon, and Evening sections made the routine easier to understand
Insights for improvement:
Slight adjustment to icon size and spacing in the child mode for better touch accuracy
An additional confirmation step is considered for task deletions in the parent view to prevent accidental removal
Introduce navigation through weekdays or a calendar view to allow users to see upcoming tasks for tomorrow or specific days
After validating the core idea through the prototype, I built an early functional MVP to test the routine-management experience in a working web app.
The MVP helped me move beyond static screens and explore how the product feels when tasks can actually be created, viewed, and completed.
What I built:
A functional MVP of MoRo based on the tested prototype, focused on daily routine tracking, child-friendly task completion, and family task visibility.
Why I built it:
To validate whether the core flow works beyond static prototypes and to practice turning UX decisions into a working product.
Next Steps
The next iteration of MoRo will focus on improving usability, planning, and product completeness.
Planned improvements:
Increase icon size and spacing in child mode
Add confirmation before deleting tasks
Add week and calendar navigation
Improve onboarding for parents
Refine the rewards system
Test the MVP with more families
Improve mobile responsiveness
Add clearer empty states and error states
This project helped me understand how important it is to design for different users within the same product. Parents need control and flexibility, while children need simplicity, clarity, and motivation.
I also learned that a working MVP can reveal questions that are difficult to see in a static prototype, such as how task creation feels over time, whether the flow remains simple in daily use, and which features should be prioritised next.
The project strengthened my skills in UX research, prototyping, usability testing, and AI-assisted product development.