Case Study
Little Talks
Helping parents create more meaningful everyday conversations.
Independent product — designed and developed by me.
Overview
Little Talks is an independent product designed and developed to help parents create more meaningful everyday conversations with their children. It delivers a thoughtful daily prompt and supports habit-building through reminders, streaks, reflections, and lightweight progress tracking.
The problem
Parents often want to connect more meaningfully with their children but struggle to find the right moment or the right words. Generic advice is easy to find, but turning intention into a daily habit requires a product experience that feels gentle, practical, and easy to return to.
My role
Key decisions
- Designed around a single daily prompt to keep the experience focused and low-pressure.
- Used streaks and reminders to support habit formation without creating guilt-driven engagement.
- Added lightweight reflection and progress tracking so parents could notice patterns over time.
- Built mobile-first with React Native and Expo for cross-platform delivery.
- Stored data locally to keep the experience simple and responsive for everyday use.
Technical approach
Little Talks is built with React Native and Expo, using local storage for user data and the notification APIs for daily reminders. The interface prioritizes quick daily interactions: read a prompt, reflect, and move on.
Accessibility considerations
Touch targets, readable type sizes, and sufficient color contrast support everyday use across devices. Notification content is written to be clear and actionable without relying on visual cues alone.
Outcome
Little Talks provides a calm, mobile-first experience for parents who want to build a consistent conversation habit. The product focuses on one prompt per day, supported by reminders and progress cues that encourage return without overwhelming the user.
What I learned
Habit-forming products need restraint. Features like streaks and reminders only help when they support the core behavior rather than competing with it. Keeping the daily loop simple made the product easier to use and easier to maintain.