# Yōkai Android manga reader: features, setup, and trade-offs > Yōkai is a free and open source Android manga reader derived from Tachiyomi and Mihon, with local reading, source-based discovery, library organization, tracking, backups, and fork-specific interface changes. It suits Android users who want a configurable reader, but its irregular maintenance schedule and ongoing infrastructure migration deserve attention before adoption. **null2264/yokai** — Free and open source manga reader for Android - Repository: https://github.com/null2264/yokai - Stars: 1,918 · Forks: 136 - Language: Kotlin - License: Apache-2.0 - Published: 2026-10-16 · Updated: 2026-10-16 · Language: en - Canonical page: https://hysenlabs.com/projects/null2264-yokai ## Yōkai's Android reader scope and intended audience Yōkai addresses a specific gap between a plain local image viewer and a full manga library application. It can read downloaded content, browse content obtained through configured sources, organize series into categories, schedule library updates, and preserve reading progress through backups. The target user is an Android reader who wants more control over presentation and storage than a simple comic viewer offers. Multiple viewers, reading directions, light and dark themes, and tablet-oriented page joining all affect how existing manga is presented. The project is a Kotlin Android application built as a fork of Tachiyomi or Mihon, with additional changes attributed to J2K and other projects. That lineage explains the breadth of its feature set, including tracker support for MyAnimeList, AniList, Kitsu, Manga Updates, Shikimori, and Bangumi. It also matters for compatibility. Yōkai says it fixes a backup incompatibility with upstream, which suggests that fork-specific handling has been considered, but it does not document every compatibility boundary between Yōkai and upstream releases. Yōkai is not a manga hosting service. Its disclaimer says the application has no affiliation with content providers and hosts zero content. The app supplies the reader, library, and source framework, while users are responsible for the content they can access and whether their chosen sources are appropriate for their use. That boundary is especially important for anyone evaluating it as an all-in-one manga catalog. ## Library, source, and reader data flow Based on the repository layout and the documented features, Yōkai separates its code into modules such as `app/`, `core/`, `data/`, `domain/`, `presentation/`, `source/`, and `i18n/`. This is a conventional layered Android structure rather than a single-screen project. The documented user flow starts with a library, categories, or source browsing, and continues into manga details and the reader. Chapters can be downloaded for local reading, scheduled for library updates, or associated with tracking services. The reader is configurable through multiple viewers and reading directions. The J2K-derived changes add a combined two-page mode for tablets, an in-reader chapter view, an expanded toolbar that can be reduced, and a floating search bar. Library organization includes a single-list design with expandable categories, a staggered grid, drag-and-drop sorting, and dynamic grouping by tags, tracking status, source, and other criteria. These are interface and metadata-management features, not guarantees about content availability. Local Source support reads `ComicInfo.xml` for chapter title, number, and scanlator. That gives locally stored chapters a defined metadata path, but the README does not explain format requirements beyond those fields. The repository also contains a `source/` module, consistent with source-based browsing, while the project description and feature list do not identify a default catalog or bundled source. Users should therefore distinguish between reading a local folder and discovering titles through remote sources. ## Installing Yōkai and completing a first library setup Yōkai documents two release channels through its download badges: a stable release for Yōkai and a separate nightly channel for `yokai-nightly`. The stable releases page is the documented starting point for a normal installation. The README does not provide an APK filename, Android package name, Gradle command, or Play Store listing, so no installation command can be reproduced from the available documentation. The documented device requirement is Android 8.0 or higher. The README also links to a GitLab mirror and a `git.aap` mirror, but it does not give a procedure for building those mirrors into an installable APK. For a first use, obtain a release artifact from the Yōkai stable releases page, install it on an Android 8.0 or newer device using the device's normal application installation flow, and open the application. The README does not document whether unknown-source installation is enabled by default or how Android's installer will present the file. The first useful task is to add a local source folder or configure a source, then import or browse manga and open a chapter. The exact menu labels and first-run screens are not described in the README, so the tutorial cannot safely invent a sequence such as a specific button path. After opening a series, the reader settings are where a user can choose a viewer and reading direction. Backup support is documented, but the README does not specify the backup file format, restore workflow, or cloud-provider setup. ## Library management features that change daily reading The most substantial fork-specific contribution is library interaction rather than a new reading engine. Yōkai adds a recents page for newly added manga, new chapters, and resuming a series. Dynamic shortcuts can open the latest chapter of the most recently read series from the home screen. These features target repeated sessions and reduce the number of navigation steps for a reader who follows many ongoing series. Dynamic categories can group entries by tags, tracking status, source, and additional criteria documented in the feature list. Drag-and-drop sorting and a staggered library grid provide direct control over presentation. A removal snackbar can delete chapters when a manga is removed and includes an undo action. That behavior is useful when bulk housekeeping goes wrong, although the README does not state how long the undo action remains available or exactly what data is deleted. The scheduling feature is also relevant to active libraries. Users can schedule updates for new chapters, but the README does not explain background execution constraints, Android battery-policy behavior, source retry handling, or partial-update failures. A scheduled update should therefore be treated as an application feature, not a guarantee that every source will refresh continuously. ## Backups, trackers, local files, and platform limits Backups can be created locally and stored in a desired cloud service, allowing reading offline or moving library data. The documented fork-specific fix for upstream backup incompatibility reduces one known class of friction, but the README does not document schema versioning or the exact cloud services supported. A user considering migration should inspect the release notes and test a backup before relying on it for recovery. Tracker integrations cover six services, which is useful for recording progress alongside existing metadata. The application also supports local reading, categories, themes, and scheduled updates. Against this breadth, Yōkai has clear boundaries. It requires Android 8.0 or higher, its source model depends on external providers, and the README says the fork was created for personal use and is focused on migrating to more modern infrastructure. The maintenance note is unusually important. It says updates are sporadic, the developer still has thesis revisions to complete, and pull requests will be looked through only from time to time. Recent release records show v1.10.0, v1.10.1, and v1.10.2 in August and September 2026, while the last push was on 2026-10-13. That is recent repository activity, but it does not erase the stated schedule limitation. Users who require stable long-term release support may find that statement more consequential than the release cadence alone. ## Yōkai versus upstream Mihon and a local-only reader The clearest alternative is upstream Mihon or Tachiyomi, from which much of Yōkai derives. Mihon is the comparison point for the shared library, source, tracker, reader, and backup model. Yōkai adds its own theme, interface redesign, manga details treatment, tablet page joining, recents view, dynamic shortcuts, library sorting, dynamic categories, and batch source migration. The practical difference is therefore fork-specific presentation and workflow changes rather than a wholly separate reading architecture. A local-only image reader is another alternative when downloaded chapters are the only requirement. Such a tool can be simpler because it does not need source discovery, library updates, trackers, or backup synchronization. Yōkai earns its greater complexity when the user wants downloaded files and remote-source series in one library, with metadata, categories, progress tracking, and a configurable reader. There is a trade-off in both comparisons. Upstream alignment may reduce uncertainty for users who already depend on Mihon behavior, while Yōkai's fork may provide changes that upstream has not accepted. Local-only software avoids source reliability questions but gives up Yōkai's library automation and tracker support. The README does not provide a formal feature matrix or compatibility policy, so adoption should be based on the specific fork features and current release notes rather than the project name alone. ## Conclusion Yōkai is a reasonable choice for Android users who specifically want its Mihon-derived reader, local library controls, tracker integrations, and fork-specific interface changes. It is less suitable for users who need a predictable update cadence or assume the fork and upstream project will remain aligned. Before adopting it, check the current release notes, migration status, backup compatibility, and whether the configured content sources provide the titles and chapters you need; the decisive boundary is that Yōkai offers substantial manga-management features but remains a personally motivated fork undergoing infrastructure work. ## FAQ ### What Android version does Yōkai require? The README states that Yōkai requires Android 8.0 or higher. ### Does Yōkai include manga content? No. The disclaimer says the application hosts zero content and has no affiliation with the content providers available through its source framework. ### Can Yōkai read local manga files and use ComicInfo.xml? Yes. Yōkai documents local reading of downloaded content. It also states that Local Source chapters read `ComicInfo.xml` for chapter title, number, and scanlator. ## Sources - [Issues](https://github.com/null2264/yokai/issues) - [License: Apache-2.0](https://github.com/null2264/yokai/blob/master/LICENSE) - [null2264/yokai on GitHub](https://github.com/null2264/yokai) - [README](https://github.com/null2264/yokai/blob/master/README.md) - [Releases](https://github.com/null2264/yokai/releases) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/null2264-yokai