Skip to content
App Graveyard
Plot #0002
AbandonediOSFinance / FintechComposite example · Metrics illustrative

SubWatch

A beautiful iOS subscription tracker that lost to incumbents and native platform features

Autopsy summary

SubWatch was built for iOS in Finance / Fintech. It died primarily from crowded market, but the useful signal is the lesson: Entering a saturated App Store category where the incumbents have thousands of reviews and years of ranking history. My app was objectively better-designed than most competitors, but that doesn't matter when you're invisible in search results. I also underestimated how easily Apple could obsolete the category with a native feature — subscription tracking is a natural OS-level capability.

Cause of death

Crowded Market

The App Store has over 40 subscription tracker apps. Most are free or freemium. Competing on design alone doesn't work when users search 'subscription tracker,' see 10 results, and download whatever's first. My app appeared on page 2-3 of search results because established apps had years of download history and reviews. Then in June 2024, Apple announced that iOS 18 would show subscription management natively in Settings. That announcement killed my motivation — why build something Apple is about to give away? Downloads were already declining, but the Apple announcement was the final nail.
Useful signal

What worked

The design was genuinely good. People who found the app loved how it looked and felt. My App Store screenshots were clean, the onboarding was fast, and the ratings averaged 4.7 stars. The 'subscription audit' feature — which flagged subscriptions you hadn't opened in 30+ days — got specific positive mentions in reviews. A few indie iOS developers shared it on Twitter, which drove my best download days.
Takeaway

What to avoid

Entering a saturated App Store category where the incumbents have thousands of reviews and years of ranking history. My app was objectively better-designed than most competitors, but that doesn't matter when you're invisible in search results. I also underestimated how easily Apple could obsolete the category with a native feature — subscription tracking is a natural OS-level capability.
Editorial read
2/10Revival potentialSolo Builder
Time spent4 months
Revenue$220 (44 users at $4.99 lifetime unlock)
Users~2,600 downloads, ~600 monthly active at peak, 44 paid
Money spent$800 (Apple Developer, a freelance icon designer, Firebase Blaze for a month)
Traffic~12,000 App Store impressions over 6 months
Launched2024-01
Shut down2024-07
Built with
SwiftFirebase
Composite launch case studyCurated by App Graveyard editors
Failed becauseCrowded Market
Key lesson

Entering a saturated App Store category where the incumbents have thousands of reviews and years of ranking history. My app was objectively better-designed than most competitors, but that doesn't matter when you're invisible in search results. I also underestimated how easily Apple could obsolete the category with a native feature — subscription tracking is a natural OS-level capability.

Worth rebuilding?
2/10

Timeline

Launch2024-01
Current statusAbandoned
Shutdown or pause2024-07
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

SubWatch was an iOS app for tracking recurring subscriptions. You'd add your subscriptions manually (Netflix, Spotify, gym, etc.), and the app showed your total monthly spend, upcoming renewal dates, and a calendar view of payments. There were reminder notifications before renewals, a 'subscription audit' feature that highlighted underused subscriptions, and spending trend charts. The UI was clean — minimal, dark mode, nice animations. I offered a free tier (up to 5 subscriptions) and a one-time $4.99 unlock for unlimited.

Thesis

Why they built it

I was paying for 14 subscriptions and realized I'd been paying for two I forgot about for 6 months. I searched the App Store and found dozens of subscription trackers, but they all felt clunky, outdated, or overly complex. I thought a beautifully designed, minimal tracker would stand out. I was also inspired by indie iOS devs on Twitter who seemed to make a living from well-designed utility apps.

Signal

What worked

The design was genuinely good. People who found the app loved how it looked and felt. My App Store screenshots were clean, the onboarding was fast, and the ratings averaged 4.7 stars. The 'subscription audit' feature — which flagged subscriptions you hadn't opened in 30+ days — got specific positive mentions in reviews. A few indie iOS developers shared it on Twitter, which drove my best download days.

Breakage

What failed

The App Store has over 40 subscription tracker apps. Most are free or freemium. Competing on design alone doesn't work when users search 'subscription tracker,' see 10 results, and download whatever's first. My app appeared on page 2-3 of search results because established apps had years of download history and reviews. Then in June 2024, Apple announced that iOS 18 would show subscription management natively in Settings. That announcement killed my motivation — why build something Apple is about to give away? Downloads were already declining, but the Apple announcement was the final nail.

