Important: This article shares my personal journey and philosophy as a parent and app developer. It's not medical, developmental, or therapeutic advice. If you have concerns about your child's development, please consult qualified professionals like pediatricians or speech-language pathologists.
Building Apps as a Parent-Developer
I'm a parent with a toddler who loves vehicles. I'm also a product manager who worked in tech before diving into app development.
That combination—understanding how digital products get built, being a parent experiencing the app landscape firsthand, and having professional experience in product strategy—shaped how I approach Little Wheels.
When I looked for quality educational apps for my own family, I kept running into the same frustrations: subscription traps with confusing free trials, excessive data collection, apps that stopped working without internet, and features that seemed designed more for engagement metrics than child development.
So I decided to build what I wished existed: apps that respect families, work offline, cost once, and prioritize child development over growth metrics. Learn more about the Little Wheels story.
The Indie Advantage: Freedom to Prioritize What Matters
Here's the fundamental difference between building Little Wheels and how larger companies operate:
When you're solo with minimal overhead, you can make decisions based purely on what's right for families. There's no tension between "what's best for kids" and "what hits quarterly targets" because those are the same thing for me.
This creates different answers to basic product questions:
Question 1: Should I build user accounts and cloud sync?
The scalable approach: Yes, because it enables personalization, data-driven optimization, and builds lock-in that supports subscription models.
My answer: No, because:
- •Parents don't trust apps that collect data on their kids
- •Requiring internet means it doesn't work on planes or road trips
- •Creating another account for a toddler app is annoying
- •Server infrastructure creates costs that force subscription pricing
I chose to rebuild everything offline. It took weeks longer, but now families get apps that work anywhere, collect nothing, and cost once.
Question 2: How should I price this?
The industry standard: Monthly subscription with "free trial" that auto-renews, optimized for recurring revenue.
My answer: One-time $4.99 purchase, own forever, because:
- •I'm exhausted by subscription fatigue as a parent myself
- •It feels wrong to auto-charge busy families monthly
- •The apps don't cost me monthly to maintain once built
- •It aligns with how I think families should own their digital tools
Question 3: What features should I prioritize?
Data-driven approach: Build whatever drives engagement metrics and daily active users.
My answer: Build what makes developmental sense based on research and expert consultation.
This is where my product management background actually helps—I know how to gather requirements, synthesize feedback, and make strategic tradeoffs. But the requirements come from child development research and professional consultations, not growth targets.
Learning from Actual Experts
One of the biggest advantages of being indie is having time to deeply research and directly consult with professionals who actually know child development.
During development, I reached out to:
- ✓Occupational therapists who work with young children on sensory and motor development
- ✓Speech-language pathologists including my sister-in-law, who gave feedback on Talk & Listen's phoneme progression and activity structure
- ✓My wife, a pediatric nurse practitioner, who helped me think through developmental appropriateness
- ✓Preschool directors and teachers who see hundreds of children and understand what actually works in practice
These weren't formal partnerships or advisory boards. Just conversations where I asked questions, showed them what I was building, and listened to their professional insights.
Example: Talk & Listen
When designing Talk & Listen's speech activities, my sister-in-law (an SLP) helped me understand why organizing sounds by articulation difficulty matters, and how vehicle themes could leverage existing interests to support practice. That direct professional input shaped the entire app structure.
Example: Create & Play
Talking with preschool teachers helped me understand why Create & Play needed to be truly mess-free and why offline functionality mattered so much for their contexts—no reliable WiFi in many classrooms, and they couldn't have 15 kids all trying to connect to school internet.
This kind of direct expert consultation is easier when you're solo. I'm not scheduling formal meetings or getting approval for external advisors. I'm just a parent asking professionals in my network for feedback, then incorporating their insights directly.
What This Actually Means for Your Family
When you choose a Little Wheels app, here's what's different:
You're NOT getting:
- ❌Growth metrics driving feature decisions
- ❌Pressure to maximize "engagement" or time-in-app
- ❌Subscription optimization designed to make canceling difficult
- ❌Data collection on your child's behavior
You ARE getting:
- ✅Apps built by a parent for parents
- ✅Features informed by professional consultation with SLPs, OTs, and educators
- ✅Decisions made based on "is this good for kids?" not "will this increase revenue?"
- ✅Honest one-time pricing with no hidden costs
- ✅Direct access—my email is on every app listing
Being indie means I can afford to make the right choice, not just the profitable one.
Why This Works in 2025
This business model works now because modern development tools handle technical complexity that used to require large teams. That dramatically lowers the overhead needed to build quality software. Read more about why indie developers can build better apps for families.
But tools don't make values decisions. They don't choose whether to respect parents or optimize for revenue. They don't determine whether to use subscription tricks or honest pricing.
Those are human choices—specifically, choices from a parent and product manager who experienced the frustration of predatory apps and decided to build differently.
The tools make it economically viable to stay small.
Being small makes it possible to stay honest.
Why My Email Is Public
Look at any Little Wheels app in the App Store. My email address is right there in the description.
When parents have questions or feedback, they email me directly. I respond personally, usually within a day (sometimes longer if life gets busy, but I do respond).
Larger companies can't do this at scale. They need support systems, ticket queues, canned responses.
Being small means staying connected to real families. I'm not reading dashboard metrics—I'm having actual conversations with parents about their kids and what's working or not working for them.
This keeps me honest and grounded. It's hard to make exploitative choices when you're personally responding to every frustrated parent who encounters them.
The Honest Tradeoffs
Being indie has real limitations:
- ⚠️Slower updates:One person can't move as fast as a team. When iOS changes something, I fix it as quickly as I can, but there's no 24/7 team on call.
- ⚠️Narrower focus:I build deeply for specific needs rather than broadly for everyone. Talk & Listenfocuses on vehicle-based speech practice. Create & Play targets mess-free creativity. If you want 100 mini-game categories, other apps do that.
- ⚠️Single point of failure:If something happens to me, there's no team to continue. Your apps will keep working offline, but new features would stop.
- ⚠️Limited support hours:I'm a parent with a toddler. I respond to emails, but not instantly.
These limitations are real. But they're intrinsically connected to why the apps can be honest, research-informed, and affordable.
What Comes Next
I'm currently researching social-emotional learning for the next app. Reading published research on emotional regulation, talking with early childhood educators, and thinking about how vehicle themes might support co-regulation and emotional skill development.
No investor is demanding a launch date. No competing priorities are pushing for features that serve business goals over developmental goals. Just careful research, professional consultation, and thoughtful building.
This is how Little Wheels will continue to grow: slowly, focused on specific needs, and honest about what it can and can't do.
If this approach resonates with you, you're exactly the type of parent I'm building for. Explore more about why indie apps are better for families.
Because in a world of subscription traps and data harvesting, there's something powerful about proving that values-driven, parent-focused products can still succeed.
Tell other parents who share these values. Together, we can show that honest apps built for families can thrive. Learn more about supporting indie developers.
Frequently Asked Questions
Ad-free & offline ready
