Daddy & Me —

Closed-loop tablet and phone for long-distance dads

Impact

Two devices, one bond: a world a child can explore alone, and an app for Dad to see how they feel and talk together.

Platform

Mobile & Tablet

Category

Consumer Apps

Industry

Family & Wellbeing

Country

United Arab Emirates flagUnited Arab Emirates

Completed

— In Development

Designed both halves of a two-device product — a docked tablet for the child, a mobile app for the dad — and one design system built for both screens at once.

Platform

Mobile & Tablet

My Role

Lead Product Designer — sole designer on the engagement

Collaborators

1 Product Designer, 1 Founder & 2 Investors

Timeline

Q2 2026 — Q3 2026

Scope

Product Strategy, UX & UI Design, Illustration Direction, Gamification, Prototyping, Design System

Organization Size

Early-stage startup

Goals

Designing presence, not another messaging app

The founder arrived with a concept document and no screens: a tablet that stays docked in the child’s room and a phone app for the dad, built as a closed system — no internet, no external contacts, one relationship per device. The hard part was never the feature list. It was that the child has to want to open it, unprompted, on a day when nothing has happened — and be able to use it with no adult in the room.

Project Goal

Give a separated father and his child a shared place that holds the relationship between calls — usable by a four-year-old alone, and honest about how his child feels.

Main OKRs

Make the child experience operable without reading or typing, so a four-year-old can use the tablet without an adult present.

Turn emotional check-ins into a daily ritual, by making them a single gesture that asks nothing back.

Give calls a reason to keep going, with structured activities built into the call itself rather than offered beside it.

Keep engagement tied to the father, not the app, so every reward traces back to a real exchange between them.

Research

Five hard questions, written down before I started

There were no users to observe yet — the product didn’t exist. The founder’s brief defined five design challenges: keeping actions simple, acknowledging feelings naturally, engaging without creating dependence, easing calls, and building routines without pressure. I used that brief and its references — Tamagotchi and Animal Crossing — to explore companionship, play, and routine. Every design decision for Daddy & Me traces back to those five questions, rather than to user research I hadn’t conducted.

User Challenges

The child can’t be taught the interface, because there is no onboarding a four-year-old will sit through and no copy they can reliably read.

Acknowledging a feeling can easily slide into analysing it, because any follow-up question turns a child’s answer into a form they’re filling in.

Engagement mechanics risk competing with the person they exist to serve, because a streak or a login reward makes the app the thing worth returning to.

A call with nothing in it collapses into the loop the product exists to fix, because “how was your day?” is what happens when neither side has a reason to keep going.

Final Design

The first thing on screen is his child

The dashboard opens on one sentence about their child — how they feel, under the time of the last check-in — with the next call, a Start Call button and the day as it happened beneath it.

Led with the child’s state in plain language, so the screen answers the only question a parent opens the app to ask.

Put the next call one tap from the top, with its date, time and both avatars attached to it.

Kept the streak in the header, not the centre — it measures the relationship rather than scoring the parent.

Final Design

The first thing on screen is his child

The dashboard opens on one sentence about their child — how they feel, under the time of the last check-in — with the next call, a Start Call button and the day as it happened beneath it.

Led with the child’s state in plain language, so the screen answers the only question a parent opens the app to ask.

Put the next call one tap from the top, with its date, time and both avatars attached to it.

Kept the streak in the header, not the centre — it measures the relationship rather than scoring the parent.

Final Design

A room to walk into, not a home screen to learn

The child’s home is a rendered living room where every affordance is an object: a gift on the shelf sends a present, a badged envelope holds messages, the easel opens drawing. No buttons, no labels, nothing to read first.

Removed the menu entirely by making every action a physical object a four-year-old already recognises.

Kept Dad on the screen at all times, so the room is never empty on a day he hasn’t sent anything.

Carried all four engagement states in one variable — the child’s own posture — instead of dimming the room or adding a warning colour.

Final Design

A room to walk into, not a home screen to learn

The child’s home is a rendered living room where every affordance is an object: a gift on the shelf sends a present, a badged envelope holds messages, the easel opens drawing. No buttons, no labels, nothing to read first.

Removed the menu entirely by making every action a physical object a four-year-old already recognises.

Kept Dad on the screen at all times, so the room is never empty on a day he hasn’t sent anything.

