u/Dssoft64

Image 1 — I just wanted to help my kid learn to read… this is what I discovered
Image 2 — I just wanted to help my kid learn to read… this is what I discovered
Image 3 — I just wanted to help my kid learn to read… this is what I discovered
Image 4 — I just wanted to help my kid learn to read… this is what I discovered
Image 5 — I just wanted to help my kid learn to read… this is what I discovered
Image 6 — I just wanted to help my kid learn to read… this is what I discovered
Image 7 — I just wanted to help my kid learn to read… this is what I discovered
▲ 1 r/appdev

I just wanted to help my kid learn to read… this is what I discovered

I built a reading app for my kid… and realized most “kids apps” are kind of broken

A few months ago I was trying to help my kid learn to read.

Naturally, I downloaded a bunch of popular apps…

and honestly, most of them felt like:

* tap random things

* loud sounds

*flashy animations

*zero actual learning

It looked like engagement > learning.

So I tried something different.

Instead of teaching kids to recognize words, I focused on helping them figure words out.

The core idea became:

* Hear a sound

* Build the word (drag letters)

* Understand it in a sentence

No overload. No chaos. Just one thing at a time.

What surprised me most while building:

Kids don’t struggle with learning — they struggle with bad UX.

If there’s even slight confusion, they drop off instantly.

If it’s clear and interactive, they stick with it way longer than expected.

It’s still early, but a few parents started using it and the feedback has been interesting — especially from kids who weren’t engaging with other apps.

Not claiming it’s perfect, just sharing what I learned building for a real user (my kid 😅)

Would love honest feedback — especially from other parents/builders.

https://phonixo.com/

u/Dssoft64 — 5 days ago