Skip to content
App Graveyard
Plot #461611419522499150
AbandonediOSProductivity

Live Smoke Test App

Temporary test submission to verify the live App Graveyard review flow.

Autopsy summary

Live Smoke Test App was built for iOS in Productivity. It died primarily from no distribution, but the useful signal is the lesson: I did not validate a repeatable distribution channel before spending time on the product.

Cause of death

No Distribution

Testing wasn't enough
Useful signal

What worked

It worked on testing
Takeaway

What to avoid

I did not validate a repeatable distribution channel before spending time on the product.
Editorial read
5/10Revival potentialSolo Builder
Time spent3 months
Revenue$100
Users200 users
Money spent$500
Traffic1000 visits/month
Launched2024-04
Shut down2026-01
Built with
Claude CodeCodex
Founder-submitted postmortemSubmitted by Live Test FounderCurated by App Graveyard editors
Failed becauseNo Distribution
Key lesson

I did not validate a repeatable distribution channel before spending time on the product.

Worth rebuilding?
5/10

Timeline

Launch2024-04
Current statusAbandoned
Shutdown or pause2026-01
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

A small web app for testing whether App Graveyard submissions are stored, reviewed, approved, and displayed correctly in production. It was built only for live smoke testing the submission pipeline.

Thesis

Why they built it

I built it to test whether a small productivity app could find real demand from builders before investing more time.

Signal

What worked

It worked on testing

Breakage

What failed

Testing wasn't enough

Failure analysis

Primary failure reason

No Distribution

Contributing factors
Crowded MarketBad Timing

What the signals looked like

It worked on testing

Where it actually broke

Testing wasn't enough

Builder takeaway

Lessons

What the founder learned

The important lesson is that the full product loop must be tested on the live domain before launch: submit, store privately, review in admin, approve, display publicly, and verify private fields never leak.

What they’d do differently

Choose different market

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?

Distribution5/10

Did they have a path to reach users?

Monetization5/10

Was the business model viable?

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

Yes, someone could fix it.

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
FeedbackPartnershipSell codebaseSell domainSell full appAllow rebuildRevenue shareOpen to offers
Available assets
CodebaseDomainApp Store listingAnalytics dataContent
Asking priceOpen to offers
Contact preferenceApp Graveyard relay; founder email hidden
Contact through App GraveyardYour message is reviewed by App Graveyard first. Founder emails are never shown publicly.Open form

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.