Cross-Platform Note-Taking, and a Cautionary Tale

TL;DR

The classic mistake is keeping your notes in an app tied to one brand (Apple Notes, Samsung Notes). It feels great until you switch phone or computer and discover your notes will not come with you. The fix is to choose notes that are cross-platform and stored in a portable format, so they follow you onto any device, this year or in ten years.

• Avoid single-ecosystem apps (Apple Notes, Samsung Notes) for anything you want to keep long term. They lock your notes to that brand.
• Prefer apps that run everywhere and can export cleanly: OneNote, Obsidian, Joplin, Standard Notes, Google Keep.
• The most future-proof format is plain text or Markdown, which any app on any operating system can open, now and forever.
• Split quick jots (a Google Keep style app) from serious, structured notes (OneNote, or a Markdown notes folder). Keep both cross-platform.
• Favour a real app with a local copy over a web-only one. A website locks you out during a provider outage or any time you are offline, which on Linux is a common trap because several big note apps have no native client.

Now for the more technical explanation

Why notes get trapped

Note lock-in happens for two reasons, and you need to beat both:

1. The app only runs on one ecosystem. Apple Notes is effectively Apple-only; Samsung Notes is Samsung-only. Switch to Android or Windows and the app simply is not there in any real form.
2. The format is proprietary. Even a cross-platform app can trap you if its notes are stored in a private format that nothing else can read, so “exporting” gives you a mess or nothing usable.

Portable note-taking means solving both: a cross-platform app, a portable format, and a sync layer that you are comfortable relying on. Get those three right and switching devices becomes a non-event.

The two things that actually matter

• Cross-platform reach: the app (or your files) must be usable on every OS you might move to: Windows, macOS, Linux, Android, iOS, and ideally the web.
• Portable format and export: you must be able to get all your notes out into a format another app can read. Plain text and Markdown are the gold standard because they are just text files. HTML is decent. A proprietary binary format is a warning sign.

A useful test before you commit to any app: put a handful of notes in it, then export everything and open the result somewhere else. If that is painful now, it will be far worse after five years of notes.

Split quick notes from long-term notes

As with a lot of cross-platform setups, one tool rarely does everything well. A clean split:

• Quick capture: fast, low-friction, synced everywhere, for shopping lists, reminders, and half-thoughts. Structure matters less than speed.
• Reference and long-form: organised, searchable, built to last, for research, documentation, study, and anything you will still want in years.

Using two purpose-fit tools beats forcing one app to be both.

The pillar people forget: offline access

Before the app-by-app rundown, the one criterion people skip. “Cross-platform” quietly includes “works in a web browser”, and a website is not the same thing as a real app. This is the trap that bites hardest, and it is worth a warning because the failure is invisible right up until the moment it ruins your day.

Here is how I learned it, the hard way. I had taken the day off work to prep for an important certification exam the next morning, with every one of my meticulously curated study notes living in OneNote. I have been a Linux user for years, and Microsoft does not make a native OneNote app for Linux, so my notes lived in the website version, which I had dressed up as a tidy PWA (progressive web app) to feel like a real app. I woke up, went to study, and simply could not get in. For the first couple of hours I assumed the problem was my machine, and I burned real time troubleshooting the wrong thing, denial as much as diagnosis. It was a Microsoft outage, and it ran for seven-plus hours.

At one point I fired up a Windows VM with the actual OneNote desktop app, ever so hopeful that would rescue me. It did not: I had not used that app in so long that my recent notes had never synced down to it, and with the service now down they could not. That is the detail that turned a bad day into the real lesson: a local-first app only saves you if it has already synced. In the end I gave up on the notes I had planned to drill, studied whatever else I could scrape together, and only got a couple of hours with my actual material when OneNote limped back late in the afternoon. All told I lost six or seven hours the day before an exam, beside myself for most of them. (I passed anyway, but that is not the point: the tooling should never have made the night before a gamble.)

The rule that comes out of it is genuinely simple: use a real desktop app on a machine you use regularly, and let it sync. That one habit covers both ways things can go wrong. If the machine dies, your notes are safe in the cloud, synced up. If the cloud has an outage, you do not care, because you are holding a full local copy. Provider outages are usually minutes to a few hours and are not that frequent, so a regularly-synced app is almost always current: the odds of an outage landing in the exact window where your local copy is stale are tiny. My mistake was not having that habit. I was leaning on the web on my daily machine, and the one desktop app I could reach was a long-dormant install that had never synced my recent notes. Neither had a current local copy when it mattered.

So the answer is not complicated. Do not rely solely on cloud-only note-taking. Keep a real app, on a machine you actually use, quietly syncing in the background, and both failure modes stop being able to touch you at once.

This lands hardest on Linux, so if you use it, read this twice:

• Several of the big note apps (OneNote among them) have no native Linux client at all, which pushes you onto the web version and straight into the trap above.
• The distro app stores do list options, but a lot of them are just Electron wrappers around the same website, so they look like an app while offering no genuine offline capability. Check whether a given one actually stores notes locally before you trust it.
• The third-party clients that do work tend to come from small developers with no long track record, and they have a habit of breaking on the next app or OS update. Fine for convenience, risky as the only thing standing between you and your notes.

