
Bubbl
A gamified learning companion for teaching body safety and emotional awareness early
Received special mention from the jury for outstanding craft and contribution to the field
Won "Best of Show" award in the showcase event
Introduction: Turning a real-world problem into a mobile experience
Bubbl was developed as the final capstone project for Langara College’s Web and Mobile App Design and Development postgraduate program. Our cohort was divided into cross-functional teams and challenged to identify a real problem encountered in everyday life, then solve it through a mobile application that meaningfully leveraged native mobile capabilities such as touch, drawing, camera, motion, and haptics.
Our team consisted of six designers and four developers, working under an intense thirteen-week timeline from ideation to final presentation. To stay aligned and move fast without sacrificing quality, we adopted an agile workflow with weekly sprints, daily stand-ups, and regular retrospective sessions. This structure allowed us to continuously validate decisions, identify blockers early, and adjust scope without losing sight of the core problem.
My role: Owning the core experience while supporting design leadership at scale
As a product designer, I contributed across the full design lifecycle, from early research and problem framing to interaction design, visual systems, and handoff. I fully owned several core flows that connected the experience end to end:
Lesson Overview (child homepage)
Article Overview and Detail views (parent homepage)
Notifications
Profile management
These surfaces acted as the backbone of the product, tying together learning, progress tracking, and parental oversight.
Because I had previously taken on Lead Designer roles in multiple major projects within the program, the team decided to rotate leadership for this project and gave me the responsibility of supporting the newly appointed Lead Designer by:
Advising on UX and interaction decisions
Leading the creation and maintenance of the design system
Reviewing other designers’ work for alignment and consistency
In addition to product design, I also volunteered to create marketing and presentation materials such as this introduction video for the final showcase.
Problem framing: Addressing sensitive topics before it is too late
Our initial discussions led us toward early childhood education, specifically children between the ages of five and ten. This age group faces rapid emotional and social development, yet interacts with technology far less independently than adults, creating a complex design space with both constraints and opportunity.
Despite advances in developmental psychology and education, topics such as body safety, personal boundaries, and bullying are often introduced too late. Children at this age are forming friendships, asserting independence, interacting with authority figures and peers of different ages, and developing self-awareness, often without the language or tools to articulate uncomfortable experiences.
At the same time, parents and educators struggle to identify early warning signs or initiate conversations around these sensitive subjects. The gap between when these lessons should start and when they actually do became the core problem Bubbl set out to address.
Market analysis: Confirming the urgency and the lack of child-centered digital solutions
To validate the opportunity further, I reviewed research and educational material from Kids in the Know, the national safety education program of the Canadian Centre for Child Protection. The data supported both the urgency of the problem and the lack of engaging, age-appropriate digital tools addressing it.
Early research revealed:
One in three children experience bullying before the age of ten
Sixty percent of parents feel unprepared to talk about body safety with their children
A significant portion of emotional learning occurs before the age of eight
Children learn best through play, repetition, and story-driven interaction
Together, these insights helped solidify Bubbl’s direction and justified a play-first educational approach.
User interviews: Learning how parents regulate technology, education, and sensitive topics
To ground our assumptions, we conducted qualitative interviews with five parents. These conversations focused on parent-child dynamics, attitudes toward technology, educational approaches, and boundaries around device usage.
Key insights from these interviews included:
Children were typically allowed limited screen time and used devices belonging to their parents under supervision
Games, videos, and visual stories were strongly preferred over text-heavy educational materials
Three out of five parents had never discussed the sensitive topics Bubbl focuses on with their children
All parents were open to introducing such an app, provided the educational content came from trusted and reputable sources
These findings reinforced the importance of credibility, parental control, and age-appropriate engagement.
Information architecture: Translating research, constraints, and native capabilities into structure
With insights and constraints clearly defined, we began shaping the product roadmap. As a capstone requirement, the application needed to meaningfully incorporate native mobile features, which influenced both interaction design and feature prioritization.
The experience was structured around several core components:
Gamified learning mechanics tied directly to educational progress
A centralized Learning Hub where lessons could be revisited and tracked
Emotion-expression tools powered by touch-based drawing
A parental monitoring and authorization system secured through passwords and Face ID
I translated these requirements into flow diagrams, defining the overall information architecture and owning the full parent flow to ensure oversight and control were treated as first-class experiences.
Concept exploration: Mapping the experience at low-fidelity
With the foundational flows in place, I moved into concept exploration for the screens under my ownership. These included both child and parent homepages, profile management, and notification surfaces.
Because these screens sat at the center of the experience, connecting lessons, progress, rewards, and monitoring, I focused on clarity of navigation and ease of movement across the app. Low-fidelity wireframes were used to validate layout structure, interaction patterns, and access points before visual styling was introduced.
UI setup: Building a system that scales across designers
One of my primary responsibilities was creating and maintaining the design system. I defined the core color palette, typography, and interaction principles, and custom-built all shared components used throughout the app.
To ensure consistency across a large design team, I created clear rulesets, layout templates, and Figma Libraries, and helped each designer set up their workspace correctly. As the project matured, I also structured the design documentation and streamlined handoff processes to support efficient development.
Personal contribution: Separating child and parent experiences
Given that children rarely use devices without supervision, I proposed a dual-profile system with clearly separated modes. One mode was designed exclusively for children, focusing on learning, play, and expression. The other was built for parents and guardians, giving them administrative control, visibility into progress, and access to educational content intended for adults.
I designed and owned the full parent experience, positioning parents as administrators within an authorization-based system. They could manage multiple child profiles, track learning pace, identify areas of difficulty, and observe potential behavioral signals. To protect sensitive information, access to parent profiles was gated behind Face ID or a secure password.
Personal contribution: Using a mascot to build emotional investment
Children disengage quickly if an experience feels static or instructional. To counter this, I drew inspiration from Tamagotchi and similar digital pet experiences, where emotional attachment and responsibility drive engagement.
I proposed a system in which a mascot accompanies the child throughout their learning journey. Starting a lesson would cost one health point from the mascot, introducing light tension and choice. As children progressed, both they and the mascot would level up together. Rewards earned through learning could be used to customize and nurture the mascot, deepening emotional investment and reinforcing continued use.
Personal contribution: Structuring learning as quests
To support long-term engagement and a clear sense of progress, I designed a quest-based module system. Lessons were grouped into themed modules focused on specific topics such as body safety, bullying, or personal hygiene.
Each module followed a structured sequence of interactive lessons, with rewards granted upon completion. Individual lessons used an interactive quiz format inspired by language-learning platforms, reinforcing learning through repetition, feedback, and visible progress. Together, the module system and mascot mechanics formed a cohesive loop that balanced education and play.
Tech stack: Supporting a multi-layered product with the right tools
Given the product’s engagement layers and complexity, the project relied on a broad set of tools to support collaboration, design, and production:
Jira for task tracking and sprint management
Slack for team communication
Figma for wireframing, prototyping, and presentations
Photoshop and Illustrator for visual assets
After Effects for mascot animations and motion assets
Premiere Pro for video production
InDesign for print and presentation materials
Results: Recognition without a public launch
Although Bubbl was a concept product and never launched publicly, it was presented with a live demo at Langara College’s largest annual product showcase. The event attracted a wide range of tech professionals from across the Greater Vancouver Area.
Our project received the Best in Show award, along with multiple special mentions from the judging panel for design quality and depth of user experience. The recognition validated both the problem we chose to tackle and the care taken in crafting an experience for a highly sensitive audience.






























