Skip to content
App Graveyard
Plot #0005
FailediOSHealth / FitnessComposite example · Metrics illustrative

SoulPulse

A generic spiritual habit tracker that learned faith products need real community specificity

Autopsy summary

SoulPulse was built for iOS in Health / Fitness. It died primarily from wrong audience, but the useful signal is the lesson: Building for a community I wasn't part of and assuming all spiritual practices are interchangeable. Prayer for a Catholic is fundamentally different from salat for a Muslim, which is different from zazen for a Zen Buddhist. A 'non-denominational spiritual tracker' is like a 'non-specific sports app' — technically covers everything, practically useful for nothing. I needed to pick one tradition, go deep, and build with (not just for) that community.

Cause of death

Wrong Audience

The 'non-denominational' positioning was the core problem. Christian users wanted Bible verse integration, prayer request sharing, and church community features. Muslim users wanted accurate prayer times, Quran tracking, and Ramadan-specific features. Buddhist practitioners wanted meditation timers with bells and dharma talk integration. By trying to serve everyone, I served no one well. Each tradition has deeply specific practices and cultural context that a generic 'spiritual tracker' can't capture. Users from each group said some version of 'this is nice but [specific app for my tradition] does what I actually need.' I also had no distribution channel into any specific religious community. I posted on Reddit's spirituality subreddits and got mild interest, but no viral spread within any community.
Useful signal

What worked

The onboarding was well-designed. Users picked their spiritual tradition (or 'none'), selected which practices they wanted to track, and set reminder times. The UI was calming and got compliments. A few users said it was the most beautiful habit tracker they'd used. The streak mechanic worked for the first week — about 40% of users who completed onboarding logged at least 5 of their first 7 days.
Takeaway

What to avoid

Building for a community I wasn't part of and assuming all spiritual practices are interchangeable. Prayer for a Catholic is fundamentally different from salat for a Muslim, which is different from zazen for a Zen Buddhist. A 'non-denominational spiritual tracker' is like a 'non-specific sports app' — technically covers everything, practically useful for nothing. I needed to pick one tradition, go deep, and build with (not just for) that community.
Editorial read
5/10Revival potentialSolo Builder
Time spent4 months
Revenue$0 (planned a $3.99/month subscription, never launched it — too few users)
Users~700 downloads across iOS and Android, ~120 used it more than once
Money spent$1,600 (Apple Developer, Google Play, a freelance designer for the icon and onboarding illustrations)
Traffic~4,000 combined App Store and Play Store impressions
Launched2024-05
Shut down2024-11
Built with
FlutterFirebase
Composite launch case studyCurated by App Graveyard editors
Failed becauseWrong Audience
Key lesson

Building for a community I wasn't part of and assuming all spiritual practices are interchangeable. Prayer for a Catholic is fundamentally different from salat for a Muslim, which is different from zazen for a Zen Buddhist. A 'non-denominational spiritual tracker' is like a 'non-specific sports app' — technically covers everything, practically useful for nothing. I needed to pick one tradition, go deep, and build with (not just for) that community.

Worth rebuilding?
5/10

Timeline

Launch2024-05
Current statusFailed
Shutdown or pause2024-11
Narrative

The story

The useful part is not that it failed. It is where the founder saw signal, where the bet broke, and what a second builder should avoid.

Context

What was built

SoulPulse was a habit tracker specifically for spiritual practices. Users could track daily prayers, meditation sessions, scripture reading, gratitude journaling, and custom spiritual habits. It had streaks, gentle reminders, a weekly reflection prompt, and a 'spiritual wellness score' based on consistency. The design used calming colors, soft animations, and nature imagery. I built it as a cross-platform app with Flutter so I could launch on both iOS and Android. The idea was to be the 'Headspace for prayer' — a polished, non-denominational app for people with a spiritual practice.

Thesis

Why they built it

I noticed that most habit trackers were generic (track anything) or secular (meditation-only, like Headspace and Calm). There wasn't a good app for people who had a religious or spiritual practice that included prayer, scripture reading, and other faith-based habits. I'm not deeply religious myself, but I meditate daily and I assumed the need was similar. I thought a 'non-denominational spiritual tracker' would appeal broadly — Christians, Muslims, Buddhists, Jews, and secular meditators could all use it.

Signal

What worked

The onboarding was well-designed. Users picked their spiritual tradition (or 'none'), selected which practices they wanted to track, and set reminder times. The UI was calming and got compliments. A few users said it was the most beautiful habit tracker they'd used. The streak mechanic worked for the first week — about 40% of users who completed onboarding logged at least 5 of their first 7 days.

Breakage

What failed

