Case studyAssignmentNoise Junior

Redesigning Noise Junior around daily readiness.

A recruiter reached out with a design assignment for the Noise Champ 3 companion app. I treated it like a real product problem: understand the parent-child split, audit the current product, use public reviews as research signals, and redesign Home and Routine around trust, sync and child ownership.

Noise Junior case study hero slide from the assignment deck

Context: Recruiter assignment
Product: Noise Junior
Focus: Home and Routine
Date: July 2026

Full Figma case study deck

The complete assignment lives in Figma with the original screens, audit notes, research signals, redesign explorations and final presentation flow.

Problem

Noise Junior had the right ingredients, but the experience felt like a list of features. Parents still had to work out whether the child's watch was ready for the day.

Move

I reframed the app around readiness, sync clarity, routine progress and child ownership instead of treating every feature as equal.

Output

A redesign direction for Home and Routine: the parent prepares the day, the child owns the watch experience, and the app makes trust visible.

Product lens

Prepared by the parent. Owned by the child.

Noise Junior is not just a smartwatch app. It is a parent-controlled setup layer for a child's first personal gadget. The phone app belongs mostly to the parent. The watch experience belongs to the child.

That split shaped the redesign. The parent needs calm, control and readiness. The child needs ownership, rewards, progress and a watch that feels like theirs.

For parents

My child's watch is ready for the day. Routines are synced, safety info is present, and anything pending is easy to see.

For children

This is my first grown-up device and it feels like mine. I complete tasks, earn rewards, unlock progress and build small habits.

Problem framing

The issue was not missing features. It was missing focus.

The current app already had routines, health, safety, challenges, EduCards, badges and coins. But Home behaved more like a feature catalogue than a daily helper.

Parents do not open this kind of app to admire modules. They open it to answer a few fast questions: is the watch ready, did today's routine sync, is anything pending, and what should my child do next?

Current Noise Junior app design audit section from the Figma assignment — The current app already had many useful modules. The problem was hierarchy: everything competed before the parent could answer the basic readiness questions.

Research signals

I used public reviews as directional research, not absolute truth.

I did not have live users or the full watch ecosystem for this assignment, so I reviewed public feedback from app stores, marketplaces, videos and discussions. The pattern was consistent enough to guide the redesign.

Parents buy reassurance, not features

The strongest signal from public reviews was not excitement about individual modules. Parents wanted to feel informed and confident.

Simplicity was already a strength

Users often described the app as simple or easy. The redesign needed better priority, not extra complexity.

Trust breaks when basics fail

Pairing, login, sync and task completion problems quickly become UX problems because parents stop trusting the information on screen.

Sync needed to be visible

Because the watch depends on Bluetooth sync, states like pending sync, last synced and ready on watch had to move into the main experience.

Design principles

Simple rules before screens.

Reassurance before exploration

Make sync visible

Interpret before showing data

Parent prepares, child completes

Routines should feel like progress, not pressure

Delight should support clarity

Redesign direction

Home became a readiness dashboard. Routine became a habit flow.

Noise Junior Home redesign showing reassurance dashboard and design rationale — Home was redesigned as a reassurance dashboard. The first read answers whether the child is okay, whether the watch is connected, and what routine item is next.

Noise Junior Routine redesign section showing routine flow and rationale — Routine became a habit flow instead of a plain task list: next up, completed, pending sync and child reward moments are easier to read.

Noise Junior setup routine redesign section showing setup flow screens — Setup Routine shows how the parent creates structure while the child still gets a sense of ownership through icons, rewards and watch-ready states.

Key decisions

The redesign made trust visible.

Status-led Home

Home starts with the current watch state: ready, away, low battery or pending sync. This gives the parent one clear read before they scan feature cards.

Device trust signals

Battery, last synced and routines ready on watch sit close to the hero state. They are small details, but they decide whether the parent believes the screen.

Routine as a daily story

Routine became a timeline of what is done, what is next, and what is waiting to sync. It feels more like the child's day moving forward.

Meaning before metrics

Instead of only showing steps, heart rate and active minutes, the design first interprets the state: Mihir is active and doing well.

Transparency

What I would validate next.

This was an assignment, not a shipped project. I did not have access to internal data, live parent interviews, engineering constraints, or the full watch-side behavior.

If this moved forward, I would treat the design as a strong hypothesis and validate these areas first:

Test the readiness language with parents.

Validate whether children understand rewards and routine ownership on the watch.

Pressure-test Bluetooth sync states with engineering constraints.

Design the watch-side companion moments, not only the phone app.