DEV Community

Crane Zhou
Crane Zhou

Posted on Edited on

Where your Android comic library actually lives: S3, R2, WebDAV or Drive

Most Android comic readers treat your library as something the app owns. You import a file, the app decides where it goes, and when you change phones you find out what that decision cost.

I have been building Easemic, an open-source (Apache-2.0) comic reader for Android, so this problem is one I keep running into.

The four storage shapes people actually have

S3-compatible buckets (AWS S3, MinIO, Backblaze B2). Cheapest per GB, one-time setup, and everything else can read it. If you already pay for object storage for anything else, this is the obvious default.

Cloudflare R2. No egress fees, which matters more for comics than for most media because you re-read pages constantly. A 2 GB library read twice a month is a few pennies.

WebDAV. Synology, Nextcloud, and most NAS boxes speak it. Slowest of the four, but it is the one that works when you would rather not hand a bucket key to anyone.

Google Drive / OneDrive. Zero setup, already paid for, and the only option many people will ever use. The tradeoff is that both throttle large media requests, so page turns can stall.

Why this matters more than it sounds

A comic library is not small. A long-running series with 200 chapters at 30 MB each is 6 GB. Multiply by a shelf of ten series and you are past any phone's comfort zone. Storing it on-device means choosing between your library and your photos.

Streaming from cloud storage fixes that, but only if the reader streams pages, not archives. Downloading a 40 MB CBZ to show page 3 is the mistake most readers make.

Encryption is the part nobody mentions

If your library goes to a cloud bucket, you are uploading content someone else can read. Easemic encrypts on-device before upload, so the bucket holds ciphertext and the key stays in the phone's keystore. That is not a feature you can add later - it decides the file format.

The migration case

The thing that made me start this project: a source goes down and takes your collection with it. If your library lives in your own bucket, a dead source is an inconvenience. If it lives in the source's app, it is a loss.


Easemic is free, has no ads and no account: easemic.com | source on GitHub

Top comments (0)