The 'non-denominational' positioning was the core problem. Christian users wanted Bible verse integration, prayer request sharing, and church community features. Muslim users wanted accurate prayer times, Quran tracking, and Ramadan-specific features. Buddhist practitioners wanted meditation timers with bells and dharma talk integration. By trying to serve everyone, I served no one well. Each tradition has deeply specific practices and cultural context that a generic 'spiritual tracker' can't capture. Users from each group said some version of 'this is nice but [specific app for my tradition] does what I actually need.' I also had no distribution channel into any specific religious community. I posted on Reddit's spirituality subreddits and got mild interest, but no viral spread within any community.

Failure analysis

Primary failure reason

Wrong Audience

Contributing factors
No DistributionCouldn't Retain Users

Failure chain

  • A polished habit tracker appealed superficially to people with spiritual routines.
  • The product flattened distinct traditions into one generic practice model.
  • Each audience needed specific rituals, language, calendars, and community features.
  • The founder had no trusted distribution inside any one faith community.
  • Retention dropped because the product felt respectful but not truly native to anyone.

What the signals looked like

The onboarding was well-designed. Users picked their spiritual tradition (or 'none'), selected which practices they wanted to track, and set reminder times. The UI was calming and got compliments. A few users said it was the most beautiful habit tracker they'd used. The streak mechanic worked for the first week — about 40% of users who completed onboarding logged at least 5 of their first 7 days.

Where it actually broke

The 'non-denominational' positioning was the core problem. Christian users wanted Bible verse integration, prayer request sharing, and church community features. Muslim users wanted accurate prayer times, Quran tracking, and Ramadan-specific features. Buddhist practitioners wanted meditation timers with bells and dharma talk integration. By trying to serve everyone, I served no one well. Each tradition has deeply specific practices and cultural context that a generic 'spiritual tracker' can't capture. Users from each group said some version of 'this is nice but [specific app for my tradition] does what I actually need.' I also had no distribution channel into any specific religious community. I posted on Reddit's spirituality subreddits and got mild interest, but no viral spread within any community.

Builder takeaway

Lessons

What the founder learned

Identity-based products must serve a specific identity, not a generic umbrella. 'Spiritual people' is not a market — Catholics, evangelicals, Muslims, Buddhists, and secular meditators are separate markets with different needs, different communities, different distribution channels, and different willingness to pay. If you're building for a community you're not part of, you must partner with someone who is, or you'll build something that looks right on the surface but misses the nuance that drives adoption. Also, 'non-denominational' sounds inclusive but actually means 'not for anyone in particular.' In spiritual tech, specificity is a feature, not a limitation.

What they’d do differently

I'd pick one community — say, young evangelical Christians — and build exactly what they need: Bible reading plans, prayer request sharing with accountability partners, Sunday sermon note-taking, and integration with popular church platforms. I'd partner with a youth pastor or campus ministry leader to co-design it and distribute through their existing community. Go deep on one tradition before going broad. Or I'd focus purely on secular meditation and compete with Headspace/Calm on a specific angle (like meditation for developers, or meditation for insomnia).

Editorial scorecard

Revival Potential5/10

How viable is rebuilding this today?

Demand Signal5/10

Did real users or customers want this?

Execution Quality5/10

How well was it built and shipped?

Distribution1/10

Did they have a path to reach users?

Monetization1/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

5/10

Rebuild thesis

The generic spiritual tracker should not be revived. The opportunity is a specific faith-community tool built with insiders, using the language, rituals, calendar, and accountability patterns of that community.

Best operator fit

A builder who belongs to the target community or is partnered with a trusted leader who can co-design and distribute the product.

What to avoid repeating

I'd pick one community — say, young evangelical Christians — and build exactly what they need: Bible reading plans, prayer request sharing with accountability partners, Sunday sermon note-taking, and integration with popular church platforms. I'd partner with a youth pastor or campus ministry leader to co-design it and distribute through their existing community. Go deep on one tradition before going broad. Or I'd focus purely on secular meditation and compete with Headspace/Calm on a specific angle (like meditation for developers, or meditation for insomnia).

First 30-day revive plan

Choose one narrow community, run interviews after actual services or group meetings, prototype with a spreadsheet or group chat, and only build once a repeated practice emerges.

Major risks

Trust is hard to earn from outside, religious practices vary even within traditions, and monetization may need to flow through organizations rather than individuals.

Founder opt-in

Revive this app

The founder is open to revival interest. App Graveyard has not verified ownership, asset claims, pricing, or availability yet. This is an interest signal, not a transaction.

Submit private interest
Open to
FeedbackPartnershipHire help
Available assets
Brand assetsAnalytics data
Asking priceNot for sale
Contact preferenceApp Graveyard relay
Contact through App GraveyardYour message is reviewed by App Graveyard first. Founder emails are never shown publicly.Open form
Avoid this failure pattern

Turn this postmortem into a pre-flight check.

Unclear Buyer

The product has a user in mind, but not a specific buyer with budget, urgency, and authority.

Study the pattern ->

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.