For shared progress and highlights, sign in to Binge Reader in your Android browser and use the web reader. For local reading in another app, connect that app to the Binge Reader OPDS feed, understanding that its progress normally stays separate.
Use the browser for continuity
Open Binge Reader in Chrome or another modern browser, launch a book, and adjust reader settings. Add the site to the Home screen when offered. This route keeps supported annotations and position in the Binge Reader account.
Use OPDS for app choice
If you prefer Moon+ Reader or another OPDS client, add the private catalog and download a book. The OPDS route is excellent for acquisition but normally does not return the app’s position or highlights.
Make the tradeoff explicit
Do not alternate between two Android readers without a plan. Choose the web reader when continuity matters, or choose the local app when its reading controls matter more and keep a chapter locator for manual handoff.
The details, at a glance.
| Consider | What to look for |
|---|---|
| Web reader | Shared Binge Reader position and annotations |
| Home Screen | Convenient browser-based launch |
| OPDS app | Browse and download to another reader |
| Handoff | Separate state unless the reader has a specific sync integration |
A few things worth asking.
Which route syncs with my Kobo?
Use the Binge Reader web reader for the shared-state route, then run Kobo Sync before opening the book on the device.
Can any Android reading app return highlights through OPDS?
No. OPDS alone covers catalog discovery and acquisition, not annotation synchronization.
Go to the source
Documentation consulted for the routes and terminology on this page. Product behavior can change; verify your exact setup.
OPDS specificationsWritten by Binge Reader. Our comparisons explain documented workflows and practical tradeoffs; they are not independent product benchmarks.