Jolly Good emulators get standalone builds via new Quality Tea frontend

A new build pipeline wraps Jolly Good emulator cores in a lightweight WIMP frontend called Quality Tea, letting users run them as ordinary standalone apps.

AI-drafted from 4 sources. This story was written with AI from the outside reporting listed under Sources, and checked by automated tools before it went up. The originals have the full detail.

The Jolly Good project has started shipping its emulator cores as ordinary standalone applications, rather than requiring a separate frontend to load them. A new repository called jgbuilds packages each core with a lightweight interface called The Quality Tea Frontend, or QTea, so the result looks and behaves like a normal desktop emulator you double click to open.

Jolly Good is a framework for building emulator cores, comparable in spirit to the better known libretro API used by RetroArch. Cores written against what its developers call the Jolly Good API can, in theory, be dropped into any frontend that supports it. Until now that has mostly meant using a multi-core frontend to pick a core and a game, in the RetroArch style. QTea takes the opposite approach. According to the jgbuilds repository, it is “a classic WIMP emulator frontend”, WIMP being the old shorthand for windows, icons, menus and a pointer, the sort of interface Windows 95 users would recognise instantly and younger emulator fans mostly do not have to think about because everything now lives in a gamepad friendly grid.

What the standalone build actually changes

The trick, as the repository describes it, is that QTea can be “linked against emulator cores using The Jolly Good API”, and the jgbuilds scripts do that linking at build time rather than leaving it to the user. The output, the maintainers write, is “what feels like a traditional standalone emulator, using a whitelabel frontend”, meaning each release is effectively a rebadged copy of QTea glued to one core, with no separate installation step or core browser to wrestle with. The repository lists minimum requirements of Windows 10, macOS 15 and Ubuntu 26.04, which is a notably recent bar for a project aimed at reviving old hardware, and worth bearing in mind if you are running an older Linux distribution.

The jgbuilds repository does not spell out, in what is available, exactly which consoles are covered in this first wave of releases, only that the build scripts pull cores in via the shared API. For anyone who has previously had to hunt down a specific Jolly Good core and bolt it onto a generic frontend by hand, that is still a meaningful simplification, even if the full list of supported systems is not yet clear from the announcement itself.

A separate, homemade frontend shows the appetite for this

The desire for friendlier front ends around Jolly Good cores is not limited to the official project. A separate Reddit thread from a few days earlier describes an independent frontend called Goliath, built for Geolith, the Jolly Good core that emulates Neo Geo MVS, AES and Neo Geo CD hardware. Its creator, who posts as u/epsx, says plainly they are “not a programmer” and built the tool largely to test how well large language models could help write one, adding “I hope you will like it… or not”. Goliath handles settings, save backups, audio export and per game configuration, and the author reports it running well on both Windows and Linux, though that is a self-report rather than an independent test, and the tool is unrelated to the official jgbuilds effort.

Taken together, the two point at the same gap: Jolly Good's cores are useful but bare, and both the project itself and its community are now racing to wrap them in something a normal user would recognise as an emulator rather than a library. What is still unconfirmed is how complete the standalone lineup will get, and whether QTea will absorb features, like Goliath's per-game settings, that currently only exist in third party tools.

Sources

Image: GitHub