Nobody Designs the Death of a Product

I tested seven TV-tracking apps this week. Not because I wanted a new hobby, but because the one holding a decade of my watch history had just been switched off. Apparently grief makes me thorough.

If you don't know: TV Time died. 26 million of us spent the last two weeks refreshing it and wondering whether the icon would vanish or just freeze forever. #savetvtime surfaced everywhere.

The official reason is "not sustainable as a free app." The realer one: the parent company found something more profitable to do with our data than let us enjoy it — an enterprise AI pivot.

Which is the lesson nobody puts in the onboarding flow:

The moment that data was worth more elsewhere, the app became overhead.

What exports, and what doesn't

You can rescue your watch history as a tidy little CSV. Very clean. Very portable.

The comments, the episode reactions, the character votes, ten years of arguing with strangers about a finale? None of that exports. Anywhere.

And that was the product. The watch history was the database; the arguing was the reason to open the app. We're not mourning a list of episodes. We're mourning a place.

Offboarding is UX too

Nobody designs the death of a product, and it shows. Since the announcement: silence.

We spend months on the welcome screen — the empty states, the tooltips, the first-run delight. And then, at the other end, nothing. No farewell, no explanation with a human in it, no thoughtful export of the things people actually cared about.

The last impression a product leaves is still an impression. You'd think we'd design the funeral with the care we give the welcome screen.

offboarding: the flow nobody puts in the portfolio

The migration, from the inside

Then there's the migration, which has been fascinating to watch from within.

The community scattered, everyone chasing the one feature they couldn't live without. And the feature hunt wasn't the worst of it. It was losing everything in one place.

Movies, series, anime — one app. The alternatives quietly re-fragment that, and suddenly I'm app-hopping like it's 2015.

Refract, the app I landed on as a fresh TV Time orphan, went from 3,000 to 130,000 users in days. It crashed under the weight of everyone's collective grief and has been shipping updates like their lives depend on it. Real respect for handling a stampede they never asked for.

Are we building better products, or nicer coffins?

But watching that migration surfaced the question I actually can't stop thinking about.

Half the internet is telling these apps: just make it exactly like TV Time. And I get it. A decade of muscle memory is real. Your thumb knows where the button was. Familiarity is comfort when everything else got deleted.

But if every survivor rebuilds the same corpse, we don't get a new app. We get a Weekend at Bernie's situation with a fresh coat of paint.

So where's the line between honouring the muscle memory people are grieving, and letting a product actually have its own spine?

If we mourn the community but only let people export the data — and then beg every new app to become a clone of the dead one — are we designing better products, or just building nicer coffins?

Genuinely asking. Especially the folks who've had to turn a product off, or bury someone else's.