Skip to content

Product History

FullRoid Games Catalog: Curated Android Emulator Game Library

A look at the FullRoid Games catalog repository: how a curated Android emulator game library is assembled without bundling copyrighted content.

FullRoid Games Catalog: Curated Android Emulator Game Library preview

Written by the Fulldive product engineering team, based on direct inspection of the repositories listed below.

When users ask about an Android emulator game library or a free Android emulator for console games, they usually want to know two things: is there something to play out of the box, and where do games come from? This post explains what the separate fulldiveVR/FullRoid.Games repository actually is and how it supports Fulldive’s One Emulator for Game Consoles. It is a catalog repository — curated, compatible content work — not a ROM dump and not a distribution of copyrighted games. We are deliberate about what it does and does not include.

Two repositories, one product

The Fulldive emulator is split across two repositories:

  1. fulldiveVR/FulldiveExtension.FullRoid — the emulator app itself. History from 2017-09-04 to 2026-04-10, 1,778 commits. Covered in The FullRoid evolution.
  2. fulldiveVR/FullRoid.Games — the catalog. A shorter, content-focused repository with 7 commits inspected between 2026-04-08 and 2026-04-10.

They are intentionally separate. The emulator app is engineering work around cores, save states, controllers, and the Android platform. The catalog is content work: what titles, which covers, which metadata, which per-title compatibility notes. Splitting the two means the emulator can ship independently of catalog changes and vice versa.

What the catalog repository actually is

The FullRoid.Games history is short because the repository is new:

  • Commit 70c6098: initial commit.
  • Commit 272aa60: additional initial setup on 2026-04-08.
  • Commit 483f526: bugfixes and performance improvements during the first catalog iteration.
  • Commit f684e3f: first version of games — the first meaningful catalog payload.
  • Commit 01e8359: added Lunar Runner entry.
  • Commit 04d0796: Lunar Runner icon.
  • Commit 76695c8: added Durio entry.

Those are catalog entries: titles, icons, and metadata, curated for integration into the emulator’s library screen.

How the catalog connects to the app

The main emulator repository integrates this catalog via commit 809ab678, which added a free game catalog. When a user installs the emulator and opens the library, the app can surface catalog entries alongside any supported game files the user has placed in their own folders.

Key points:

  • The catalog does not ship copyrighted commercial ROMs. It is not a library of Nintendo, Sony, or Sega first-party titles.
  • Entries are curated items compatible with the emulator’s cores.
  • The emulator still does not provide commercial games.

If you came here expecting a list of famous retro titles, this post is going to disappoint you on purpose. The catalog exists to give users something to open on day one, not to imply the app is a piracy-adjacent product.

Why bother with a catalog at all?

Because “install an emulator, now find legal games” is a real adoption hurdle. A small curated catalog solves the cold-start problem for users who just want to try the app:

  • They can install and play something immediately.
  • They can test save states, fast forward, and controllers on real content instead of an empty library.
  • They see the library UI (migrated to Compose in commit 38ddf7fa on the main repo, with in-game menu and animated list follow-ups) doing what it was designed for.

The catalog is modest on purpose. Its scope is clear. Its licensing is verifiable per entry rather than hand-waved.

Why it matters for search intent

A lot of searches for “free Android emulator for console games” are, under the hood, searches for “somewhere to play something retro without a lot of setup.” Fulldive’s answer is: the emulator is free (with a Pro upgrade to remove ads), the catalog gives you something to open on first launch, and any further games you play are legally obtained game files you supply yourself. We don’t target pirated-ROM queries, and we don’t put copyrighted games in the catalog to pretend we do.

What good catalog engineering looks like

Three rules from the FullRoid.Games experience:

  1. Treat catalog as content, not code. Keeping it in its own repo keeps release cadence honest — you can update a cover without shipping an emulator update.
  2. Version every entry. Bugfix/performance pass in commit 483f526 shows the catalog is iterative, not “build once, forget.” Entries get refined as they’re tested.
  3. Be explicit about licensing. Each entry needs a clear path to a license the catalog can rely on. That’s why the repository is small and grows slowly, rather than ballooning with unchecked content.

This is one of many Fulldive content-and-app splits. The Fulldive company story describes the broader pattern of small specialized repositories orbiting each app. For emulator users specifically, the catalog is one more reason that The FullRoid evolution keeps producing user-visible changes even during periods that look quiet on the main app’s code.

The FullRoid.Games catalog is curated content intended for use inside Fulldive’s emulator apps. It does not contain copyrighted commercial games or ROM downloads, and the emulator does not include or distribute such content. Users who want to play their own classic games must provide legally obtained game files from hardware they own. Compatibility with any specific file varies by emulator core, core version, device, Android version, and controller. We do not claim universal console or game support, and we do not target queries for pirated ROMs.

Sources

Last updated: 2026-04-16. Commit hashes and version numbers are drawn from Fulldive repositories inspected on 2026-04-13.