Rommio provides native Android and iOS companions for RomM: a fast, touch-friendly client for browsing your library, downloading games, and launching supported titles with an embedded libretro player.
The Android development build synchronizes game saves and resume/manual snapshots independently for qualified, account-bound FCEUmm NROM/Namco games on RomM 5.2.0. Other core/server combinations retain local progress and explicit compatibility limits. Existing saves and pending changes are preserved. See the progress protocol and remediation status for behavior and validation.
Android and iOS now activate independent game-save and resume-snapshot storage/sync for owned, verified single-file NES content using the pinned FCEUmm NROM/Namco layouts and RomM 5.2.0. Actual simulator/emulator exchange and offline iOS process restart are verified. Broader cores and physical lifecycle qualification remain separate gates. See iOS progress behavior and evidence and iOS build instructions.
Download the latest APK from GitHub Releases.
Rommio requires your own RomM server. It does not provide ROMs, BIOS files, or emulator cores.
Two themes, each in light and dark: Aurora (glass over light taken from your games) and Riso (two-ink print on paper). Pick one in Settings › Appearance.
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
- Native Android and iOS apps with platform navigation: Play, Library, Search, Stats and Settings
- Two designed themes, Aurora and Riso, each in light and dark
- Offline-first browsing once a profile has been hydrated online at least once
- Download queue management with progress, retry, cancel, and local install tracking
- Embedded libretro play for supported platform families
- Touch controls on mobile-friendly platforms and controller-first support for heavier systems
- Local storage for installs, saves, save states, profile cache data, and player preferences
- An Android phone or tablet running Android 8.0+ (
minSdk 26) - A working RomM server
- A first online session so Rommio can cache your library for offline use
Rommio is designed to complement RomM, not replace it. Server administration, library scanning, metadata enrichment, and multi-user management still live in RomM itself.
Rommio uses three support tiers in the app:
Touch: embedded runtime plus first-class touch controlsController: embedded runtime exists, but the platform is still controller-firstBrowse only: browseable in RomM, but not enabled for embedded playback in Rommio
The current runtime matrix, recommended cores, and validation status live in docs/core-matrix.md.
- Browse Play, Library (platforms and collections), Search, Stats, and game detail from local cache
- See recent saves across games with preview frames, and play time from sessions recorded on this device
- Launch installed titles without a live RomM lookup when the metadata has already been hydrated
- Keep ROM downloads queued while offline and resume automatically when the network returns
- Sync game saves and resume/manual snapshots independently on the qualified route, with verified readback, durable retries and preserved conflicting branches
- Queue core download work for reconnect
- Cache thumbnails for platforms, collections, and games locally so the app still feels complete offline
- Tune the player with touch layout options, OLED black mode, and optional console-inspired control colors; controls follow the chosen theme
Rommio is licensed under GPL-3.0-or-later.
This app is built to work with RomM, which is licensed under the GNU Affero General Public License v3.0. Rommio is a separate Android client and is not a ROM source.
Rommio uses LibretroDroid for embedded libretro playback. LibretroDroid is licensed under the GNU General Public License v3.0. Rommio bundles FCEUmm from pinned source for offline NES/Famicom core installation and uses the broader libretro ecosystem for other downloadable cores. Each core retains its own license and attribution. BIOS files are supplied by the user and are not bundled.
For direct shipped dependency notices, see THIRD_PARTY_NOTICES.md.
If you want to build, test, or release the app yourself, start with docs/development.md.
Other useful references:
- Save, sync, and session architecture — target behavior shared by Android and iOS
- Android player ownership — qualified save/resume ownership and current limits
- Backup bundle format — format-3 save metadata and artifact transfer
- App remediation plan — ordered fixes, dependencies, and validation for the structural audit
- UI studio — five full-app design directions and a mockup workbench for iterating on every screen
- docs/core-matrix.md
- docs/validation-matrix.md
- app/
- scripts/android/