It is one more reason the Markdown-in-a-folder approach keeps winning: the notes are real files sitting on your disk, so they are offline by definition. No app and no server has to be reachable for you to open them.

What is the best cross-platform note-taking app?

Plain text / Markdown in a synced folder (the durable choice). Your notes are ordinary .md or .txt files in a folder that syncs (OneDrive, Dropbox, Nextcloud, or a Git repo). Edit them with Obsidian, Joplin, or literally any text editor on any platform.

• Pros: maximum longevity and portability, no lock-in, you own the files and choose the sync, works offline, searchable with normal tools.
• Cons: less hand-holding, images/attachments need a little discipline, no fancy shared databases.
• Best for: anyone who wants notes that outlive any single app or company.

OneNote. Genuinely cross-platform (Windows, macOS, iOS, Android, web) and free, great for mixed content (typed notes, ink, images, clippings).

• Pros: everywhere, free, flexible page/section model, strong for study and mixed media.
• Cons: proprietary format; exporting is per-section and clunky, so it is portable to use but not the easiest to leave. And note the platform list above has no Linux: on Linux you are on the website, with the offline exposure covered above.
• Best for: structured, mixed-media notes across Microsoft and non-Microsoft devices.

Google Keep. Excellent quick-capture app, with fast sync and reminders. Native apps only on Android and iOS, though: on Windows, macOS and Linux there is no official desktop app at all, only the website (or a PWA wrapped around it).

• Pros: frictionless on mobile, great for lists and quick thoughts.
• Cons: limited structure and formatting; export is via Google Takeout (HTML/JSON), fine for a bulk escape but not elegant. And because it is web-only on every desktop, it carries the offline exposure described above: no connection or a Google outage means no notes on your computer. Fine for the throwaway quick-capture tier, not for anything you must be able to reach.
• Best for: the quick-capture tier.

Joplin and Standard Notes (open and privacy-friendly). Both are open source, cross-platform, and built around portability. Joplin stores Markdown and syncs via Dropbox/OneDrive/Nextcloud/WebDAV/its own service, with optional end-to-end encryption and a good Evernote importer. Standard Notes is end-to-end encrypted by default with a strong longevity focus.

• Pros: portable formats, E2EE options, no single-vendor lock-in, self-host friendly.
• Cons: slightly less polished than the big commercial apps; you manage more yourself.
• Best for: people who want privacy and independence without hand-rolling everything.

Notion and Evernote. Powerful, cross-platform, feature-rich (databases, web clipping, collaboration).

• Pros: capable and convenient, sync everywhere.
• Cons: cloud lock-in, and export quality varies (Notion exports to Markdown/HTML/CSV but complex databases do not survive cleanly). You are trusting the vendor to stay around and stay reasonable.
• Best for: people who value features now and accept some lock-in.

Apple Notes and Samsung Notes (the lock-in warning). Both are good apps, and both are traps for portable note-taking. Apple Notes is tied to Apple (limited web access, poor export); Samsung Notes is tied to Samsung. They are fine for notes you would not mind losing, but not for anything you want to carry across a device switch.

The sync question

Two broad models:

• App-native sync: the app handles it (OneNote via Microsoft, Notion/Evernote via their cloud, Joplin/Standard Notes via their service). Convenient; you inherit that provider’s availability and lock-in.
• Your own sync: with Markdown-in-a-folder you pick the sync yourself: OneDrive, Dropbox, Nextcloud (self-hosted), or Git (which even gives you version history). More control, and no dependence on a notes company staying in business.

If you already run a cross-platform file service, putting your notes folder inside it is the simplest durable setup: the notes sync exactly like your other files and appear on every device.

A note on privacy

Most cloud note services can technically read your notes (they are not all end-to-end encrypted). If your notes include sensitive information, prefer an end-to-end encrypted option (Standard Notes, Joplin with E2EE, or an encrypted Markdown vault), or keep sensitive notes out of the cloud entirely.

A recommended setup

A pragmatic, lock-in-resistant pairing:

• Quick capture: Google Keep (or any simple cross-platform quick-note app) for lists, reminders, and fleeting thoughts.
• Reference and long-term: either OneNote if you want rich mixed-media across all your devices, or a Markdown notes folder (Obsidian/Joplin) in a synced location if you want maximum longevity and zero lock-in.

Both tiers are cross-platform, so a new phone or a new laptop, even a jump between Apple, Android, Windows, and Linux, changes nothing about where your notes live.

Getting out (migration)

Whatever you use now, know your exit before you need it:

• Find the app’s export, run it, and confirm the output opens elsewhere.
• Markdown and HTML import into most other tools; proprietary formats often need a converter (Joplin, for instance, imports Evernote exports).
• Do a trial migration of a small set of notes to your target app before committing, so you learn the rough edges while the stakes are low.

The goal throughout is simple: your notes should belong to you, not to whichever device or app you happened to start with.

Related

• Making an Android phone and a MacBook work together like an iPhone and a Mac

Written by Tom Langston, IT Infrastructure and Cybersecurity.