Published
Why Cross-Platform Reading Sync Is Harder Than It Looks
Apple Books remembers your place across your own devices. So does Google Play Books. Neither remembers it on the other's platform — and that's not an oversight, it's how the systems are built.
Introduction
You finish a chapter on your phone. Later, on a different device, you open the same file — and it doesn't remember where you were. It's a small annoyance, but understanding why it happens is worth a few minutes: the cause isn't a bug in any one app, it's a gap between how iOS and Android are built. Sync inside one company's ecosystem is mostly solved. Sync between two different ones almost never is, and the reasons are more concrete than "the companies don't talk to each other."
What it is
The short version
Reading position sync means an app remembers your exact spot in a document — not just which file you had open, but the location inside it — and shows you that same spot the next time you open the file somewhere else. It sounds like one feature. It's really two different problems wearing one name, and the split comes down to the file format.
Two formats, two ideas of "where you are"
PDF is fixed-layout: every page is locked to a specific size, so your position is a page number and a zoom level. That works fine until the screen changes size, which is why a PDF looks different on every device — page 42 on a laptop and page 42 on a phone aren't showing you the same amount of text. EPUB gets around that by being reflowable: text reshuffles to fit whatever screen it's on, more readable but with a catch — "page 42" no longer means anything stable. An app has to describe your position relative to the text itself, and reading apps don't all implement that locator the same way. Two apps opening the identical EPUB can each hold a private, incompatible idea of "where you are."
Why it matters
Same-platform sync already has a lot of moving parts
Before you even get to a different platform, sync within one company's ecosystem depends on things that all have to be true at once. Apple's own troubleshooting guidance for Books lists them plainly: you have to be signed into the same Apple ID, have iCloud syncing turned on for Books, and have a working connection on every device involved. If you've kept your place across an iPhone and an iPad, you've relied on all three of those staying true — and that's still confined to one account with one company.
The piece that's actually missing for cross-platform
Here's the concrete reason an iPhone and an Android phone don't sync automatically: iCloud Drive doesn't have a native Android app. There's a Windows companion app and a browser view at iCloud.com, but nothing an Android app can quietly hook into the way an iOS app can. Google's side has the mirror-image problem: Play Books syncs your uploaded files across your own Google account, but that system was built for Google's apps, not Apple's. Each company solved sync for its own ecosystem, then stopped there.
Where you'll see it
The everyday version of this
It shows up any time you send yourself a document and open it somewhere else later — a PDF you emailed yourself, an EPUB you AirDropped, a contract you meant to finish on a different device than the one you started on. If you've tried reading EPUB files on Android without an account, you've probably noticed the file arrives fine. It's the position inside it that doesn't.
Who runs into it most
This lands hardest on people who read across two different ecosystems by necessity, not by choice: a work phone on one platform and a personal phone on the other, or a shared document handed between someone on iOS and someone on Android. It's less about brand loyalty and more about the ordinary reality of reading across more than one device.
How Margina handles it
The honest answer: no, not as of 2026-05. Margina doesn't sync reading position between an iPhone and an Android device, and we're not going to claim otherwise.
The apps that do offer real cross-platform sync — BookFusion is a good example — get there by building and maintaining their own account-bound server that every version of their app talks to. That's a reasonable choice, and it works. It's also the opposite of what Margina is: a local-first app with no account and nothing on a server holding your reading data. That's the tradeoff — a private, local library on one hand, a server-mediated bridge between platforms on the other. Margina picked the first one on purpose. If what you want in the meantime is a safe copy of your library rather than cross-device position, backing it up to your own iCloud is the closest fit for Margina's approach.
Frequently Asked Questions
Can I sync my reading position between an iPhone and an Android phone?
Not through any built-in system tool. Apple Books syncs through iCloud, and Google Play Books syncs through your Google account, but each only works between devices signed into that one company's account — neither talks to the other. A handful of third-party apps solve this by building and maintaining their own account-bound cloud backend, which is a different tradeoff than a local-first app makes.
Why doesn't iCloud just work on my Android phone?
Apple ships iCloud Drive as a native, deeply integrated feature on iOS and macOS, but there's no Android app for it — only a limited browser view at iCloud.com. An iOS app can read and write iCloud files in the background; an Android app has no equivalent hook to plug into, so it can't quietly stay in sync the way two Apple devices can.
Does Margina sync reading position between iPhone and Android?
Not as of 2026-05. Margina is local-first by design — no account, no server holding your reading data — which is what makes it private. It also means there's no company-run backend in the middle to carry your position from one platform to another. Everything you send yourself with Margina stays on the device you sent it to.
Is this a format problem or an app problem?
Both. PDF is fixed-layout, so "where you stopped" is a page number and a zoom level that doesn't reflow across screen sizes. EPUB is reflowable and needs a text-relative locator to describe a position consistently — and reading apps don't all implement that locator the same way. On top of that, each app's sync feature is something the company built on its own cloud, not something baked into either file format.
What can I do in the meantime?
Pick a primary device for a given document and stick with it, or move the file itself — not just the position — between devices with AirDrop, email-to-self, or a shared drive folder, and re-find your place by memory or a bookmark you set yourself. It's more manual. It also doesn't require handing your reading habits to a server.
Conclusion
None of this is a bug waiting on one update to fix it. It's a structural gap between two ecosystems that were each built to serve themselves, and the only apps that currently paper over it do so by putting a company's server in the middle. Margina takes the other path — private, local, and honest about what that means it can't yet do. If cross-platform sync ever changes here, it'll be because we found a way to do it without giving up the local-first part.