WhatsApp Messenger
Adding a Feature to an Application
Project Summary
Mission
Video calls have become a lifeline for families in general, and especially with loved ones living far away. Parents want their children to build real connections with grandparents, cousins, and friends across the world but those moments are often cut short by accidental screen taps, leaving both sides frustrated. This project set out to design a simple feature within WhatsApp that helps parents maintain uninterrupted video calls by freezing the screen, making it easier for families to stay present, engaged, and emotionally connected, no matter the distance.
The Problem
WhatsApp currently doesn’t offer a way to disable screen interactions during video calls, making it easy for babies and toddlers to end or disrupt the calls. While both iOS and Android provide system-level tools like Guided Access and App Pinning, they’re buried in settings and rarely used by the average parent. This created a clear disconnect between everyday needs and available tools.
The Solution
The goal was to design a “Child Lock” mode that fits naturally into WhatsApp’s interface, one that requires minimal setup, respects platform limitations, and feels frictionless to use. First-time users would feel guided and supported, while returning users would be able to activate the feature in a single tap. The entire experience was crafted to feel native to WhatsApp’s design language and thoughtful in its simplicity.
Timeframe
3 weeks (July 2025)
My Role
Product Designer
Skills
Research
User flows
Wireframing
Visual design
Prototyping
Usability Testing
Tools
Figma
Fig Jam
Maze
Starting with Research
Because this project involved designing a new feature for an existing product, the research focused on understanding which platforms people were already using for video calls, especially with young children. The goal was to explore real-world behaviors, preferences, and pain points, like how often kids interrupt calls or what workarounds parents currently use. This helped ensure the feature would be built where it was most needed and aligned with how users already interact with familiar tools like WhatsApp.
User Interviews
User interviews revealed valuable insights about how parents use video calls with young children, including common frustrations like accidental hang-ups and screen tapping. These conversations helped validate the need for a screen-freezing feature and shaped the direction of the design moving forward. The key findings are outlined below.
Competitor Analysis
To guide my design decisions, I conducted a competitor analysis that included both direct competitors, like all-in-one messaging apps, and indirect ones focused solely on kid-friendly video calls. This helped me strike a balance between broad communication tools like WhatsApp and specialized features built for child safety. I focused on identifying key components and interactions that could give WhatsApp an edge, making it even more accommodating for families and a wider range of users.
Who Are We Designing For?
To guide my design decisions, I conducted a competitor analysis that included both direct competitors, like all-in-one messaging apps, and indirect ones focused solely on kid-friendly video calls. This helped me strike a balance between broad communication tools like WhatsApp and specialized features built for child safety. I focused on identifying key components and interactions that could give WhatsApp an edge, making it even more accommodating for families and a wider range of users.
Bridging Research to Action
Project Goals
I paused to define what this feature really needed to achieve, for both parents using it and for WhatsApp as a platform. Since it was being added to an existing product, it had to strike a balance between solving a real user problem, supporting business goals, and working within technical constraints. Laying out these goals side by side helped guide every design decision that followed.
User Flow
With the project goals prioritized, it was time to begin bringing this feature to life.
To map out how people might use the new feature, I created a user flow chart. This helped me identify the key screens and interactions to include as I moved into wireframing.
Exploring the Flow
It was now time to begin bringing this feature to life.
To better understand how the feature would function within WhatsApp’s existing interface, I created a series of low- to mid-fidelity wireframes. This let me visualize the flow, play around with layout and interactions, and annotate ideas before moving into high-fidelity design.
Fitting it into the System
Before jumping into high-fidelity wireframes, I created a custom UI kit using WhatsApp’s visual language including pulling in colors, fonts, icons, and components that matched the existing product. This helped ensure the feature would feel native to the app, while also giving me a consistent system to build with.
Making it Real
With the foundation in place, I moved into high-fidelity designs to bring the feature to life within WhatsApp’s interface. These screens reflect the final visuals, interactions, and component choices, staying true to the platform while introducing a new layer of functionality.
*While “swipe to unlock” was used in this prototype, it was a workaround due to Figma's prototyping limitations. The original concept involved a press-and-hold gesture, which was more aligned with the goal of reducing accidental unlocks.
Testing the Flow
To test how intuitive and effective the feature really was, I ran a remote usability test using Maze. I recruited 7 participants, all active WhatsApp users, and gave them one simple, realistic task:
This helped me observe how users naturally approached the feature and whether the flow felt clear, seamless, and purposeful.
Imagine you want to video call Grandma with your baby or toddler. Start a video call and then try using Child Lock to freeze the screen so your toddler can’t mess up anything. Then, once you're ready, turn off Child Lock and return to the regular video call.”
User Feedback
“I love my kid but I hate when they use my phone when I call family… this solves my issue!”
Future Testing
For this round, I kept testing to a single task flow for simplicity, but in the future, I plan to break it into two- turning Child Lock on and off- to better analyze behavior.
I’d also explore A/B testing to see whether users prefer activating Child Lock before the call or during it, which could inform future improvements.
Iterating on the Design
In my first round of testing, a few users said the prototype wasn’t working, even though it seemed fine when I tested it myself. After watching one user test it in person, I realized they were tapping the whole video call bar, not just the icon like I had assumed. I updated the prototype so the entire button was clickable. It was a good reminder that sometimes the issue isn’t the design- it’s the assumptions behind it.
Adding the “Yes” Users Expected
The second iteration came after testing. I had originally kept the bottom sheet simple with just a “Maybe Later” option, thinking the “Learn How” link would be enough. But a few users were confused and expected to see a clear “Yes” option. To make the choice more obvious, I added a “Yes, Show Me How” button, even though I didn’t build out the full flow behind it yet.
“I need this (feature) NOW!”
“This (feature) may actually entice me to call my parents more often so they can see my kids if I know they won’t ruin the call!”
Reflection
Next Steps
Design an Android-specific version using native tools like App Pinning
Integrate optional onboarding or in-app guidance for first-time users
Consider adding customizable settings, like auto-lock timers or pre-call preferences, to give parents more control
This project showed how a small, focused feature can make a meaningful difference when thoughtfully designed. It reinforced the value of observing real behavior, working within constraints, and designing with empathy for everyday moments.