Manic EMU puts many retro cores behind one iOS app

One app, and a policy about what you run in it

Manic EMU is described as an all-in-one retro game emulator for iOS, and the README expands that to console, arcade, computer and mobile Java systems brought into one app, with a clean interface and gameplay focused controls.

The emulator model is multiple cores, including Libretro based frameworks and dedicated cores. So the scope is not one machine emulated well, it is many machines emulated adequately under a single interface, which is the trade every multi-system emulator makes.

What the project is explicit about is content. Manic EMU does not include ROMs, ISOs, BIOS files or copyrighted game data, and the README asks users to use legally owned backups, homebrew and public domain software only, linking an anti-piracy policy document in the repository for the full project position. The stance is summarised in the README's own words as open source, community-driven and anti-piracy.

The licence is AGPL v3, the language is Swift, and the app targets iOS 15 and later on iPhone and iPad. The releases are v2.0.1 from 2026-09-18, v2.0.0 from 2026-09-03 and v1.9.2 from 2026-04-16, and the last push was on 2026-09-18.

The platform table is the real scope of the project

The supported platforms table in the README is the fastest way to understand what this app is, and it is a long list across several families.

Nintendo covers Wii, GameCube, 3DS, N64, DS, Game Boy Advance, Game Boy Color, Game Boy, NES, Famicom Disk System, SNES, Virtual Boy and Pokemon Mini. Sony covers PlayStation and PlayStation Portable. Sega covers Dreamcast, Saturn, Master System, Game Gear, SG-1000, Genesis 32X and Super 32X, Sega CD and Mega-CD, and Genesis and MegaDrive. Atari covers Jaguar, Lynx, 7800, 5200 and 2600.

The rest of the table is the interesting part for a phone. Arcade is covered by MAME and FBneo. Microsoft contributes MS-DOS, Sun Microsystems contributes J2ME, Commodore contributes the C64 and the Amiga, SNK the Neo Geo Pocket and Color, NEC the PC-Engine, and Nokia the Symbian family across S60 versions and the N-Gage. The README notes that more platforms are planned upstream.

That J2ME and Symbian entries say something about the design brief. Those are platforms whose games ran on modest hardware, which is the same constraint an iPhone imposes, and it suggests the core selection is aimed at titles that translate well to a touchscreen with limited input.

Features that make sense on a phone

The feature table is organised by what the phone has to solve, and the entries are specific rather than generic.

Saves come as manual saves plus 50 auto-save slots. Gameplay controls include 5x speed control, cheat-code support, custom shortcuts and a full-screen orientation mode. Visuals offer retro filters, screenshot capture and custom third-party compatible skins. The rewind feature lets you rewind the game progress and keep tweaking the levels, which is the feature that changes what a game is worth on a device with no physical controls.

Achievements are RetroAchievements integration with Hardcore Mode support, and a RetroAchievements account is required. Sync is iCloud for games, saves and settings, with encrypted storage and cloud backups. Cloud import covers Google Drive, Dropbox, OneDrive, Baidu Cloud, Aliyun, WebDAV and SMB, which is the feature that makes a large library portable when the device storage is not.

Controllers are handled natively for Joy-Con, DUALSHOCK, Xbox and generic Bluetooth controllers, plus keyboard, Mac and multi-controller support, and the Global Navigation and Focus entry means the whole user interface can be operated with a keyboard or a controller, which matters more on a handheld than the feature list suggests.

Cross-screen play covers AirPlay mirroring and phone-to-TV play for big-screen sessions, and the full-screen orientation entry is really a presentation feature, with dynamic backgrounds, background music, a variety of game cover carousel styles and full customization.

Building it needs an Apple developer account and Git LFS

The development notes list what a build machine needs, and it is a short list with some awkward conditions.

You need macOS with Xcode 26 or newer, the iOS SDK 15 or newer, and Swift 5.9 or newer. You need Git LFS, because the repository carries binary cores and bundled system assets, which is the difference between a clone that works and one that produces missing files. You need an Apple Developer Program account for services such as App Groups, In-App Purchases and iCloud, and the README is explicit that these capabilities must be configured by the builder or removed before compiling, so the account is not optional for a stock build. And you need third-party API keys for services configured through `Cipher.swift`, when those services are enabled.

At runtime, the requirements are more modest. An iPhone or iPad that can run the selected core, legally obtained game backups and any required system files, an optional RetroAchievements account for achievement tracking, and optional cloud provider accounts for the import and sync workflows.

That split is the point. Most users never build, and the ones who do are taking on signing, capabilities and API keys, which is a real cost even for a project with an open licence.

Four build steps and a signing change

The build steps are given as a numbered sequence.

First, install Git LFS:

   brew install git-lfs
   git lfs install

Then clone the upstream repository with its submodules:

   git clone --recursive https://github.com/Manic-EMU/ManicEMU.git

Then open the Xcode project:

   open ManicEMU/ManicEmu/ManicEmu.xcodeproj

The last two steps are the ones people miss. You update the developer team and the bundle identifier in the ManicEmu target's Signing and Capabilities settings, and the README then tells you to wait for Swift Package Manager to finish resolving packages before running the app with `Cmd+R`.

The `Cmd+R` instruction is worth a note, because the app is a host for other people's emulator cores and bundled system assets, and the first run is a long one. The README's runtime section says as much from the other direction, listing the hardware, the legally obtained backups, the optional accounts and the core you intend to run.

The repository holds cores, system data and the app itself

The top level of the repository is unusual for an application, and it explains the build requirements. There is `ManicEmu/` for the app itself, `Cores/` for the emulator cores, `System.core/` for the bundled system assets, `Dependencies/` for third-party components, `Scripts/` for the build and packaging helpers, and a `StikJIT/` directory, which lines up with the JIT workflows the README mentions in its availability caveat.

Alongside those are the files a project like this needs: `ANTI_PIRACY.md`, `SECURITY.md`, `THIRD_PARTY_NOTICES.md`, `CONTRIBUTING.md`, `CODE_OF_CONDUCT.md`, a `.gitmodules` file for the submodules, and a `docs/` directory holding the branding assets.

The distribution model is also unusual. The app is on Apple's App Store and, in parallel, on the sideloading channels StikStore and SideStore, and the README is straightforward about the consequence. App Store builds and sideloaded builds may differ where Apple services, signing or JIT workflows are involved. The same paragraph notes that compatibility and performance vary by device, iOS version, emulator core, game and JIT availability, which is a compact way of saying that the same game will not feel the same on every device.

The project's position on content is settled and repeated in the README rather than left implicit, which is a good sign for anyone deciding whether to contribute to it or build on it.

Editorial conclusion

Adopt Manic EMU if you have your own legally obtained backups and want one iOS app rather than a separate emulator per system, especially if you want sync, cloud import and rewind in the same place. Do not adopt it expecting the App Store build to behave like a sideloaded build, since the README says the two may differ where Apple services, signing or JIT workflows are involved. Verify first that the core you need exists for your iOS version, that your device and the chosen core can run the game, that the rewind and RetroAchievements features are acceptable for the titles you play, and that the AGPL-3.0 terms, which cover network interaction as well as distribution, are what you want before you build on it.

Frequently asked questions

Official sources

1. Issues
2. License: AGPL-3.0
3. Manic-EMU/ManicEMU on GitHub
4. README
5. Releases