Carried all four engagement states in one variable — the child’s own posture — instead of dimming the room or adding a warning colour.

Final Design

Calls that arrive with something to do

The call is the container: drawing and guessing games run inside it, and AI reads their chat history for prompts so neither of them has to start from “how was your day”.

Built the activities into the call, not beside it, so a father can draw or play with his child while they are still talking.

Used AI to read their chat history for topics, so a conversation has somewhere to go instead of running in a straight line.

Designed every call state twice — ringing, connected, no-answer and each activity — once on the phone and once on the tablet.

Final Design

Calls that arrive with something to do

The call is the container: drawing and guessing games run inside it, and AI reads their chat history for prompts so neither of them has to start from “how was your day”.

Built the activities into the call, not beside it, so a father can draw or play with his child while they are still talking.

Used AI to read their chat history for topics, so a conversation has somewhere to go instead of running in a straight line.

Designed every call state twice — ringing, connected, no-answer and each activity — once on the phone and once on the tablet.

Final Design

The child picks the version of themselves that matches

The check-in asks how are you feeling now? and answers with the child’s own avatar, not an emoji — four options below, one large figure above, and a reply in their own voice: I feel angry.

Put the child inside the picker, so choosing a feeling means finding yourself in it rather than decoding a symbol.

Wrote the confirmation in first person, so the screen reflects the feeling back instead of assessing it.

Held it to four states and one confirm, because a follow-up question turns a feeling into a form.

Final Design

The child picks the version of themselves that matches

The check-in asks how are you feeling now? and answers with the child’s own avatar, not an emoji — four options below, one large figure above, and a reply in their own voice: I feel angry.

Put the child inside the picker, so choosing a feeling means finding yourself in it rather than decoding a symbol.

Wrote the confirmation in first person, so the screen reflects the feeling back instead of assessing it.

Held it to four states and one confirm, because a follow-up question turns a feeling into a form.

Final Design

Reading the week, not the day

Insights opens on the whole week as one proportional chart — fine, happy, angry and sad sized against each other, with the check-in and missed counts above it. The day-by-day list sits underneath.

Led with the pattern rather than the incident, so one sad check-in doesn’t become a phone call the child didn’t ask for.

Reported missed check-ins beside the total, so the proportion can be trusted rather than assumed complete.

Kept the day-by-day detail directly below, because an acute bad day is exactly when a parent should be able to look closer.

Final Design

Reading the week, not the day

Insights opens on the whole week as one proportional chart — fine, happy, angry and sad sized against each other, with the check-in and missed counts above it. The day-by-day list sits underneath.

Led with the pattern rather than the incident, so one sad check-in doesn’t become a phone call the child didn’t ask for.

Reported missed check-ins beside the total, so the proportion can be trusted rather than assumed complete.

Kept the day-by-day detail directly below, because an acute bad day is exactly when a parent should be able to look closer.

Impact

Two devices, one complete handoff

The engagement delivered both platforms end to end — the child’s clubhouse, check-ins, gifts, chats and calls; the dad’s dashboard, insights, messaging, scheduling and call flows — on a shared component library, with annotated clickable prototypes for each device.

Around fifty screens across two platforms, covering four engagement states, six chat states and every call state on both devices.

Every call state designed twice — once from the tablet, once from the phone — so engineering received a matched pair rather than one screen and an inference.

Zero typed input anywhere in the child experience, with recording, tapping and drawing covering every action available.

Seven milestones delivered from visual direction through gamification, design system and annotated prototype handoff.

Reflection

What designing for a four-year-old takes away from you

This was the first project where most of my usual tools were unavailable — no copy to explain a control, no onboarding, no tooltips, no research programme. What’s left is whether the thing in front of the child is recognisable on sight.

A brief that names its own hard questions is a research artifact.

The founder had already written down the five things that would be difficult. Treating that as evidence rather than a wish list gave the project its spine.

Designing for small children removes your usual escape hatches.

No label, no onboarding, no tooltip. The interface has to be recognisable on sight, which is a far higher bar than learnable.

An empty state is a design position, not a fallback.

Keeping Dad in the room was the biggest call on the project — showing nothing until something arrives would have confirmed exactly what the child fears on a quiet day.

A shared streak is not a login streak.

It only advances when both people show up, so it measures the relationship rather than the child’s loyalty to an app. That distinction is the whole gamification argument.

Next ›

Mental Health Platform