You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This research document outlines potential integration of RomM with various gaming frontends, launchers, operating systems, mobile apps, handhelds, and custom firmware. It details the implementation status of plugins, sync services, and server-side push-pull mechanisms across different platforms, with a focus on enabling seamless ROM management and save synchronization.
Caution
This document is for research and discussion purposes only! It is not a development roadmap, and inclusion does not guarantee implementation.
Breakdown
Plugins for Playnite, LaunchBox and Lutris
Cross-platform (Windows, macOS and Linux) sync service for ES-DE, Retroarch, OpenEMU, RetroBat, Ludo, Bizhawk, Lakka, RetroPie, Batocera and Bazite
React Native app for Android which connects to other emulator apps
Server-side push-pull for Provenance on iOS
Client apps for muOS, OnionUI and CrossMix
On-device sync service for ArcOS, GarlicOS, Knulli and ROCKNIXX
Server-side push-pull for all targeted CFWs (AmberELEC, ArkOS, CrossMix, GarlicOS, Knulli, MinUI, muOS, OnionUI and ROCKNIX)
Legend
⚪ Completed
🟢 Targeted
🟠 Concerns or unknowns
🔴 Unsupported
⚫ Dead project
🔵 Client app/plugin
🟣 On-device sync service
🟤 Server-side push-pull
Frontends and Launchers
For launchers with no plugin systems, it might be possible to build sync software that downloads games into the correct folders for each app, and syncs the saves back to the server on change (like Syncthing).
All of these systems are Linux based, so we could build a simple CLI tool that fetches games, and a service that syncs saves (like Syncthing). Would need a GUI app when running on handhelds, or systems with a desktop environment.
For Android devices, generally speaking, we'd need to build a React Native app that not only connects to RomM and displays the mobile interface, but is also aware of the other emulators installed on the device, like Dolphin, PPSSPP or DraStic. The app should be able to download and move games to a location usable by the emulators (easier), and sync saves back up to the server (harder).
Options are much more limited for iOS devices, and we would likely need to integrate directly with any apps.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
This research document outlines potential integration of RomM with various gaming frontends, launchers, operating systems, mobile apps, handhelds, and custom firmware. It details the implementation status of plugins, sync services, and server-side push-pull mechanisms across different platforms, with a focus on enabling seamless ROM management and save synchronization.
Caution
This document is for research and discussion purposes only! It is not a development roadmap, and inclusion does not guarantee implementation.
Breakdown
Legend
⚪ Completed
🟢 Targeted
🟠 Concerns or unknowns
🔴 Unsupported
⚫ Dead project
🔵 Client app/plugin
🟣 On-device sync service
🟤 Server-side push-pull
Frontends and Launchers
For launchers with no plugin systems, it might be possible to build sync software that downloads games into the correct folders for each app, and syncs the saves back to the server on change (like Syncthing).
Operating Systems
All of these systems are Linux based, so we could build a simple CLI tool that fetches games, and a service that syncs saves (like Syncthing). Would need a GUI app when running on handhelds, or systems with a desktop environment.
Mobile
For Android devices, generally speaking, we'd need to build a React Native app that not only connects to RomM and displays the mobile interface, but is also aware of the other emulators installed on the device, like Dolphin, PPSSPP or DraStic. The app should be able to download and move games to a location usable by the emulators (easier), and sync saves back up to the server (harder).
Options are much more limited for iOS devices, and we would likely need to integrate directly with any apps.
Custom Firmwares
Beta Was this translation helpful? Give feedback.
All reactions