What Happens When Your Note App Dies?

What happens when your note app dies is a sequence, not an event. The company posts a sunset blog. An export window opens. A read-only window follows. Then the servers go dark and a backup file you may or may not have downloaded becomes the only copy. Mozilla shut down Pocket on July 8, 2025 along this exact arc.¹

This essay is a documentary post-mortem of five shutdowns that emptied real users' notebooks: Pocket (Mozilla, July 8, 2025)¹, Google Reader (March 13, 2013 announcement, July 1, 2013 sunset)², Springpad (May 21, 2014 announcement, June 25, 2014 sunset)³, NaNoWriMo (April 2025)⁴, and Evernote's transformation under Bending Spoons (2023–2024).⁵ Each story is sourced to the official shutdown notice, a status page or Wayback snapshot, and the user-side reaction on Hacker News or Reddit. The aim is not to grieve. It is to inventory how the procedure unfolds, what data survives, and which export decisions — made years earlier — decided the outcome.

The standard shutdown sequence

The standard shutdown sequence is four phases: the announcement post, the new-signup freeze, the export window, and the read-only or full sunset.¹² Pocket compressed all four into roughly two months.¹ Google Reader took just under four months.² Springpad gave users five weeks.³ The export window is the only phase the user controls, and most users miss the email.

Mozilla's "Future of Pocket" announcement on May 22, 2025 closed new signups immediately, set the apps to stop working on July 8, 2025, and kept exports available until October 8, 2025 — a roughly five-month export window for a service that had grown across more than a decade of use.¹⁶ Google's "A second spring of cleaning" post on March 13, 2013 set Reader's shutdown for July 1, 2013, with a Google Takeout export route active through the same date.² Springpad founder Jeff Janer's May 21, 2014 farewell letter set the cutoff at June 25, 2014 and pointed users to a JSON+HTML export.³ NaNoWriMo's board posted the closure announcement on April 1, 2025 after months of declining trust over an AI-content moderation crisis, and gave participants a window to download forum and project data before archives went read-only.⁴⁷ Each of these followed the same template, in roughly the same order, with roughly the same amount of warning.⁸

Pocket: a decade of saves, five months, one CSV

Pocket's shutdown is the cleanest recent example because Mozilla published every phase on a single page, with dates, on May 22, 2025.¹ Tens of millions of saves spanned more than a decade of Pocket's life under Read It Later and then Mozilla.⁶ Mozilla offered one export: a CSV of saved URLs and tags. Article body text was not exported.¹⁹

Mozilla's official announcement framed the wind-down as a refocusing of effort onto other browsing-habit projects, and locked the dates plainly: new signups and downloads closed on May 22, 2025; apps stopped working on July 8, 2025; and the export tool remained live until October 8, 2025.¹ The export schema, published in Mozilla support documentation, is a CSV containing title, URL, time added, tags, and status — no offline article bodies, no annotations, no read position.⁹ On Hacker News the announcement thread climbed to over a thousand points and hundreds of comments within a day, with commenters mourning the loss of saved snapshots rather than the bookmark list.¹⁰ Wallabag, the open-source self-hosted alternative, published a Pocket migration guide within days, and its GitHub star count rose noticeably in the week after the announcement.¹¹¹² The signal in the noise: the export is a list of links, not a library of saved reading. The library is what users thought they had.

Google Reader: the canonical shutdown the internet still cites

Google Reader announced on March 13, 2013 that the service would close on July 1, 2013, ending an eight-year run that had ~30 million estimated users at peak.²¹³ Google Takeout offered a complete export of OPML subscriptions, starred items, and shared notes. Users had 110 days.² The shutdown is now the canonical reference for the SaaS-shutdown genre.¹⁴

Google's "A second spring of cleaning" post was terse, attributing the closure to declining usage and an internal push to focus on fewer products.² Within hours a Change.org petition titled "Keep Google Reader running" passed 100,000 signatures; it eventually exceeded 150,000 by the July sunset.¹⁵ The Verge's March 13, 2013 coverage by Ellis Hamburger framed the loss as cultural, calling Reader a way many on the web had learned to follow it.¹⁶ Marco Arment, on his blog the same day, argued that Reader's shutdown was a setback but also an opening for the open web.¹⁷ Feedly grew from roughly 4 million users in March 2013 to 12 million by mid-July 2013, almost entirely on Reader migrants.¹⁸ OPML — the open subscriptions format — survived the shutdown as a portable standard, and a decade later remains the way users move feed lists between RSS readers.¹⁹ The lesson the rest of the internet took from Reader is that an open file format is what makes a shutdown survivable. The lesson the rest of the internet has not yet learned is that most note apps do not have an OPML.

Springpad: five weeks and a JSON dump

