Feature Area

UI/UX Improvements, Performance, Developer Experience

Problem Description

Project-Myriad requires a structured, actionable roadmap to achieve a clean, performant, and modern Android manga reader experience. Without a systematic approach to codebase optimization and UI/UX polish, the app risks technical debt, slower development cycles, and a suboptimal user experience.

Proposed Solution

Implement the following directives to 100% completion:

Phase 1: Foundational Improvements (Build & Architecture)

1. Centralize dependency management using a Gradle Version Catalog (libs.versions.toml).
2. Modularize the codebase into feature-specific modules (e.g., :core:ui, :core:model, :feature:library, :feature:reader, :feature:downloads, :feature:browse) for better scalability and build speed.

Phase 2: Core Performance Enhancements
3. Integrate Baseline Profiles for AOT compilation to improve startup time and runtime performance.
4. Optimize image loading (Coil) and Room database queries for responsiveness and stability. Apply granular state updates to reduce unnecessary recompositions in Compose screens.

Phase 3: Cosmetic & UI/UX Polish
5. Embrace Material You and dynamic theming for a personalized Android experience.
6. Add polished animations (shared element transitions, content fade-in) and subtle haptic feedback for major interactions.
7. Ensure adaptive layouts for tablets and foldables (responsive grid, two-page reader in landscape).

All work must strictly follow the project’s architectural and coding conventions as stated in the custom instructions. Each directive should be marked complete and verified before closure of this issue.

Alternatives Considered

Alternatives include incremental or piecemeal optimizations, but these risk creating inconsistencies and technical debt. Only a full, holistic implementation will guarantee the desired outcome.

Additional Context

Refer to the custom instructions and organizational guidelines for exact implementation details. Strict adherence to MVVM, Clean Architecture, Kotlin only, Jetpack Compose, Material 3, Coroutines/Flow, Hilt, Retrofit, Room, and Coil is required. See linked org instructions: https://docs.github.com/en/copilot/customizing-copilot/adding-organization-custom-instructions-for-github-copilot

Implementation

• I'm willing to implement this feature
• I need help with the implementation
• I just want to suggest the idea

Code of Conduct

• I agree to follow this project's Code of Conduct