Finally, a Material 3 media player for Android TV!
Website • Download the latest alpha • Discord Server
- Your own library of local media under
MoviesandTV Showsdirectories in local or extended storage (Download,DCIMandVideosare also supported.) - Clear file names representing movie titles
- Clear folder structure (e.g.
Show/Season/SXXEXX.mp4) for TV Shows
- Material 3 UI
- TV-Optimised Navigation
- Media3 Powered
- Custom themes
- Name matching and asset detecting with TMDb
Aperture is currently in ALPHA. Here is what is being tracked for future incremental updates:
- Press Back for Sidebar Navigation
- Branding updates
- App launch animation
- Complete OpenSubtitles Integration
- Proper audio synchronisation: Forwards and backwards
- Default audio track selection: accessible in settings
- Support for NAS types, Jellyfin and Plex
- Support for 3D TVs
Download the latest release .apk directly from the Releases tab and sideload it onto your Android TV device. We recommend using Downloader by AFTVNews from the Google Play Store.
-
Clone the repository:
git clone https://github.com/XDanfr/Aperture.git
-
Open in Android Studio: Ensure your environment is configured to use JDK 17 or 21 (others are currently untested).
-
Sync & Deploy: Sync Gradle, build the project, and deploy it to your physical Android TV device or an emulator running API 27+.
- Language: Kotlin
- UI Framework: Jetpack Compose for TV
- Media Engine: Media3 / ExoPlayer
- Theming: Material 3
- Website Components: matraic/m3e
Contributions are what make the open-source community such an amazing place! Want a feature or a bugfix? Pull requests are incredibly welcome.
- Issues: Open an issue if you discover a new bug or want to propose a fresh feature request.
- Pull Requests: Fork the project, create your branch, and submit a PR. Please make sure that your code aligns with the existing project style, unless you're going for a more M3E style as Material 3 transitions towards that look.
Q: How are mass local drives parsed?
A: The media architecture leverages standard Android Storage Access Framework processes to securely look up file spaces on attached storage hardware or local nodes.
Q: Was any AI used for this?
A: Gemini was used as a starter to build the baseline template. Some AI features (like autocomplete) were used to speed up development. However, all code is human-reviewed, manually structured, and the trickier bugs are tackled by hand!
Aperture wouldn’t have active development without sponsors. Special thanks to kurohigex for keeping the app running :)
If you like Aperture, please consider supporting its development on GitHub Sponsors 💜