Springpad, founded in 2008 and once positioned as an Evernote rival with around 5 million users, announced its shutdown on May 21, 2014, set the closure date for June 25, 2014, and gave users roughly five weeks to export a JSON+HTML archive.³²⁰ Founder Jeff Janer's farewell letter cited a monetization failure.³ Imports to Evernote and Pocket were offered.²¹

Janer's May 21, 2014 letter, archived on Springpad's blog, conceded that the company had built a large and active user base but had failed to monetize it sufficiently to continue.³ The export tool produced a ZIP containing a JSON file and a folder of HTML snapshots per notebook — a format chosen specifically so users' data would travel in something they could actually open.³ The Internet Archive snapshot from June 24, 2014 — one day before sunset — confirms the export tool was still live.²² On Hacker News, the May 21, 2014 thread drew users praising the choice of JSON over a proprietary dump.²³ TechCrunch's May 21, 2014 piece by Sarah Perez documented the migration paths the team published.²¹ What stood out about Springpad, in retrospect, was the founder's tone: the letter was apologetic, explicit about the export, and did not pretend the closure was a graduation. The pattern shows up in fewer than half of subsequent SaaS shutdowns.⁸

NaNoWriMo: a community sunset, not a SaaS sunset

NaNoWriMo, the National Novel Writing Month nonprofit that since 1999 had hosted hundreds of thousands of writers across Novembers, posted its closure announcement on April 1, 2025 after a moderation crisis, board resignations, and collapsing donations through 2024.⁴⁷ The site moved into archive-only mode; user word-count histories, forum posts, and project drafts went read-only and then offline through the spring of 2025.⁷²⁴

NaNoWriMo's April 1, 2025 announcement on the official site declared the board's vote to dissolve the organization, with the site to remain accessible in a limited capacity through the end of April 2025 before going to archive.⁴ The Verge's coverage contextualized the collapse around the 2024 AI-content controversy and a deeper, slower failure of community trust.²⁵ On the r/nanowrimo subreddit, a stickied post collected migration links to Notion, Scrivener, and a self-hosted word-count tracker script; the thread drew over a thousand upvotes and hundreds of comments.²⁶ What made NaNoWriMo unusual is that the lost data was not just the project file — it was twenty-five years of community writing logs, forum threads, and badge histories that no individual user had ever exported because the community had felt permanent. The Internet Archive captured what it could; entire subforums survive only because volunteers ran a final crawl in late March 2025.²⁷ When a community sunsets, the export tool is the wrong unit of analysis. The unit is the volunteer with a scraper.

Evernote, Day One, and the slow-shutdown pattern

Not every shutdown is sudden. Evernote's transformation under Bending Spoons since the 2022 acquisition, and Day One Journal's evolution under Automattic since the September 2021 acquisition, show the slow-shutdown pattern: the company does not close, but the product the user signed up for steadily disappears.⁵²⁸ The export still works. The reasons to stay accumulate against the reasons to leave.

Bending Spoons' press release framed the deal as a long-term commitment.²⁹ By July 3, 2024, TechCrunch reported on a second layoff round and the relocation of operations to Europe.⁵ Evernote's December 4, 2023 official blog post capped Free accounts at 50 notes and 1 notebook.³⁰ The product still exists. The product the 2014-era user signed up for does not. Day One Journal, acquired by Automattic on July 13, 2021, has continued to ship, and its end-to-end-encrypted journal export remains a clean ZIP of JSON plus media.²⁸³¹ But the standalone Day One company is gone, and the future of the standalone subscription depends on Automattic's roadmap rather than the original Day One team's. These are not failures. They are reminders that "the company shuts down" is one branch of a tree whose other branches — acquisition, pivot, neglect — produce the same final question. Is my notebook still mine, in a format I can open, on a device I control?

What survives, and what decides it

What survives a shutdown is exactly what the user exported, in the format the company chose, before the export window closed. Nothing else. The decisions that determine outcomes are made years earlier, when the user picks a tool with a plain-text export — or doesn't.³²³³ Steph Ango framed the principle in one line in 2023.³²

Ango's "File over app" essay, published July 1, 2023, said: "In the fullness of time, the files you create are more important than the tools you use to create them. Apps are ephemeral, but your files have a chance to last."³² The Ink & Switch team's 2019 paper "Local-first software" added the operational test: your work should continue to be accessible indefinitely, even after the company that produced the software is gone.³³ The European Union's Data Act, in force since September 12, 2025, encodes a version of this as law — Article 23 requires "effective switching" between data-processing services and prohibits contractual obstacles to data portability.³⁴ GDPR Article 20, in force since May 25, 2018, established the data-portability right earlier and weaker: a structured, commonly used, machine-readable format on request, but no time-bound enforcement against shutdown sequences specifically.³⁵ Joel Spolsky's "Things You Should Never Do, Part I," published April 6, 2000, gave the corporate version of the same argument: when you start over, you throw away years of accumulated knowledge and bug fixes.³⁶ Translated to the user's side: when a company starts over — or stops altogether — what survives is the file the user can still open, on a device the user still owns. The export is the contract. The file format is the only enforcement clause that matters when the announcement post drops.

