Frontends & Launchers: Difference between revisions
From Retroid Handhelds
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
{| class="wikitable" style="text-align: left;" | {| class="wikitable" style="text-align: left;" | ||
|- | |- | ||
Revision as of 04:48, 15 September 2020
| Frontend/Launcher | Notes |
|---|---|
| Pegasus | Free. Fast. Immensely and overwhelmingly theme-able (can be skinned to look and behave exactly like any other frontend, given the time and effort). Open-source and actively in development. An absolute pain to configure, and lacks built-in scraping support. Actively being developed. |
| Dig | Free. Slow. Theme-able. Super easy to configure, and does have built-in scraping. Development has been abandoned and the app is closed-source. Consequently, this will never be able to launch certain emulators like Flycast and the GBA build of Retroarch included on RP2. |
| RESET | $5. Fast. Not theme-able. Slick and easier than both Pegasus and Dig to configure. Built-in scraping. Actively being developed. |
| RetroX | $12/year. Fast. Theme-able. The easiest out of all of these to configure, by far. Uses built-in emulator cores, giving you handy universal shortcuts in all of your games. Some systems might be faster in RetroX than on the RP2s pre-installed emulators, while some might be slower. Emulation is less customizable than with other emulators. The subscription covers cloud saves, letting you stay synced across any device you use RetroX on, but with the notable downside that internet access is required to open your games. Actively being developed. |
Credit to @ryan86me for the write ups for these
