I launched Whet on the App Store on March 31 — an iOS app that turns any topic into a 5-minute AI lesson with a quiz, then pulls you back through spaced repetition so the learning doesn't evaporate.
Here's where I actually am two and a half weeks in:
64 total installs
51.6% completed at least one lesson
29.7% completed two or more
21.9% completed three or more
15.6% opened the app on three or more distinct days
So roughly 10 people are doing the thing I designed the app around — building a small learning habit.
Launch week was rough. Two crashes (one in navigation, one in storage) meant a chunk of my earliest installs opened the app, crashed, uninstalled, and never came back. None of that shows up in analytics. It just shows up as a quiet retention cliff you understand later.
I spent the next two weekends shipping features: a difficulty picker, an accessibility mode, a batch of SEO landing pages. Yesterday I realized none of those 10 active users had asked for any of it, and I haven't actually talked to a single one of them.
So here's what I'm doing next: stopping feature work for two weeks and interviewing my 10 most active users. Three questions I want to ask:
What topic were you trying to learn, and did Whet actually teach it?
What almost made you delete the app?
If Whet disappeared tomorrow, what would you replace it with?
For anyone who's been at the 10–50 active user stage — did founder-led interviews actually move the needle for you, or did you wait for more scale first? Curious what worked.
App: https://apps.apple.com/us/app/whet-sharpen-your-mind/id6761222658
Site: https://whetlearning.app
Website: https://whetlearning.app
I'm at a similar stage with an Android beta, and I think stopping feature development to talk to the people who are actually using it is probably one of the highest-value things you can do right now.
One thing I'm trying to pay attention to is not just who is active, but why they're coming back and what happens when they use the product. A user who opens something 20 times isn't necessarily more valuable than someone who uses it twice but tells you that those two interactions genuinely solved a problem.
I'm also finding that asking users to describe a behaviour after the fact can be less useful than asking about the specific moment when the problem occurs: What were you trying to do? What did you expect? What did you actually do?
With such a small user base, I think those individual stories can reveal patterns long before the analytics become statistically meaningful.
I'd definitely be interested to hear what you discover from the interviews with your most active users — especially whether their reasons for returning match what you originally thought the product's core value was.
I know a few active users of new iOS learning apps personally. I could ask if they’d be willing to answer your questions for free.