Failure analysis

Primary failure reason

Crowded Market

Contributing factors
Platform DependencyPricing Wrong

Failure chain

  • The app solved a real annoyance for a small group of subscription-conscious users.
  • App Store discovery favored older trackers with thousands of reviews and keyword history.
  • A one-time $4.99 unlock could not fund ongoing feature work or acquisition.
  • Apple moved subscription management closer to the operating system, weakening the standalone utility.
  • The product had polish, but no data advantage or channel strong enough to beat incumbents and the platform.

What the signals looked like

The design was genuinely good. People who found the app loved how it looked and felt. My App Store screenshots were clean, the onboarding was fast, and the ratings averaged 4.7 stars. The 'subscription audit' feature — which flagged subscriptions you hadn't opened in 30+ days — got specific positive mentions in reviews. A few indie iOS developers shared it on Twitter, which drove my best download days.

Where it actually broke

The App Store has over 40 subscription tracker apps. Most are free or freemium. Competing on design alone doesn't work when users search 'subscription tracker,' see 10 results, and download whatever's first. My app appeared on page 2-3 of search results because established apps had years of download history and reviews. Then in June 2024, Apple announced that iOS 18 would show subscription management natively in Settings. That announcement killed my motivation — why build something Apple is about to give away? Downloads were already declining, but the Apple announcement was the final nail.

Builder takeaway

Lessons

What the founder learned

Design is not a moat. If 40 apps exist in a category and yours is prettier, you still need a distribution advantage to get seen. The App Store rewards incumbents — download velocity, review count, and keyword history determine ranking, not design quality. Also, never build a utility that the platform owner has obvious incentive to build natively. Apple wants users to manage subscriptions in Settings (so they can push Apple One bundles). Building on top of that was building on borrowed time. Finally, one-time $4.99 pricing for a utility app is a dead business model — you need recurring revenue to justify ongoing development, and users won't pay a subscription to track their subscriptions.

What they’d do differently

I wouldn't build a subscription tracker at all. But if I had to, I'd differentiate on data, not design: automatic subscription detection from bank/email feeds (via Plaid or email parsing), negotiation assistance (auto-cancel or downgrade underused subscriptions), and team/family subscription management. Those are hard features that Apple won't build. I'd also charge businesses, not consumers — an 'employee subscription audit' for companies overspending on SaaS tools has real budget-owner buyers.

Editorial scorecard

Revival Potential2/10

How viable is rebuilding this today?

Demand Signal5/10

Did real users or customers want this?

Execution Quality7/10

How well was it built and shipped?

Distribution2/10

Did they have a path to reach users?

Monetization2/10

Was the business model viable?

Lesson Value8/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

2/10

Rebuild thesis

Consumer subscription tracking is too exposed to Apple and too crowded to justify another standalone app. The stronger revival is B2B SaaS spend cleanup for small teams that cannot justify enterprise procurement software.

Best operator fit

Someone with finance ops, SaaS procurement, or founder-led B2B sales experience who can reach budget owners directly.

What to avoid repeating

I wouldn't build a subscription tracker at all. But if I had to, I'd differentiate on data, not design: automatic subscription detection from bank/email feeds (via Plaid or email parsing), negotiation assistance (auto-cancel or downgrade underused subscriptions), and team/family subscription management. Those are hard features that Apple won't build. I'd also charge businesses, not consumers — an 'employee subscription audit' for companies overspending on SaaS tools has real budget-owner buyers.

First 30-day revive plan

Talk to 15 small-team operators, audit their SaaS receipts manually, quantify duplicate tools, and sell a cleanup report before rebuilding any dashboard.

Major risks

Plaid/email integrations add security burden, procurement workflows are slow, and incumbents can move downmarket if the segment proves attractive.

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
Sell codebaseAllow rebuildOpen to offers
Available assets
CodebaseApp Store listingBrand assets
Asking priceOpen to offers
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.

Crowded Category

The idea enters a busy market without a wedge strong enough to change buyer behavior.

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.