iiSU: an Android-first, visuals-first emulation frontend in alpha

What iiSU actually replaces on an Android handheld

iiSU is a frontend, and the README is explicit about the boundary: it does not include games or emulators. What it replaces is the home screen. The project describes itself as a launcher with a UI built to display and launch games and apps, developed Android-first, with handhelds as the target form factor. That framing matters more than it sounds. On a stock Android handheld you get a phone-style launcher that knows nothing about your ROM library, your emulators, or your RetroAchievements profile. iiSU sits in that slot and builds a library view on top of the ROMs you already have and the emulators you already installed. The audience is therefore narrow and specific: people who own an Android-based handheld, have already set up emulators, and want the browsing and launching layer to look like a game console rather than a phone. The README also mentions web services and community asset work beyond the app, which suggests the project sees the launcher as one part of a larger effort around emulation artwork and metadata.

How the library, metadata and scraping pipeline fits together

The mechanism visible in the README is a pipeline with several optional inputs. On first launch, an interactive onboarding walks through configuration and then indexes your library and prepares media, a step the README calls Asset Prep. ROM import is where you point iiSU at a ROM folder, and where you can link ES-DE metadata if you are migrating from that frontend, change where iiSU stores media, and check which systems were detected. Scraping services are configured separately with keys and sign-in data, and the initial scrape is a distinct step that the README says is not required if you have linked ES-DE metadata or simply do not want to scrape yet. RetroAchievements is a second, parallel data path: you connect an account with an API key from the RetroAchievements settings page, and then hash your ROMs on a dedicated onboarding page so the launcher can match them and display achievement data. RomM server linking appears in the ROM import step and is labelled experimental. The practical consequence is that iiSU is not a single import button. It is a set of independent sources (local ROM folder, ES-DE metadata, scraped media, RetroAchievements hashes, optional RomM server) that you can enable in any combination, and the quality of what you see depends on which of them you fed it.

Installing iiSU from the Releases page and running first setup

There is no package manager install. The README points to the GitHub Releases page for the latest APK, and notes a built-in updater plus Obtainium as an alternative way to keep it current. Download the APK on the device and install it. The package identifier used in the Obtainium link is com.iisulauncher, and the same link points at the repository URL.

# Obtainium deep link from the README (open on the Android device)
http://apps.obtainium.imranr.dev/redirect.html?r=obtainium://app/%7B%22id%22%3A%22com.iisulauncher%22%2C%22url%22%3A%22https%3A%2F%2Fgithub.com%2Fiisu-network%2FiiSU%22%2C%22author%22%3A%22iisu-network%22%2C%22name%22%3A%22iiSU%22%7D

If you open that link on the device, Obtainium should register iiSU as a tracked app so future releases are picked up there instead of by hand. The README also states iiSU has its own updater, so you can stay on the built-in path if you prefer.

After installing, launch the app and work through the onboarding flow. The steps are ordered: welcome, dual screens if an external display is detected, customization for theme colour and browsing style, ROM import, quick access apps, RetroAchievements login, scraping service keys, asset prep, RetroAchievements hashing, scrape pass, and a final overview. The README notes every step can be skipped and revisited, and that onboarding can be relaunched at any time, which makes a partial setup a reasonable first pass.

To make iiSU the actual home screen, the README gives a specific route: open Settings, search for Default Home App, and select iiSU. After that, the README's post-onboarding list suggests checking Settings (select), then iiSU Settings, then Updates, for Starter Pack, emulator, and iiSU updates. If a console will not launch, the documented fix is Quick Settings (select) on the selected console, then Console Settings, then Edit Console Settings, and choosing the correct emulator, with RetroArch version selection called out as a common cause.

The alpha warnings are the honest part of the README

The README does not pretend the software is finished. It states that iiSU is in an early Alpha stage focused on building the technical foundation for future iterations, and that bugs and issues will exist. Releases are versioned 0.0.7.x, which is consistent with that claim. The last push to the repository was on 2026-07-31, the same date as the 0.0.7.4 release, so the project is not dormant, but the version number and the README's own language should set expectations. There is a second limitation that is structural rather than temporary: iiSU depends on emulators you install separately, and the README treats emulator mapping as a per-console setting you may have to correct. That means a broken launch is not necessarily an iiSU bug. It can be a mismatch between a console entry and the emulator version on your device. The RomM server integration is explicitly experimental, so treating it as a production path would be a mistake. Anyone who wants a launcher that never needs per-console configuration should look elsewhere, because iiSU's design assumes you will do that configuration.

iiSU compared with ES-DE as the metadata source

The most informative comparison in the README is not with another Android launcher but with ES-DE, because iiSU treats it as an import source rather than only a rival. During ROM import you can link ES-DE metadata, and the README says that if you do, the initial scrape is not required. The difference in approach is where the work happens. ES-DE expects you to scrape and maintain a metadata set for a desktop-oriented frontend, and iiSU can consume that output instead of rebuilding it. If you already have a curated ES-DE library, iiSU becomes a display layer over metadata you already paid for in time. If you do not, you fall back to iiSU's own scraping services, which means entering keys and sign-in data for those services and running a scrape pass. Either way the metadata is the expensive part, and iiSU is flexible about its origin rather than opinionated about it. That flexibility is a real design choice, and it is also why setup has so many optional branches.

Maintenance, updates and the licence question

Updating is handled in three places according to the README: iiSU itself, the Starter Pack, and emulators. The Starter Pack has its own release line, with starter-v1.0.0 published on 2026-06-21, which suggests it is versioned separately from the app and updated on its own schedule. Checking all three from iiSU Settings, Updates is the documented routine, and the built-in updater means you are not required to sideload each release manually. The repository's top level contains only .github, README.md, and an updates directory alongside a .DS_Store file, so the visible repository is not where the application source lives. The README does not state a licence, and the repository metadata does not name one either. That is a real gap for anyone who needs to know the terms before redistributing or bundling iiSU, and it is worth resolving with the maintainers through the Discord or the issue tracker rather than assuming a permissive default. The README also links a Ko-fi page for support, which is a funding channel, not a licence statement.

Editorial conclusion

Adopt iiSU if you run Android handhelds, already have emulators and ROMs, and want a launcher that puts cover art and metadata in front of them; the project's own warning is clear that it is a frontend, not an emulator, so it is the wrong tool if you expect it to supply games or emulator cores. Do not adopt it if you need a stable daily launcher, since the README describes an early Alpha where bugs and issues will exist. Before installing, verify which emulator each console is mapped to under Quick Settings, Console Settings, Edit Console Settings, because the README names RetroArch version selection as a common cause of games not launching.

Frequently asked questions

Official sources

1. iisu-network/iiSU on GitHub
2. Issues
3. Project website
4. README
5. Releases