Bring your hardware.
Help port the shared software to a board you own. Document graphics, audio, controllers, game launching and recovery as separate milestones.
Propose a port ↗
Try the demo ↗
Help make a console experience that people can understand, repair and improve. Code, testing, documentation and hardware validation all matter.
Help port the shared software to a board you own. Document graphics, audio, controllers, game launching and recovery as separate milestones.
Propose a port ↗Reproduce controller handoff, transfer interruption and session-recovery bugs. Include the board, component commit, exact steps and relevant logs.
Browse session issues ↗Build a focused menu, library or store improvement. Describe the player journey and discuss substantial changes before implementation.
Discuss a menu feature ↗Improve setup instructions, record compatibility results, clarify controller guides or help make the experience accessible.
Improve the library & docs ↗Rust session supervision, launch contracts, focus/input coordination and integration helpers.
Repository & setup ↗ Issues ↗Quickshell / QML system UI, settings, transfer, artwork and notifications.
Repository & setup ↗ Issues ↗Qt Quick library, home, favorites, search, game details and preferences.
Repository & setup ↗ Issues ↗Qt Quick / C++ curated native-game storefront and background transactions.
Repository & setup ↗ Issues ↗Dragon Q6A is the reference development platform. A Raspberry Pi 5 image is planned. Other boards begin as community ports.
Desktop UI work can often start with component previews. A complete port also needs real-device graphics, input, audio, session and recovery testing.
Read each repository’s license. Upstream dependencies, fonts and branding retain their own terms.
Hardware & image status