What a reader can do this week

What a reader can do this week is short and structural. Open every note, read-it-later, and journal app you use. Find the export page. Run the export. Open one file in a plain-text editor. If you cannot, your data is portable in name only.³²³³ These moves take an hour.

1. List every app that holds something you care about. Notes, journals, saved articles, drafts. Five minutes with a paper list. The list is usually longer than expected.
2. Open each app's export page and run the export today. Save each export to a single folder you control, named with the date.
3. Open one exported file in a plain-text editor. If the format is .html, .json, or a proprietary archive, your data is portable in name only. If it is Markdown or plain text, you have a working escape route.³⁷
4. Subscribe to the company's status page or blog email. Shutdown announcements arrive there first. The Pocket and Google Reader windows were both posted on the corporate blog before the in-app banner appeared.¹²
5. Set a quarterly reminder to re-export. The next shutdown announcement will not arrive on a convenient day. The export from last month is the difference between a backup and a regret.

Five moves. Each takes a few minutes. None of them requires leaving the app you love today.

Who this is not for

Honest balance is the price of being read. Three patterns of use are mostly unaffected. The user whose only "notes" are calendar events and emails, both of which export trivially. The team whose workspace runs a business and accepts cloud lock-in as the cost of collaboration. The reader who re-finds saved articles via search, for whom a CSV is enough.³⁸

For these readers, the timeline above is context, not call-to-action. The argument is not "leave your app." Apps are tools, and tools have life cycles. Cal Newport, writing on slow productivity, has argued in the same key that the most important productivity decision a person makes is which tools accumulate their work over the years.³⁹ The decision is not which app is best this quarter. It is which file format is still readable in 2040, on a device that has not been invented yet, by a person who may have changed careers twice. That is the only question the five shutdowns above are meant to surface. Read your tool's export documentation before its feature list. The export page is the only page where the company has to be honest. The feature list is the marketing. The export is the contract.

If this argument lands, MNMNOTE (mnmnote.com) stores notes as plain Markdown in your browser — no account, no cloud, and an export that is a .md file your grandchildren can still open.

Frequently asked questions

What actually happened to Pocket?

Mozilla announced Pocket's shutdown on May 22, 2025, set the apps' final working date as July 8, 2025, and kept the data export tool live until October 8, 2025.¹ The export is a CSV of saved URLs, titles, tags, and timestamps — article bodies and annotations were not included.⁹

When did Google Reader shut down, and what could users save?

Google announced Reader's shutdown on March 13, 2013, with the service closing on July 1, 2013 — about 110 days of warning.² Google Takeout offered an OPML export of subscriptions, plus archives of starred items and shared notes.² Feedly grew from ~4 million to ~12 million users in the four months between announcement and sunset.¹⁸

What happened to Springpad?

Springpad, founded in 2008 with roughly 5 million users, announced its shutdown on May 21, 2014 and closed on June 25, 2014 — five weeks.³²⁰ Founder Jeff Janer cited a monetization failure and pointed to a JSON+HTML export plus migration paths to Evernote and Pocket.³²¹ The Internet Archive snapshot from June 24, 2014 shows the tool still live.²²

Why did NaNoWriMo close in 2025?

NaNoWriMo's board announced dissolution on April 1, 2025 after the 2024 AI-content moderation controversy, board resignations, and collapsing donations.⁴⁷ The Verge's coverage framed it as a trust failure rather than a financial one.²⁵ User word-count histories, forum threads, and project drafts went read-only and then offline through April 2025.⁴ Volunteers preserved subforums via final scrapes.²⁷

What does the EU Data Act say about shutdowns?

The EU Data Act, in force since September 12, 2025, requires "effective switching" between data-processing services under Article 23 and prohibits contractual obstacles to portability.³⁴ GDPR Article 20, in force since May 25, 2018, established the right to a machine-readable export but did not bind shutdown procedures.³⁵ Together they raise the EU legal floor.

Is a CSV or JSON export "good enough"?

It depends on what was inside the app. A CSV of saved links captures URLs but not article bodies, which is why the Pocket export felt thin.⁹ A JSON journal dump may include text but lose formatting and links. A Markdown export is the highest-fidelity portable format, because the export and the original are the same file — the format is an open spec, not a vendor artifact.⁴⁰⁴¹

How is MNMNOTE different in this respect?

MNMNOTE stores notes as plain Markdown in your browser — no cloud, no account, no proprietary format.³⁷ The export is the file. There is no shutdown sequence to wait through, because the data was never on a server. The Ink & Switch local-first paper sets the standard the project follows.³³

References

FAQPage JSON-LD

Article JSON-LD