Choose MAME or RetroArch for a legal Android arcade library
Choose a maintained standalone MAME port when exact upstream revision, machine audits, and MAME-native diagnostics are the priority. Choose RetroArch with a documented arcade core when unified controllers, overlays, and multi-system navigation matter, while recording both frontend and core versions. In either case, choose software first, match each lawful set to that version, and keep rights evidence separate from compatibility.
Do this in order
- 01
Inventory Android version, CPU, storage model, controllers, accessibility needs, and lawful content rights receipts.
- 02
Require any candidate package to identify its official source, software license, upstream MAME/core revision, update path, and storage behavior.
- 03
Choose standalone MAME for native audit and machine controls, or RetroArch for frontend integration, only after documenting the trade-off.
- 04
Match one authorized game's set generation to the selected revision and verify parents, BIOS, devices, and CHDs without using bundles.
- 05
Test cold launch, controls, touch/keyboard escape, audio, suspend, saves, relaunch, and a redacted diagnostic export.
- 06
Record the decision and keep the other option uninstalled unless a distinct need justifies its additional configuration and data copies.
Decision and diagnostic table
| Decision factor | Standalone MAME | RetroArch arcade core |
|---|---|---|
| Version receipt | Port plus upstream MAME | Frontend plus exact core |
| Audit workflow | MAME-native when exposed | Core/frontend tools vary |
| Controls | MAME machine/UI controls | RetroPad, remaps, overlays |
| Legal content | Separate rights receipt required | Same separate rights receipt required |
Convenience does not erase versions
A frontend can simplify navigation while adding a core version and configuration layer that must be recorded.
Legal and compatible are independent
Permission answers whether you may use the content. A matching audit answers whether the selected build understands it.
Select with one test case
A small authorized test exposes storage, controller, save, and diagnostic boundaries before a library migration.
Use only game, firmware, artwork, and configuration files you created, dumped lawfully, or received under permission covering your use. Emulator compatibility never grants content rights; do not use unauthorized ROM, BIOS, CHD, artwork, or music mirrors.