// OPENBOX DOCS
Roadmap
What is in the current release, what is in progress, and how to shape what comes next.
Roadmap
OpenBox is maintained by one person in the open, so the roadmap is short and honest: what is in the current release, what is being worked on, and where new ideas come from. There are no dates and no promises beyond that.
In the current release
The changelog is the accurate record. The headline pieces in 0.9.0 are the engineering foundation: a verification gate that runs lint, compile, tests, and coverage on every push, a route registry with structured API errors and request ids, gzip-served libraries that load 96% smaller, rolling state snapshots, and the full LaunchBox media catalog (box backs, spines, 3D boxes, logos, fanart, banners, screens, carts, discs, and ads). The desktop UI opens chrome-less by default, and releases ship with SBOM and signing tooling.
In progress
The Unreleased section of the app changelog tracks the next batch. New ideas come from the sources below.
Where ideas come from
- GitHub issues, using the feature request template. The maintainer triages these directly.
- The parity matrix, which tracks LaunchBox workflows and what is intentionally not replicated on Linux.
- The community: the project is open source (AGPL-3.0), and contributions that follow Contributing are welcome.
What will not happen
A few things are ruled out by design, not just postponed: no OpenBox account, no cloud library, no telemetry, no subscription, and no bundling of games, ROMs, or BIOS files. If a request requires one of those, it will not be built.