Default apps: choose for portability, not habit

An archived personal list of default apps attracted links to this address. A list of someone else's choices would age quickly and would imply that this edition uses their accounts. This new guide asks a more durable question: can you leave an app without losing your work?

Choose a default by workflow

Make a short inventory: mail, notes, calendar, files, browser, password manager, photos and RSS. For each, write down what must work offline, what must sync, which people or devices you share with and how much recovery time you can tolerate. A popular app can be a poor default when its export path fails your real data.

Test the exit before the move

Export five representative items and import them into a second tool. Include formatting, attachments, dates and a non-ASCII filename. Compare what arrived with the originals. Do this while the old account still works. A nominal “export” button does not prove that metadata or relationships survive.

For a browser, test bookmarks and passwords separately; for a notes app, test links between notes and attachments; for a calendar, test recurring events and time zones. Keep an encrypted local backup of the exported files and rehearse opening it on another device.

Privacy and continuity are separate tests

Check where data is stored and who can read it, but also examine account recovery, update cadence and whether a service can unexpectedly disappear. End-to-end encryption may protect content from a provider while making forgotten credentials harder to recover. Write down which trade you are accepting.

Change one category at a time

Move a noncritical category first, leave both tools available for a brief overlap and decide what happens to the old copy. For essential accounts, keep working authentication and backup codes until the new setup is verified. An app migration is complete when normal work and recovery both succeed, not merely when an icon appears on the dock.