Three phones showing the KinSync app: home timeline, splash screen and the paywall, over a chevron pattern

KinSync APP

  • MOBILE APP
  • 2026

Overview

Role
Product Designer
Platform
IOS & Android
Timeline
7 weeks, February 2026
Deliverables
User Research, User Interviews, Journey Map, Competitive Analysis, User Flow, Paper Wireframes, Low & High Fidelity Prototypes
Overview

KinSync started with a personal problem.

As a parent, I constantly found myself trying to keep track of my child’s ever-changing schedule. School, extracurricular activities, appointments, pickups.... it quickly became too much to manage with scattered notes and calendar reminders. I wanted a simpler way to organize everything in one place while also receiving timely reminders and accounting for real-world factors like traffic and travel time.

After talking to other parents, I realized this wasn’t just my challenge, it was a shared frustration. Many families struggle to coordinate busy schedules and ensure everyone is where they need to be, on time.

That insight became the foundation for KinSync. This app designed to help busy families manage schedules, coordinate responsibilities, and reduce the mental load of everyday family life.

Final Screens

Let’s see how I got here

The Challenge

Problem Framing

Busy families manage a constant flow of school, extracurricular activities, appointments, and shared responsibilities. Many parents rely on a combination of calendars, notes, and messages to stay organized, making it easy to miss important details or last-minute changes.
Through conversations with other parents, I realized this was a common challenge. The problem wasn’t just keeping a schedule, it was reducing the mental load of coordinating everyday family life while staying on top of reminders, travel time, and unexpected delays.
This revealed an opportunity to design a smarter family coordination experience rather than just another calendar app.

Pinpointing Issues

  1. Scattered information

    Schedules, reminders, and notes are spread across multiple apps and conversations.

  2. Coordination challenges

    Keeping parents and caregivers aligned on pickups, drop-offs, and schedule changes is difficult.

  3. Missed reminders

    Busy routines make it easy to forget activities, appointments, or last-minute updates.

  4. No travel awareness

    Traditional calendars don’t account for traffic, travel time, or when it’s actually time to leave.

The Goal

Create an intuitive family coordination experience that helps busy families stay organized, reduce mental load, confidently manage daily schedules, reminders, and transportation.

HOW MIGHT WE’S?

  • How might we reduce parents’ mental load?
  • How might we improve family coordination?
  • How might we prevent missed activities?
  • How might we help families stay on time?
Line illustration of a parent sitting on a stool, phone in hand, with a thought bubble that reads “How?”

Research Process

The research phase included user interviews, journey maps, empathy maps, user stories, goal statements, and a competitive analysis. To keep this case study focused and easy to navigate, I’ve highlighted only the key insights and decisions that shaped the product.

User Interviews

I conducted interviews with five parents to learn how they currently manage their children’s schedules, what creates the most stress, and where existing tools fail to support them.

User interviews — synthesis board for five parents

Key Takeaways

The main problem was not a lack of scheduling tools. It was the mental effort required to connect schedules, responsibilities, reminders, and transportation across multiple platforms.

Journey Maps

I created an individual journey map for each participant to understand how they moved through a typical day: from receiving activity information to planning transportation, coordinating pickups, and responding to unexpected changes.

Journey maps — user stories for Jacob, Anna, Binisha, Lian and Sasha

Key Takeaways

The most stressful moments happened between activities, not during them. Parents needed support before an event, when coordinating responsibilities, calculating travel time, and deciding when to leave.

Competitive Analysis

Most competitors provided strong basic calendar functionality. Some supported shared schedules or family communication, but important gaps remained:

  1. Scheduling & Transportation

    Treated as separate tasks.

  2. Family Coordination

    Often required additional messaging tools.

  3. Reminders

    Usually based only on the event start time.

  4. Traffic-aware departure planning

    Was limited or unavailable.

Competitive analysis — Family Wall, Tiny Calendar, Cozi

Research Outcome

The research confirmed that the original problem was shared by other families, but it also expanded the initial product idea.

KinSync evolved from a simple activity scheduler into a family coordination tool designed to:

  • Bring schedules and responsibilities into one place
  • Reduce repeated communication between caregivers
  • Help families prepare for activities before they begin
  • Account for travel time and unexpected delays
  • Reduce the cognitive burden of managing everyday family life

