-
Notifications
You must be signed in to change notification settings - Fork 6
Roadmap
Levyra is under active development.
This roadmap describes the main engineering directions of the project rather than promising features for specific release dates.
Priorities can change when playback reliability, privacy, user data or platform compatibility require immediate attention.
Levyra development is focused around several long-term areas.
flowchart TD
LEVYRA[Levyra]
LEVYRA --> PLAYBACK[Playback]
LEVYRA --> OFFLINE[Offline & Data]
LEVYRA --> UI[Performance & UI]
LEVYRA --> RESILIENCE[Media Resilience]
LEVYRA --> WINDOWS[Windows]
LEVYRA --> RELEASES[Distribution]
Playback remains Levyra's highest product priority.
Development in this area focuses on:
- Faster playback startup
- Reliable stream resolution
- Better fallback behavior
- Stable queue management
- Media3 / ExoPlayer reliability
- MediaSession synchronization
- Background playback
- Android Auto
- Audio and video mode stability
- Gapless playback
- Crossfade and AutoMix behavior
- Reduced playback latency
Visual features must never prevent or delay audible playback.
Levyra is designed around local ownership and recoverability.
Ongoing work includes:
- Reliable portable downloads
- Better offline playback
- Playlist persistence
- Favorites
- Listening history
- Queue restoration
- Preference persistence
- Backup and restore
- Smart local playlists
- Safe database migrations
- Storage cleanup and recovery
User data should never be silently discarded simply to simplify an implementation.
Performance is treated as part of the architecture rather than an optional optimization.
Areas of focus include:
- Faster startup
- Reduced main-thread work
- Non-blocking preference access
- Efficient state observation
- Reduced unnecessary recomposition
- Artwork loading and caching
- Memory usage
- Smooth scrolling
- Faster navigation
- Efficient background work
Levyra should remain responsive even on less powerful devices.
The interface will continue evolving while preserving the identity of Levyra.
Development includes:
- Better responsive layouts
- Improved visual consistency
- Accessibility
- Localization
- RTL support
- Reduced-motion behavior
- Better large-screen behavior
- More predictable UI state
- Improved discovery experiences
Optional animation and artwork should enhance the experience without becoming dependencies for core functionality.
Music discovery remains an important part of Levyra.
Areas being developed and refined include:
- Your Orbit
- Quick Picks
- Levyra Collections
- Personalized radio
- Similar songs
- Older favorites
- Artist discovery
- Better metadata resolution
- Improved recommendations
- Smarter library discovery
Discovery should remain useful without requiring a Levyra account or remote tracking profile.
Levyra continues to improve the experience around the music itself.
This includes:
- Synchronized lyrics
- Better lyric matching
- Lyric sharing
- Artwork presentation
- Canvas
- Motion artwork
- Full-screen visual experiences
- Levyra Ambient
These systems remain secondary to playback reliability.
Remote music services change over time.
Levyra continuously improves its ability to handle these changes through:
- Better stream resolution
- Controlled retries
- Multiple fallback paths
- Safer caching
- Provider failure isolation
- Network diagnostics
- Validation of remote media
A failure from one remote provider should not corrupt local data or destabilize the rest of the application.
The Windows version of Levyra is developed as its own native runtime.
Future work focuses on:
- Playback reliability
- libvlc lifecycle and resource management
- Downloads
- Mini player
- Media keys
- Deep links
- Update reliability
- Installer quality
- Portable distributions
- Desktop-specific performance
Android and Windows releases remain independent.
Privacy remains a permanent engineering requirement.
Levyra intends to preserve:
- No mandatory Levyra account
- No advertising profile
- No unnecessary analytics
- No hidden tracking
- Local listening history
- Local listening statistics
- User-controlled integrations
- Portable user data
New features should not weaken these principles.
Levyra's distribution system will continue improving across supported platforms.
Focus areas include:
- GitHub Releases
- Android APK releases
- F-Droid-compatible builds
- Windows packages
- Reproducible builds
- Artifact verification
- Release checks
- Safer update flows
Release automation must remain separate from normal development work.
Levyra follows a strict development workflow:
Plan
↓
Implement
↓
Test
↓
Review
↓
CI
↓
Manual validation
↓
Merge
↓
Release
These stages are intentionally separate.
A change being implemented does not automatically mean it is ready to be released.
When development priorities conflict, Levyra generally follows this order:
- Safety, privacy and user data
- Playback reliability
- Lifecycle and resource correctness
- Offline reliability
- Performance and accessibility
- Release integrity
- Optional visual enhancements
This means a playback or data-integrity problem will normally take priority over a new visual feature.
The roadmap is not a closed list.
Ideas from users are welcome and can influence future development.
Before suggesting a feature, check whether a similar request already exists:
The detailed engineering roadmap lives inside the repository:
Active engineering tasks are tracked separately:
The repository documents are the source of truth when they differ from this high-level Wiki overview.
No fixed release dates are promised by this roadmap.
Features and priorities may change as Levyra evolves.
Levyra Wiki
Home · Getting Started · Features · FAQ & Troubleshooting
Development · Architecture · Roadmap · Privacy & Data
GitHub Repository · Latest Release · Issues · Website
Levyra is an open-source music application for Android and Windows.