Skip to main content

Command Palette

Search for a command to run...

Fixing Retention Is Harder Than Fixing Code (Week 09)

Updated
2 min read
Fixing Retention Is Harder Than Fixing Code (Week 09)
M

I love turning ideas into products that make learning and growth feel natural. Freelancing, experimenting, and building my startup one step at a time, learning out loud as I go.

I thought I knew what was wrong.

Last week, my brother’s behavior gave me a clear signal:
he liked the app, completed multiple sessions on day one, then never came back.

Activation? ✅
Retention? ❌

From his feedback, one issue stood out immediately:
after finishing a lesson, the app showed a white screen for 2–3 seconds before the learning path appeared again. No loader. No feedback. Just friction.

That alone was annoying enough to break the experience.

But I had another strong hypothesis.

Even if the experience was good, the app wasn’t nudging him back.
And the reason was a technical shortcut I had taken early on.

To move fast, I used local notifications instead of push notifications.
That meant the learner had to open the app every day for the next day’s reminder to be scheduled.

Since my brother only opened the app twice, he barely received any notifications at all.

So this week, the focus was clear:
remove friction and increase nudges.


What I Fixed

The white screen issue was the easier one.

Instead of reloading all data after each lesson, I used caching to preload the learning path and only update what actually changed. The white screen disappeared, and the flow felt much smoother.

Push notifications were a different story.

They took longer than expected.
I had to integrate third-party tools, set up cron jobs, and work with Firebase, but eventually, it worked.

I shipped version 1.1.0, uploaded it to Google Play Console, and updated my brother’s app.


What Happened Next

For three days after the update, my brother didn’t open the app.
Not once.

Even with consistent daily notifications at 7 PM.

That was a hard truth to face.

It means my current solutions aren’t strong enough.
Either the notification content isn’t compelling,
or notifications alone aren’t enough to drive retention in this context.

The UX fix gave me no data, because he never reached that part again.


The Real Lesson This Week

Retention isn’t a single fix.
It’s not “just notifications” or “just better UX.”

People don’t come back because an app works.
They come back because it gives them a reason to care today.

Next week will be about finding that reason.

That’s it for this week, see you next Tuesday 🚀