These findings became the foundation for feature prioritization, information architecture, and the core user flows.

Paper Wireframes

Before moving into digital wireframes, I explored early concepts through paper prototypes. This allowed me to quickly visualize user flows, test different layouts, and iterate on ideas without being constrained by visual design.

  • Paper wireframes — sketch 1 of 6: splash, onboarding and create account

  • Paper wireframes — sketch 2 of 6: family space setup and invites

  • Paper wireframes — sketch 3 of 6: home dashboard and flows A, B, C

  • Paper wireframes — sketch 4 of 6: calendar, event and tasks screens

  • Paper wireframes — sketch 5 of 6: kid’s mode tabs

  • Paper wireframes — sketch 6 of 6: caregiver mode tabs

Low-Fi Wireframes

Using insights from the research and paper prototypes, I translated the initial concepts into low-fidelity wireframes. This stage focused on defining the information architecture, refining user flows, and validating the placement of key features before investing in visual design.

The low-fidelity prototype allowed me to validate navigation, refine task flows, and quickly iterate on the product structure before investing in visual design. This stage ensured the experience was intuitive and aligned with the research findings.

Key Features Explored:

  • Family dashboard
  • Weekly calendar
  • Activity details
  • Shared responsibilities
  • Smart reminders
  • Traffic-aware departure planning
  • Low-fi wireframe — Parent flow 2.1

  • Low-fi wireframe — Parent flow 2.2

  • Low-fi wireframe — Home 4.0 events

  • Low-fi wireframe — Home 4.3 calendar

  • Low-fi wireframe — Home 4.6 event details

  • Low-fi wireframe — Home 4.9 selected dates

  • Low-fi wireframe — Home 4.9 selected dates, second variant

  • Low-fi wireframe — Events 5.2 flexible

  • Low-fi wireframe — Events 5.2 flexible, second variant

  • Low-fi wireframe — Events 5.7 end time selected

  • Low-fi wireframe — Events 5.1.7 location selected

  • Low-fi wireframe — Tasks 6.0 add task

  • Low-fi wireframe — Tasks 6.9 custom reminder

  • Low-fi wireframe — Tasks 6.1.5 filled

  • Low-fi wireframe — Calendar 7.6 filters applied

  • Low-fi wireframe — Calendar 7.2 delete or dismiss

  • Low-fi wireframe — Calendar 7.0 default view

  • Low-fi wireframe — Messages 8.9 group created

  • Low-fi wireframe — Messages 8.5 chat

  • Low-fi wireframe — Events 5.3 important

  • Low-fi wireframe — Messages 8.1.0 updates

Design System

Before designing the final interface, I established a lightweight design system to ensure consistency, scalability, and efficiency throughout the product.

Building the design system early allowed me to focus on solving UX problems instead of repeatedly designing the same UI elements.

Key Elements

  1. Color palette & design tokens
  2. Typography scale
  3. Buttons & form controls
  4. Navigation components
  5. Cards & Lists
  6. Icons
  7. Spacing & layout guidelines
  8. Reusable components & variants
Line illustration of a designer pointing at a whiteboard titled “Design System”

High-Fidelity Prototype

With the core user flows validated and the design system in place, I transformed the low-fidelity wireframes into polished, interactive interfaces. Every design decision was grounded in the research findings and aimed at reducing cognitive load while making everyday family coordination simple and predictable.

Reflections

Key Takeaways

  • Prioritized the most important actions
  • Minimized taps for common tasks
  • Created reusable interaction patterns
  • Used progressive disclosure principles
  • Used color to reduce cognitive load
  • Designed with accessibility in mind

Next Steps

Although KinSync is currently a concept, the design process doesn't end with the final prototype. The next phase would focus on validating the product with real families through usability testing and refining the experience based on their feedback.

Future iterations would include expanding collaboration features, enhancing smart reminders with real-time traffic insights, and integrating with school and activity management platforms. As the product grows, the design system would continue to evolve, ensuring a consistent, scalable, and user-centered experience.

This project reinforced the importance of designing with empathy, validating assumptions through research, and continuously iterating to create solutions that genuinely improve everyday life.

Thank you for taking the time to explore this case study !

LET'S TALK

And make something meaningful.

Say hi

Thanks for scrolling all this way ✦