Roadmap
Solo project, so these are intentions rather than promises, and things move between groups as priorities shift. If something you want isn't here, open an issue or say so in Discord.
Being built now.
A free iOS edition that keeps everything on device with iCloud sync across your Apple devices, no server to run. Point it at your own Librarium later if you want to.
Field-level last-writer-wins with per-field timestamps, incremental deltas and tombstones. Underpins Lite, and fixes the flaky read-only offline cache for self-hosted users as a side effect.
Queued up, not started.
Drop in an export from any of them and Librarium hydrates the catalogue with metadata and covers from whichever providers you have enabled.
Deploy templates so you can stand up your own instance on a cloud host without hand-rolling Compose. Railway first, then others. Your instance, your data, your bill.
Off by default, and gated twice on self-hosted: an operator flag plus per-user consent. The code that sends lives in the public repos.
There is no path for this in the UI today.
Covers currently come back as a 128px thumbnail. Providers expose larger images; this makes that an option.
Wanted, no date, may change shape.
ISBN is already optional, but four things make older collections awkward: no way to describe what is inside an anthology or an Ace Double, publish dates that turn "1932" into 1 January 1932, no per-copy record for condition or provenance, and no identifiers beyond ISBN. The first is a real schema change; the rest are cheaper.
Reviews marked visible to members are stored but never shown to anyone else, so the field is half built. This would surface them on the book page, same-library scope only, with private notes staying private.
Asked about often enough to be worth answering. These aren't happening.
Cancelled. Running a hosted service means being on call for other people’s servers. One-click deploy templates are the answer instead: your instance, your data. Nothing is held back from self-hosted for a commercial tier.
I don't have an Android device to test on, so there's nothing to develop against. The web UI works in a mobile browser in the meantime. This could change if I pick one up.
Running several of your own servers and switching between them is supported. A cross-instance social graph is a different product.