Skip to content
App Graveyard
Plot #0003

InnerLog

AI-guided journaling that asks the right questions at the right time

Revive Score40
BuilderSolo Builder
Time Spent3 months
Money Spent$1,200 (Apple Developer, Supabase Pro, Claude API credits, TestFlight beta expenses)
Revenue$860 (annual subscriptions at $29.99/year — about 29 subscribers at peak)
Launched2024-08
Shut Down2025-02
Users~3,200 downloads, ~1,100 wrote at least one entry, 29 paid subscribers
Traffic~9,000 App Store impressions, ~2,000 from a Threads post that got traction
Built with
React NativeClaude CodeSupabase
Composite launch case studyCurated by App Graveyard editors
Failed becauseCouldn't Retain Users
Key lesson

Treating retention as a feature problem when it's a behavior problem. I kept adding features to improve retention — streaks, mood tracking, better prompts, insight summaries — but none of them moved the 14-day cliff. Journaling apps don't fail because the app is bad. They fail because most people don't actually want to journal regularly. The addressable market of 'people who want to journal and need help starting' is small and the habit doesn't stick.

Worth rebuilding?

4/10 revival potential

Timeline

Launch2024-08
Current statusFailed
Shutdown or pause2025-02

The story

What was built

InnerLog was a journaling app that used AI to generate personalized writing prompts based on your mood, the time of day, and your recent entries. Morning entries got reflective prompts ('What's one thing you're avoiding?'). Evening entries got gratitude prompts. If you mentioned work stress in previous entries, it would gently probe that topic. It also generated weekly 'insight summaries' showing emotional patterns across your entries. The writing experience was clean — distraction-free editor, dark mode, end-to-end encrypted entries stored in Supabase.

Why they built it

I'd journaled on and off for years and always quit because of the blank page problem — I'd open a journal app, see an empty screen, and not know what to write. AI-generated prompts felt like the obvious solution. I tested the concept by journaling with ChatGPT for a month and found the prompts genuinely helpful. I assumed other people had the same blank-page problem and would pay for a polished app that solved it.

What worked

First-session engagement was extremely high. People who opened the app and saw a thoughtful, personalized prompt wrote an average of 280 words — much more than typical journaling apps report. The weekly insight summaries were a hit — people shared screenshots on social media ('the app noticed I'm stressed every Tuesday'). The AI prompts felt personal, not generic, because they referenced themes from previous entries. Beta testers called it 'the first journaling app that actually knows me.'

What failed

Day 14 was a wall. Of users who journaled on day 1, only 18% were still journaling on day 7, and only 6% on day 14. By day 30, it was under 2%. The AI prompts helped people start, but they couldn't sustain the habit. After two weeks, the prompts started feeling repetitive (there are only so many ways to ask about gratitude and stress), and users felt like they were 'performing' for the AI rather than writing for themselves. The insight summaries were interesting but not useful enough to open the app for. Push notification reminders had a 4% tap-through rate — most people ignored them. The fundamental problem was that journaling is a habit, and no AI feature can substitute for the intrinsic motivation to journal. I was fighting human nature, not a product problem.

What was validated

First-session engagement was extremely high. People who opened the app and saw a thoughtful, personalized prompt wrote an average of 280 words — much more than typical journaling apps report. The weekly insight summaries were a hit — people shared screenshots on social media ('the app noticed I'm stressed every Tuesday'). The AI prompts felt personal, not generic, because they referenced themes from previous entries. Beta testers called it 'the first journaling app that actually knows me.'

Key lesson

Treating retention as a feature problem when it's a behavior problem. I kept adding features to improve retention — streaks, mood tracking, better prompts, insight summaries — but none of them moved the 14-day cliff. Journaling apps don't fail because the app is bad. They fail because most people don't actually want to journal regularly. The addressable market of 'people who want to journal and need help starting' is small and the habit doesn't stick.

Failure analysis

Primary failure reason

Couldn't Retain Users

Contributing factors
Bad Business Model

What the signals looked like

First-session engagement was extremely high. People who opened the app and saw a thoughtful, personalized prompt wrote an average of 280 words — much more than typical journaling apps report. The weekly insight summaries were a hit — people shared screenshots on social media ('the app noticed I'm stressed every Tuesday'). The AI prompts felt personal, not generic, because they referenced themes from previous entries. Beta testers called it 'the first journaling app that actually knows me.'

Where it actually broke

Day 14 was a wall. Of users who journaled on day 1, only 18% were still journaling on day 7, and only 6% on day 14. By day 30, it was under 2%. The AI prompts helped people start, but they couldn't sustain the habit. After two weeks, the prompts started feeling repetitive (there are only so many ways to ask about gratitude and stress), and users felt like they were 'performing' for the AI rather than writing for themselves. The insight summaries were interesting but not useful enough to open the app for. Push notification reminders had a 4% tap-through rate — most people ignored them. The fundamental problem was that journaling is a habit, and no AI feature can substitute for the intrinsic motivation to journal. I was fighting human nature, not a product problem.

Lessons

What the founder learned

Some product categories have structural retention problems that no feature can fix. Journaling, meditation, language learning, and fitness apps all hit the same wall: the user's motivation fades before the habit forms, and the app can't manufacture motivation. If you're building in one of these categories, you need either a social accountability mechanism (journaling with a partner), external stakes (lose money if you skip), or a non-habit business model (one-time use, like generating a single life story from journal entries). Also, AI-generated prompts have a freshness window — they feel magical for 5-7 sessions, then repetitive. The novelty wears off faster than the habit forms.

What they’d do differently

I wouldn't build a daily journaling app. Instead, I'd build a 'life documentation' tool — you journal when something meaningful happens (not daily), and the AI helps you reflect on it deeply. Remove the daily habit expectation entirely. Or I'd pivot to a B2B angle: AI journaling prompts for therapy patients (therapist assigns prompts, patient writes between sessions, therapist sees summaries). That has external accountability built in and a professional paying the bill.

Editorial scorecard

Revival Potential4/10

How viable is rebuilding this today?

Demand Signal6/10

Did real users or customers want this?

Execution Quality7/10

How well was it built and shipped?

Distribution4/10

Did they have a path to reach users?

Monetization3/10

Was the business model viable?

Lesson Value9/10

How useful is this postmortem for other builders?

Scores are assigned by App Graveyard editors after review. They are directional, not scientific.

Rebuild opportunity

4/10

Daily journaling apps are a graveyard category. But AI-assisted reflection for specific moments (quarterly life reviews, therapy homework, career transition processing) has untapped potential because you don't need a daily habit — you need depth at key moments. The B2B therapy angle is strongest: therapists want patients to reflect between sessions, patients need prompts, and insurance or the therapist pays, not the consumer.

Related postmortems

Built something that didn't work out?

Every failed app has a lesson. Submit yours and help the next builder avoid your mistake. Anonymous submissions welcome.