Browse and play your self-hosted retro game library across Xbox, Windows, and Android with gamepad-first navigation, RomM v5 API pairing, and direct emulator handoff.
Xbox · Android · Windows & Web · Connect · Known limits · Report a problem
| Platform | Type | Best Fit | Description & Install |
|---|---|---|---|
| Xbox | Native UWP (WebView2) + Browser | Xbox Series X|S & Xbox One | Native controller input, big-screen TV navigation, and EmulatorJS cores. Available on Microsoft Store (App ID: 9MXC51W17LH4) or via Dev Mode sideload. |
| Android | Native Handheld Client (WebView) | Retro handhelds (Ayn Odin, Retroid Pocket, Anbernic), Android TV, tablets, phones | Gamepad-native fullscreen launcher with analog stick support, cleartext LAN discovery, and intent dispatch to RetroArch, Dolphin, PPSSPP, and NetherSX2. Build via android/. |
| Windows & Web | Desktop Shell & Static Web App | PC, Mac, Steam Deck, Browser | Static HTML/CSS/JS frontend that can run standalone, in Electron via Cartridge for Windows, or reverse-proxied with your server. |
- A RomM or ROMarr server with your own library and actual ROM files.
- A gamepad/controller and a supported device (Xbox console, Android handheld/phone, or PC).
- A supported player or core for the selected game. A streaming server is optional and adds remote play for heavy systems.
Cartridge is a dedicated player client. RomM or ROMarr supplies library data, covers, files and save-state services. ROMarr automates game acquisition, DAT checksum verification, and library imports.
| Path | What it runs | Setup |
|---|---|---|
| Xbox Edge | Static web client in the Xbox's Chromium browser | Host the files with the same origin as RomM, or configure the required proxy/headers. |
| Native Xbox app | UWP shell with WebView2, native gamepad input and a network bridge | Use an approved Store build (Store #9MXC51W17LH4), or build/test the MSIX through a supported developer installation. |
The native shell is the package project under shell/.
Cartridge for Android is packaged as a lightweight, controller-first native Android application under android/:
- Gamepad-native input: Automatic mapping for hardware controllers, D-pads, bumpers, and analog thumbsticks on Ayn Odin, Retroid Pocket, Anbernic, and Android TV remotes.
- Immersive mode: True edge-to-edge fullscreen sticky layout with system bars hidden during gameplay.
- External emulator handoff: Option to dispatch local ROMs directly to installed emulators (RetroArch, Dolphin, PPSSPP, NetherSX2, DuckStation) via Android's
ACTION_VIEWintent.
cd android
./gradlew assembleRelease
# Or on Windows:
.\gradlew.bat assembleRelease- Start Cartridge and enter your RomM or ROMarr server address, including the port if needed (e.g.
http://192.168.1.100:6868). - Let the connection check finish. Its status and failure reason are shown on screen.
- Pair using RomM → Settings → Client API Tokens → Add → Pair, if your server provides that flow, or use your username and password.
- Choose a platform and a game. Start with a small file and verify playback and saving before relying on a long session.
An installed native shell can route plain-HTTP LAN requests through its native bridge. The browser client still follows browser origin and certificate rules: a page served over HTTPS cannot simply fetch every HTTP server. Network setup and why browsing can work while playback fails.
Self-signed certificate support is an explicit opt-in for your selected server in the native app. Keep normal certificate validation enabled for other hosts. Connection and transport logic is tested in CI; successful playback with your server and console still needs a real test.
- D-pad: move; A: choose/play; B: back through menus.
- LB/RB: switch platform.
- During a game, B belongs to the game. Hold Menu + View to leave playback.
- X on the setup page: diagnostics, including build and connection information.
A supported EmulatorJS system runs locally in the browser/WebView2. A configured streaming server can provide remote playback for other systems. Available routes depend on the platform, file format, core, firmware and server configuration; library visibility is not a guarantee that every game can launch.
Save-state upload is implemented through RomM/ROMarr. Validate a save and reload on your own setup before depending on it. Controller timing, memory limits and streaming latency are hardware/network dependent.
The web client is static HTML/CSS/JavaScript; it needs no Node build step. Serve it from the same origin as your RomM or use a reverse proxy. A typical layout is:
/ -> Cartridge web files
/romm/ -> RomM, with the prefix stripped
/api/ -> optional streaming server, including WebSocket signalling
/emu/ -> your EmulatorJS data, if using this layout
Adapt this to your RomM deployment rather than assuming those paths already exist. See network deployment and the separate Cartridge streaming server.
The Store product remains 9MXC51W17LH4. The public name is Cartridge for Xbox. The package identity MOVEWEIGHT.RomMforXbox and registered publisher are retained so this remains an update to the same product.
Store approval/publication is separate from a successful GitHub build. An unsigned CI artifact is not a retail-console installer. Dev Mode testing requires the appropriate package trust/signing and device setup.
The Windows CI workflow runs on relevant pull requests and main-branch changes. It:
- Validates the package identity and visible product name.
- Tests EmulatorJS core keys, native URL/error logic, controller/connection logic and the real JavaScript transport bridge.
- Restores and builds the actual x64 UWP/WebView2 project with .NET Native.
- Unpacks the output and checks its identity, Xbox target family and required web content.
- Uploads the package as a workflow artifact.
Run the portable checks locally with Node.js and Python 3:
python3 tests/validate_manifest.py
python3 android/tests/validate_android.py
node tests/validate_cores.js
node shell/tests/bridge-logic.test.mjs
node shell/tests/native-fetch.test.mjsBuilding the native app itself requires Windows, Visual Studio/MSBuild with UWP tools, the Windows SDK and NuGet restore. The canonical project is shell/RommForXbox.Shell/RommForXbox.Shell.csproj; CI records the complete build command and toolchain. Do not infer that a Linux syntax check built the MSIX.
CI checks real source logic and the actual Windows package build. It cannot validate Xbox hardware input, WebView2 behavior on a particular console, each emulator core, all RomM versions, or save-state persistence across every device. This rebrand does not add a new hardware proof claim.
The package history and hardware test checklist explain the older hosted package and the current native shell. For a bug report, include the build/version, platform (Xbox/Android/Windows), RomM version, server address scheme (HTTP/HTTPS), failing action and diagnostics message. Remove tokens and passwords.
- Cartridge for Windows: optional desktop companion.
- ROMarr: acquisition and library automation.
- ROM Hub: source and metadata plugins.
Cartridge is an independent community project by Move Weight and is not endorsed by RomM or Microsoft.