Reader goals
- Prefer downloaded pages before remote image loading.
- Keep page index, chapter progress, and resume state understandable.
- Expose real retry/error surfaces when a page is missing or corrupted.
Feature guide
MIYO is built around reading flow, not just source browsing.
The app focuses on reliable local reading, background downloads, source/plugin separation, and native helpers where Kotlin-only paths become expensive.
Reader
Downloaded chapters should open like local files.
Offline-first behavior is the baseline. When a chapter is already downloaded, the reader should prefer local pages and avoid wasting network data.
Background downloads with better state.
MIYO puts more attention on slow providers, notification controls, cancellation, local validation, and stuck-state visibility.
- Progress surfaces for current work.
- Storage checks before declaring a chapter complete.
- Safer cancellation and stuck-download reporting paths.
Parser logic stays away from the core reader.
Compatible source plugins use the Kotatsu-style parser boundary. Repositories that contain Mihon/Tachiyomi APKs are detected and blocked until a real compatibility runtime exists.
- Clear error paths for unsupported plugin formats.
- Captcha/browser handoff remains source-aware.
Native work
C++ is used as a helper layer, not as a second app.
Native code belongs on measurable hot paths: image probing, archive work, and refinement helpers where JNI overhead is worth paying.
- Probedetect dimensions and format before expensive decoding
- Archivesupport zip-oriented chapter work and CRC paths
- Refineaccelerate local enhancement when a model is installed
- Guardfallback to safe Kotlin paths when native work cannot run
Interface evidence
Real app states, not fake product chrome.
The screenshots show the actual UI direction: black canvas, purple navigation, dense manga grids, and source/action sheets.
