First Real Usage, First Real Reality Check (Week 08)

Last week my little brother installed version 1.0.0 of the app. He was curious about it, but he didn’t use it that day. I decided not to remind him and just observe whether he would return on his own.

The next day, I was out all day. In the evening, I opened Supabase to check if anything happened. And there it was: four completed learning sessions.

That moment was huge. After weeks of building, seeing real usage from my only user felt unreal. Even though it's just one learner, it meant the idea was finally alive, not in my head, but in someone’s hands.

A Promising First Pattern

From the session logs, a few things immediately stood out:

• He tried it completely on his own, with zero reminders.

• He completed two sessions back-to-back.

• Later in the evening, he came back and took two more.

• All four sessions happened before the scheduled 7 PM notification.

This was encouraging.
It suggested curiosity, enjoyment, and self-driven motivation, all strong signals for activation. It gave me real hope that the core experience actually works.

Then the Drop

But for the rest of the week, he didn’t open the app again. Not once.

I waited a few days before talking to him, because I still don’t want him to know it’s my app. Honest feedback is rare, especially with family, the moment someone knows you built it, they hesitate to disappoint you.

During those days, I knew the notifications weren’t working. The app uses local notifications, meaning he only receives the next day’s reminder if he opens the app daily. Since he didn’t reopen it after day one, he only ever received that single reminder.

This is a design failure on my part.

Learning apps rely heavily on nudges, especially when the users are young. Even if they enjoy the experience, motivation fades quickly in the middle of a world full of distractions. I underestimated how important consistent reminders are.

The Feedback That Hit Hard

At the end of the week, I casually asked him whether he liked the app.
He said yes, which matched the pattern from day one.

Then I asked why he didn’t open it again.

He simply said, “I don’t know.”

That “I don’t know” actually tells a lot.
It means the app wasn’t bad. It wasn’t confusing. It just wasn’t compelling enough to pull him back in. That’s a very common gap in early-stage products: people like them, but not enough to return consistently.

And then he added something important.

He said that after completing a learning session, the screen turned white for 2–3 seconds before the path showed again. That small delay annoyed him.

That hit me.
A tiny UX flaw I thought wouldn’t matter actually disrupted the experience. It happened because the app was updating his progress in the backend without showing any loading indicator. Those few seconds were enough to create friction, the silent kind that kills retention.

This is a classic lesson in product design:
It’s rarely the big features that break the experience. It’s the small, unpolished moments.

What This Week Really Taught Me

Activation happened. That’s great.

But retention? That’s the next battle.

Here’s what I’m taking away:

• Curiosity gets you the first session.

• A smooth experience gets you the second.

• But it’s the loop, notifications, reward, pacing, UX, that brings users back.

My job now is to fix what’s broken, remove friction, and design a consistent path back into the app.

Next Week

Next week will be focused entirely on retention work:
fixing the UX delays, solving the notification flaw, and trying to understand how to make the experience motivating enough for him to come back without being pushed.

Thanks for reading, see you next Tuesday! 🚀