Jarcade

About

Keeping Java ME games playable

A generation of mobile games shipped as .jar files for phones that no longer exist. Jarcade gives those games somewhere to live — and a way to actually play them again, in any modern browser.

Why it exists

Emulating a J2ME title normally means finding the right desktop emulator, installing a Java runtime, and wrestling with keypad mappings before you see a single frame. Most people give up before that point, and the games quietly become unplayable.

Jarcade removes every one of those steps. Upload a package or pick something from the library, confirm which keys you want to use, and the game runs in the tab you already have open. Your controls follow your account, your saves stay on your device, and the game keeps running even while you browse for the next one.

How it is built

Two independently deployed applications talking over a REST API.

Frontend

Next.js App Router with TypeScript and Tailwind CSS, deployed on Netlify.

Backend

Django REST Framework with JWT auth, deployed on PythonAnywhere.

Emulator

freej2me-web compiled to run in the browser through CheerpJ — no server-side execution.

Uploaded games are treated as untrusted data. Files are validated as ZIP archives, stored as-is, and only ever executed client-side by the emulator — the server never runs uploaded bytecode.

Common questions

What kind of files can I upload?
Java ME game packages — a .jar file, optionally with its .jad descriptor. Jarcade reads the MIDlet manifest inside the JAR to fill in the title, developer, description, and icon automatically.
Where are my save files stored?
In your own browser. The emulator writes MIDP record store (RMS) data to IndexedDB, so progress stays on the device you played on and is never uploaded.
Why does the first game take a while to start?
The first launch downloads the Java runtime the emulator needs. After that it is cached, so later games start much faster.
Do uploads appear immediately?
No. Every upload starts as pending and becomes public once a moderator approves it. You can still open, edit, and test your own uploads right away.
Is uploaded code run on the server?
Never. JARs are validated as archives and stored as opaque files. The only place a game executes is inside your browser tab.

Who built this

Jarcade is designed and developed by Muzahidul Islam, a full-stack developer working with Next.js, Django, and everything in between.

Ready to add something to the library?