Mihon: an open source Android manga reader and what it does not ship

What problem Mihon solves, and for whom

Mihon is a reader, not a store. The repository describes it as a "Free and open source manga reader for Android", and the README's disclaimer states that the developers have no affiliation with content providers and that "this application hosts zero content". That single sentence defines both the audience and the boundary. Mihon is for people who already know where their manga comes from and want one Android application to organise it: a library with categories, a configurable reader with multiple viewers and reading directions, scheduled library updates for new chapters, and local backups for offline reading or upload to a cloud service of your choice.

The second half of the feature list is tracking. Mihon supports MangaBaka, MyAnimeList, AniList, Kitsu, MangaUpdates, Shikimori, Bangumi and Hikka. If you already keep a reading list on one of those services, Mihon is the client that keeps it in sync while you read. If you do not use trackers and you do not want a library with categories and update schedules, you are carrying a lot of application for a simple page viewer.

The project inherits its shape from Tachiyomi, which the topics list names explicitly with a tachiyomi-alternative tag. That lineage matters for anyone evaluating it: the mental model, the extension model and the backup format all come from that family of apps, so existing habits transfer.

How the extension model actually works

The repository layout is the clearest statement of the architecture. Alongside app/, data/, domain/ and presentation-core/ sit source-api/, source-local/ and core-metadata/. The naming is not decorative. source-api is the interface layer that content sources implement against, source-local handles content that lives on the device, and core-metadata deals with metadata. The application is split into a data layer, a domain layer and presentation modules, with the source abstraction kept separate from all of them.

The practical consequence is that Mihon has no built-in catalogue. Sources arrive as extensions, which are separate packages implementing the source API, and the README's download section points readers to mihon.app/download for both the stable and beta builds. The README does not document the extension installation flow, so anyone describing it in detail is going beyond what the repository states. What the repository does make clear is the separation: the app is one artifact, the sources are another, and the disclaimer that the developers have no affiliation with content providers follows directly from that design.

There is a second consequence that is easy to miss. Because extensions are separate installable packages, the trust boundary of your reading setup is not the Mihon APK. It is whatever extension repository you point the app at. The README is silent on how that repository is chosen or vetted, which is a gap worth naming rather than glossing over.

Installing Mihon and reaching a working library

Mihon is not distributed through the Play Store according to the README; the download badges link to mihon.app/download, where the stable and beta channels are published. The README states the requirement plainly: Android 8.0 or higher. Check that before anything else, because there is no lower-API fallback.

Get the APK from the official download page rather than a mirror. The README links stable and beta builds to mihon.app/download, and the repository publishes releases such as v0.20.4. Sideloading an APK means your device will ask you to allow installation from that source.

Once the app is open, the first real task is adding a source. The README does not document this flow, so treat the extension list as the thing to configure rather than something the app supplies. After a source is added, the sequence the feature list describes is: browse, add titles to your library, sort them into categories, then let the scheduled update job check for new chapters. Backups are the step people skip. The README lists local backups for offline reading and upload to a cloud service, so configure one before you build a library you would miss.

Where Mihon is the wrong tool

The hardest limitation is the one the disclaimer states outright: the application hosts zero content. If you want an app that opens to a browsable catalogue, Mihon is not that, and no amount of configuration will make it that. You supply the sources.

The second limitation is platform. The README says Android, the repository's primary language is Kotlin, and the build files are Gradle. There is no iOS target in the repository. Readers who split time between an iPhone and an Android tablet will not get parity here.

The third is that the extension layer is undocumented in the repository. The README explains what extensions are for only implicitly, through the source-api module and the disclaimer. It does not explain how to install one, how to add a repository, or what happens when a source stops working. That silence is a real cost: when a source breaks, the fix is not in this repository, and the README gives no rollback or troubleshooting path. The README does point to a FAQ at mihon.app/docs/faq/general, a changelog at mihon.app/changelogs/ and the GitHub issue tracker, which is where that kind of problem is meant to be handled.

Finally, the Android 8.0 floor excludes older hardware. Devices stuck on Android 7 or below cannot run it at all, and the README states no plan to change that.

How Mihon differs from a self-hosted server reader

The obvious alternative category is a self-hosted manga server paired with a browser or a thin client. The difference is where state lives. Mihon is a local-first Android application: your library, categories, reading progress and backups are on the device, and the only network dependency is fetching chapters from whatever source you configured. A server-based reader inverts that. The library lives on a machine you run, and every client is a view onto it.

That inversion changes the failure modes. With Mihon, a lost or wiped phone means restoring from a backup file, which is why the backup feature is listed as a first-class capability. With a server, a lost phone means logging in again. On the other hand, a server requires a machine that is always on, and it gives you one place where all reading data is visible, which Mihon does not.

Mihon's tracker support is the second axis. MangaBaka, MyAnimeList, AniList, Kitsu, MangaUpdates, Shikimori, Bangumi and Hikka are all supported, so if your reading history already lives on one of those, Mihon slots into an existing account rather than asking you to maintain a new one. A self-hosted server may or may not integrate with those services; the choice depends on the server, not on Mihon.

Neither approach is strictly better. If you read on one Android device and want offline access with no infrastructure, Mihon's local model is simpler. If several people read from several devices and you want a single shared library, the local model is the wrong shape.

Maintenance, releases and what the licence allows

The repository is not archived, and the last push was on 2026-09-20. Releases are frequent: v0.20.2 on 2026-08-01, v0.20.3 on 2026-08-04 and v0.20.4 on 2026-08-05. That cadence matters for an Android app because it means the project is still absorbing changes rather than sitting still.

The upgrade path is the part to think about. The README publishes both a stable and a beta channel through mihon.app/download, and the beta builds come from a separate repository, mihonapp/mihon-preview. Running beta means you are tracking a different release stream from stable, and the README does not describe a downgrade path. If you depend on the app daily, stable is the safer channel.

Licensing is Apache-2.0, with the copyright notice naming Javier Tomás from 2015 and the Mihon Open Source Project from 2024. That is a permissive licence: it allows use, modification and redistribution provided the licence terms are met, and it includes a patent grant. It does not give you any rights to the content you read through the app, and the disclaimer makes clear the developers claim no affiliation with content providers. Whether a particular source is lawful in your jurisdiction is a question for you, not for the licence. This is a description of the licence text, not legal advice.

Contributions go through pull requests, with the README asking that major changes be discussed in an issue first, and translations are handled on Weblate.

Editorial conclusion

Adopt Mihon if you read manga on Android, want local library management with trackers and scheduled updates, and accept that sources come from separately installed extensions that the app does not provide. Do not adopt it if you need iOS, or if you expect the app itself to contain a catalogue of titles. Before committing, verify three things: that your device runs Android 8.0 or higher, that the extension repository you intend to use is one you are willing to trust, and that the backup file you create actually restores.

Frequently asked questions

Official sources

1. Issues
2. License: Apache-2.0
3. mihonapp/mihon on GitHub
4. README
5. Releases