who's actually syncing
Clients
Shiori is only a sync server; anything that speaks the wire protocol can be a client. This page tracks what exists today, what's planned, and a few ideas nobody's started yet. If your reader isn't here, the protocol is open and documented; nothing about it is Komikku-specific.
Available now
One client ships today: a fork of Komikku, a manga reader for Android, wired up to shiori's sync API in place of its usual local-only library. Chosen first because it's what I use.
| Client | Platform | Status | Notes |
|---|---|---|---|
| Komikku (unofficial fork) | Android | Public beta | View the fork — library and read-state sync against a shiori account; expect rough edges while it's in beta. |
Planned & under consideration
TachiyomiSY is the next one actually committed to. The rest are readers whose users would plausibly want shiori sync, listed as ideas rather than promises; nobody's writing code against them yet.
| Client | Platform | Status | Notes |
|---|---|---|---|
| TachiyomiSY | Android | Planned | An SY-flavored Tachiyomi fork; a shiori sync module is next up after Komikku stabilizes. |
| Mihon | Android | Idea | The actively maintained continuation of Tachiyomi; sync would follow the same shape as TachiyomiSY. |
| Paperback | iOS | Idea | The main gap on iOS; nothing shiori-shaped exists there yet, planned or otherwise. |
Build your own
There's no privileged client. Komikku's fork talks to the same four endpoints anyone else would: account creation, pull, push, delete, all authenticated the same way. The cryptography and wire protocol sections of the plan cover key derivation and request signing end to end, and the client behavior section walks through the merge loop a well-behaved client needs. If you'd rather start from the machine-readable contract, the OpenAPI file is the source of truth.