What to do when an app you rely on shuts down

The shutdown notice is usually one paragraph in the release notes, and the date in it is closer than it looks. Mealime announced it would close on October 21, 2026, with no export button, and people who had spent years building recipe collections in it suddenly had a few weeks and a screenshot tool. We wrote about that case in Mealime is shutting down with no export. The lesson generalizes to every app you depend on.

The first hour: get your data out

Do this before you research replacements. The replacement can wait; the data cannot.

1. Look for an official export. Check settings, account pages and the help center for words like export, download, backup or archive. A CSV or JSON file is ideal because other tools can read it.
2. Ask for your data formally. If the company is covered by privacy law, you usually have a right to a copy. Under the EU's GDPR, a data access request generally has to be answered within one month, and GDPR also includes a right to data portability. California's CCPA gives businesses 45 days to respond to a request to know. Send the request by email to the address in the privacy policy, today, because a company that is winding down may stop answering.
3. Screenshot what matters, then copy the best of it as text. Screenshots are fast, but you cannot search or paste them later. For the ten things you actually use, copy the words into a plain note.
4. Record your settings. The preferences you spent months tuning, such as filters, units, reminders and categories, rarely survive any export. Write them down.

The best time to find out whether an app can export your data is the day you start using it, and the second best time is today.

Signs an app might be next

No single signal means much, but a few together are worth noticing:

• Updates have stopped for many months, or release notes have become vague.
• The company was acquired and the product now points you toward the parent company's apps.
• Features are quietly removed, or support replies slow down.
• Pricing changes suddenly, especially a lifetime plan that disappears.
• The app needs a server for everything, so it cannot function once that server is switched off.

That last one matters most. An app that keeps your data on its own servers can take your data with it when it goes. An app that stores data on your device keeps working, at least in its current form, even if the developer disappears.

Choosing a replacement that won't do this to you again

When you evaluate what comes next, ask four plain questions:

• Where does my data live? On your device, in your own cloud storage, or on the company's server?
• Can I get it out? Look for an export you can test on day one, not a promise of one.
• Does it need an account for the core job? If a simple tool demands a login, something you care about lives on their side.
• What happens offline? Turn on airplane mode and try the main task. If it still works, the app is doing its work on your phone.

This is the thinking behind the apps on our apps page: most of them run on the device, need no account, and keep working without a connection. That does not make them immune to change, but it means a closure notice never takes your records with it.

Habits that survive any tool

The durable fix is not finding the perfect app. It is keeping the important parts of your life in forms that outlive apps.

• Keep a plain-text or PDF copy of anything you would be upset to lose, refreshed a few times a year.
• Put a recurring calendar reminder on the first of each quarter: export from every app that allows it.
• Prefer tools that use common formats such as CSV, PDF, photos in your camera roll and plain notes.
• Keep a short list of the apps you depend on, with a note next to each about how to get your data out.

Apps will keep coming and going. The recipes, records and notes that matter to you can stay put.