Mangayomi review: a Flutter manga, novel and anime reader for Android, iOS, desktop and Linux

What Mangayomi actually is, and the reader it replaces

Mangayomi is a Flutter client, not a content service. The README describes it as an open-source Flutter app for reading manga, novels, and watching animes across multiple platforms, and the repository topics list android, anime, anime-streaming, dart, flutter, ios, isar, linux, macos, manga, manga-reader, video and windows. The disclaimer is explicit: Mangayomi is not hosting any kind of content and the developer(s) of this application does not have any affiliation with the content providers. So the app is the shell. What you can read depends on the sources you add.

That distinction matters more than the feature list. The README lists reading manga, webtoons, comics, novels, animes and movies, a configurable reader with multiple viewers and reading directions, categories for the library, light and dark themes, local reading, and backups to local storage or a cloud service. None of those features produce a single page on their own. They are the furniture around an extension system.

The intended user is someone who already reads across several sites and wants one library, one reading-progress store and one backup file instead of a browser full of tabs. The tracker integrations (MyAnimeList, AniList, SIMKL, trakt and Kitsu) point at the same person: someone who already keeps a list somewhere else and does not want to maintain it twice.

Extensions are the whole product, and the repository is separate

The README points contributors to CONTRIBUTING-DART.md for creating sources in Dart and CONTRIBUTING-JS.md for creating sources in JavaScript, both hosted in the kodjodevf/mangayomi-extensions repository. Two languages means two runtimes inside one app: a Dart path and a JavaScript path. The repository topics include dart-eval, which is consistent with running JavaScript source definitions from Dart rather than compiling each one into the binary.

The practical consequence is that the app and its sources version independently. A new chapter layout on a site is an extension change, not an app release. You can update an extension without waiting for a new APK, and you can also be left with a broken source on a perfectly current app build. The README does not describe a health check, a source status indicator, or any automatic fallback when a source stops returning results, so recovery means finding an updated extension and reinstalling it.

That is the trade-off of the design. A bundled client is stable and limited. An extension client is broad and fragile. Mangayomi chose broad, and the repository layout (lib/, rust/, go/, proto/, rust_builder/) shows how much machinery sits underneath that choice.

Installing Mangayomi: releases first, then a first source

The README says to get the app from the releases page, and the three most recent releases are v0.9.5, v0.9.6 and v0.9.7. There is no package registry install and no official website; the README states that this GitHub repository and the official Discord server are the only official sources, and warns against downloading releases anywhere else. Pick the asset that matches your platform: Android, Windows, Linux, macOS or iOS.

For iOS the README supplies sideloading sources for AltStore, Feather and SideStore, plus a direct URL source. It also carries a note that only future releases above 0.5.2 will be signed and therefore have AltStore and SideStore compatibility, so an unsigned build is a real possibility depending on what you grab.

# iOS sideload source URL referenced by the README
https://raw.githubusercontent.com/kodjodevf/mangayomi/refs/heads/main/repo/source.json

If you are building from source rather than downloading a release, the README requires the Flutter SDK and the Rust toolchain, because the project uses flutter_rust_bridge. Check both before you start.

rustc --version
flutter doctor

The bridge codegen tool is installed separately, then run once to generate the bindings, after which the project builds like any other Flutter app.

cargo install 'flutter_rust_bridge_codegen'
flutter_rust_bridge_codegen generate
flutter run

Once the app is open, the work that matters is adding a source. The README does not document the exact in-app steps, so the honest description is: install extensions from the mangayomi-extensions repository or the app's extension interface, then open a source and confirm that a title loads and a chapter opens. Test that before importing a backup or organizing categories, because a dead source will make the library look broken when it is not.

Where the extension model breaks down

The failure mode is predictable and it is not the app's fault. Sources depend on site structure. When a site changes its markup, its API or its anti-bot behaviour, the extension returns errors, empty chapter lists or partial pages. The README documents no retry policy, no per-source diagnostics and no way to report a broken source from inside the app. Your options are the mangayomi-extensions repository and the Discord server.

The second limitation is platform friction rather than code. On iOS, the README's own note about signing means sideloading is the supported route, and sideloaded builds expire and need reinstalling. Anyone expecting a store install on iPhone is looking at the wrong tool.

The third is scope creep in the feature list. The README advertises animes and movies alongside manga and novels. A reader with a configurable viewer and reading directions is a mature shape for text and images. Video playback across arbitrary sources, with trackers attached, is a different reliability problem, and the README offers no statement about codec support, buffering or quality selection. Treat the video side as a bonus, not the reason to adopt.

Alternatives, and the difference that matters

The closest comparison is Tachiyomi and its forks. Tachiyomi is an Android-only manga reader built around extensions in Kotlin; Mangayomi is a Flutter application that also targets iOS, macOS, Linux and Windows, and it accepts sources written in Dart or JavaScript rather than Kotlin. If your devices are all Android, the extension ecosystem you already know is on the other side of that fence. If you read on a laptop and a phone, Mangayomi's cross-platform reach is the reason to pick it, and the smaller extension catalogue is the price.

A second option is a dedicated anime client such as Aniyomi, which follows the same extension philosophy but centres on video. Mangayomi's own README claims anime, movies, manga and novels in one app, which sounds like an advantage until you notice that each medium has its own failure surface. A tool that does one medium well will usually be more predictable than one that does four.

The third option is a local library: download your files, read them with a plain viewer, and skip sources entirely. Mangayomi supports local reading, so this is not an either-or. The difference is that local content never breaks, while sourced content breaks on someone else's schedule.

Licence, build cost and what upgrades really involve

Mangayomi is Apache-2.0, Copyright 2023 Moustapha Kodjo Amadou. The licence text in the README is the standard Apache 2.0 grant: use, reproduction and distribution are permitted under its conditions, and the software is provided on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND. For most users this is a non-issue. If you fork it, redistribute it or ship a modified build, read the notice and attribution requirements in the full licence rather than the README summary, and treat extension licensing separately, since the extensions live in a different repository.

The upgrade cost splits in two. App upgrades are release downloads; the most recent releases are v0.9.5, v0.9.6 and v0.9.7, published within days of each other, so the cadence is fast enough that you should not expect long-term support on any single version. Extension upgrades are independent and are where most of your maintenance time will go.

Building from source is the expensive path. You need Flutter, the Rust toolchain and flutter_rust_bridge_codegen, and you must rerun the codegen when the bridge changes. The README does not document rollback, a version pinning policy, or a migration path for the Isar database that the repository topics indicate is in use. Back up before you upgrade, and keep the previous release asset until the new one has opened your library successfully.

Editorial conclusion

Adopt Mangayomi if you want one Apache-2.0 client on desktop and mobile, you are comfortable installing sources from the mangayomi-extensions repository, and you accept that a source can break the moment a site changes. Do not adopt it if you need a store install on iOS or a client that ships with content already wired in. Before anything else, confirm which release asset matches your machine, check whether the iOS build you intend to use is signed, and test one extension end to end before you build a library around it.

Frequently asked questions

Official sources

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