A Journaling App That Works on iPhone and Android

2026-09-30 · Yesterself

Your phone lasts three or four years. A journal, if it works at all, outlasts several of them. Somewhere in that span there is a decent chance one replacement comes from the other side of the fence — a work phone on Android, a good trade-in deal on an iPhone, a household where one person is on each. That mismatch of timescales is the whole problem. You are choosing a place to keep decades of writing based on the operating system you happen to be holding this year.

This piece is not a ranked list. It is about the one property that decides whether your journal follows you across a platform change, how to test that property before you need it, and what a one-ecosystem journal actually costs you later.

The thing that breaks is not the writing

When people picture a bad switch, they picture lost entries. That is rarely what happens. Your words are usually still there, sitting in a backup or a server, perfectly intact and completely unreachable from the phone in your hand.

What breaks is the delivery route: the mechanism that gets an entry from the device you wrote it on to the device you are holding now. Judge a journal on that route, not on its feature list. Every feature you like is worth nothing on a phone that cannot open the file.

Five sync models, and which ones survive a switch

1. Platform account sync. The app leans on the operating system's own cloud — the entries ride along in the platform backup, and there is no app on the other store. This is the most convenient model to live with and the most brittle to leave. Everything works beautifully until the moment it does not work at all.

2. Neutral storage, single-platform app. The entries sit in a general-purpose cloud drive that exists on both platforms, so it feels portable. It often is not. The storage location being cross-platform does not mean there is an app on the other side that knows how to read that particular folder. You end up with a directory of files you can see but not open as a journal.

3. The app runs its own account and ships on both stores. This is the mainstream cross-platform answer, and it works: install on the new phone, sign in, wait for the download. Your dependency shifts from a platform to a company. Worth asking how long they have shipped both versions, and whether the second one gets features at the same time or a year late.

4. Device-to-device encrypted sync. The devices hold the key and the server holds unreadable ciphertext. Moving to a new phone means proving you are you with something you kept — a recovery phrase, a scan from the old device — rather than signing into a platform. This survives a switch as long as the app exists on both platforms, and it survives the company knowing what you wrote.

5. Plain files in a folder you control. Markdown or text, one file per entry, kept wherever you like. Nothing to migrate, because there is nothing tying it down. You pay for that in features: no reminders, no linked photos, no search that understands dates. Some people happily accept the trade for an archive nothing can lock.

Models three, four and five cross the border. One and two do not, without manual work.

The mixed-device household is the more common case

Switchers get all the attention, but plenty of people never switch and still need this. An iPhone with a Windows laptop. An Android phone with an iPad. A personal phone on one platform and an employer's on the other. A couple where the shared part of the journaling — a letter, a prompt, an anniversary note — has to reach a phone that is not yours.

For those situations, ask two extra questions. Is there a web or desktop version, and can it write, or only display? And does the second platform get real feature parity, or a thinner version that mostly views? A read-only companion is a viewer, not a second home, and it will frustrate you on the days you actually want to write on the other device.

The portability drill

Do this on a quiet evening, not on the day the new phone arrives.

1. Export now. Find the export in the settings and run it. If you cannot find it in five minutes, that is your first finding.
2. Choose the plainest format offered. Text, Markdown, or JSON travels further than a proprietary archive. PDF is a picture of your journal, not your journal.
3. Open the file somewhere else. A computer, a friend's phone, a device from the other ecosystem. Reading it back on the same phone that made it proves almost nothing.
4. Look for what quietly fell off. Photos and audio are the usual casualties, then timestamps that shifted by a timezone, then tags and formatting. Pick five entries you remember well and check them line by line.
5. Count. If the app says you have 812 entries, the export should contain 812 entries. Anything that lived only on the server will show up as a gap.
6. Repeat quarterly, and after any big update or plan change. Put it in the calendar. Exports change format without announcement.

If you want the short version: a journal you have never exported is a journal you do not yet know you can keep.

Yesterself is being built for both iPhone and Android, and the identity is deliberately not a platform account — no email, no password, just twelve words you hold. Moving to a new phone means entering those twelve words. The archive is end-to-end encrypted, the server stores ciphertext it cannot read, and export is free forever, including on the free tier. Sync across devices is part of the paid tier; the free tier writes and exports on one device, indefinitely. It is not released yet, so there is nothing to install today — only a waiting list.

What a single-ecosystem journal actually costs

The price is not the subscription. It is paid in three other currencies.

• It narrows your next phone decision. Four years from now, a switch that would otherwise be a Saturday afternoon becomes a question about your diary. People stay on a platform for less.
• It cuts your household in half. If the person you would share a letter with is on the other platform, the shared part of the journal simply does not exist for them.
• It makes the archive a hostage. Not through malice — usually through a discontinued app, an abandoned second version, or a plan change that puts export behind a wall. The end state is the same: writing you own and cannot open.

Questions to ask before you commit

• Is there a real app on both stores, and when was each last updated?
• Where does sync actually happen: the platform's cloud, the app's own servers, or between my devices?
• What exactly do I type on a new phone to get my journal back?
• What does the export contain, and is it available without paying?
• If this company closed next year, what would I still be holding?

None of those need a support ticket. Ten minutes on the settings screen and one export answers most of them.

If the new phone arrives this month

1. Export from the old phone before you wipe it, and copy the file somewhere that is not either phone — a laptop, a drive.
2. Set the new phone up and get the journal running first, before the old one goes back in the box.
3. Compare a handful of dated entries side by side on both screens, including one with a photo and one from years ago.
4. Only then trade it in. A device you no longer have is a backup you no longer have.

The answers you collect doing this stay useful long after the app you chose has been replaced. You are not picking software for this phone. You are picking the conditions under which your own writing will still open on a device that does not exist yet.

Common questions

Does a cross-platform journal have to be less private?

No. What matters is where the encryption key lives, not how many app stores the app is in. A journal can be on both platforms and still keep the key on your devices rather than on a server.

Can I move my entries from an iPhone-only journal to Android?

Usually yes, but by hand. Export to an open format on the iPhone, move the file off the device, then import into the new app and check dates and attachments survived.

What is the single best test of portability?

Export today and open the file on a computer or phone from the other ecosystem. If you cannot read it there, the journal is tied to the platform no matter what the marketing says.

Is a web version enough to count as cross-platform?

It helps in a mixed-device household, but check whether it can write as well as read, and whether it works offline. A read-only web view is a viewer, not a second home.

How often should I re-test my export?

Once a quarter, and again after any major app update or plan change. Exports quietly change format, and the worst time to discover that is the day you switch phones.