Noomiclone

Noomiclone is a gymnastics bar game where the entire input is four keys. You hang from a post, swing, throw your body into a shape, let go, and either reach the next bar frame or drop to the orange floor. The browser build runs on Unity WebGL inside the page, so nothing installs and no account is needed. It belongs on this site for the same reason the wacky walking games do: the whole game is one press landing inside a window of a few frames.

Two things about this build are worth fixing in your head before the first attempt. It is version 0.9, and the developer's itch page still marks it In development. And it has one scene. No map picker, no modes, no lobby. From the moment it loads you are on the same bar, and every attempt after that is the same bar again.

That second point explains most of the confusion around the game. The store listings for the phone app describe 12 bar maps and 6 tumbling maps, and people repeat that number when they talk about the browser version. It does not apply here. What loads in your tab is a single fixed scene, and the map count belongs to a different build of the same game.

The same four actions exist as large buttons in the left and right margins of the player, labelled arch, tuck, let go and reset. A phone or trackpad user is therefore pressing the same four verbs rather than a cut-down set, which is more than most browser builds bother to do.

The game's own hub page names six operations: Arch, Tuck, Release, Twist, Grab and Reset. Only four are bound in the browser build. Twist and Grab never show up in its interface, so a guide that tells you to twist out of a swing is describing the phone app. Those are the four tools. What decides an attempt is which one you reach for when it starts going wrong.

The top of the screen carries a running count: 0 regrabs, then 1, then more. A regrab is a second grab at the bar after you have already let go. On the phone app the same counter feeds skin unlocks. The browser build never shows a score screen that explains what it does with the number here.

Read it as a record of bailing rather than a score to chase. Zero regrabs on a completed attempt means one clean grab. One regrab means you caught the bar, lost it and had to catch it again, which is a different skill from a clean catch and should not be filed under progress.

It also does something a timing game needs. It turns a feeling into a number. You cannot see your release timing in this build, but you can see how often it was wrong.

The Google Play listing advertises 12 bar maps and 6 tumbling maps, slow motion, replay export, draggable buttons and a high frame rate option, on version 2.3.2 from October 2026. The browser build says 0.9 and In development. Those are not two descriptions of one product. They are two products at very different stages, and the map count only holds for the one on your phone.

The build backs that up on its own. It ships a single scene file, and a player comment on the itch page calls the web version a proof of concept where the maps cannot be changed. Different kinds of evidence, same conclusion.

For a game built on repeated attempts, one scene is a defensible trade. A map list would put a load pause between attempts, and attempts are the entire product. What you give up is variety. Ten minutes in, the bar and the sky behind it stop being new, and the only thing left that can change is your timing.

Physics games usually ask you to slow down. There is no slow motion in this build, so the equivalent is to narrow what you watch.

Ten minutes is a sensible session at this stage. The scene does not change, so the thing that improves is your sense of the window, and a sense of a window holds better than a memorised route does.