Persistent app destinations
Back to featured workPre-release
Case study
Tebeo
A rights-aware Android reading platform for manga, comics and illustrated stories.

The problem
What the work needed to solve
Build a calm native reader while keeping content rights, age guidance, regional availability and secure media delivery visible in the product architecture.
Implementation
What I built or changed
- Created a guest-first Flutter experience with four persistent destinations and a native reader.
- Separated readable licensed content from metadata-only catalog entries.
- Designed private signed-media delivery, entitlement checks and server-authoritative purchase boundaries.
- Added light and dark UI verification across core screens and reusable components.
Stack
Tools used in context
Evidence
Numbers with their context attached.
Every metric below names the page or test surface, profile, date and source. Limitations follow immediately after.
Limitations
What this evidence does not prove
- The app remains pre-release. Rights review, Android identity and production signing must be completed before store submission.
Next work
What comes after this snapshot
- Confirm the final Android application identity.
- Complete rights, production-environment and signed-release validation.