Fruit Alchemist is coming to Google Play

· 5 min read

By Phil · building Legitsauce

Update, September 8, 2026: Fruit Alchemist is now available on Google Play. Read the release announcement and Android roadmap. The original preview follows below; its launch estimate is no longer current.

Fruit Alchemist has been playable in the browser for a while now. You open a tab, drop fruit into a barrel, try to merge your way up to the Golden Quince, close the tab. That version works and I still like it. But I've been quietly building a native Android version alongside it, and it's nearly done.

Mid-September 2026. Google Play. Phones, tablets, any device the store supports.

This is the first Legitsauce game to leave the browser, and it felt like the right one to go first.

Why this game, why now

Fruit Alchemist was always built for a phone. The whole input is one finger: drag to aim, release to drop. The screen is a single barrel. There's no text you need to squint at, no minimap, no toolbar along the bottom eating your real estate. It already plays well in mobile browsers, which made me wonder what would happen if I stopped routing through WebAssembly and just ran it natively on the hardware.

The answer is that everything gets better in ways you feel immediately but struggle to name. The physics tick at a locked 60 fps with no dips. Fruit collisions land tighter. The merge animations snap instead of easing in a half-frame late. Touch response drops from "good enough" to instant. And the whole package sits under 80 MB, which is smaller than most app store icons feel like they ought to be.

Fruit Alchemist running natively on Android in full landscape, a barrel full of merged fruit mid-game with a score of 1,517 and a Pomegranate discovery card on screen
A mid-game run on the native Android build. The barrel, the preview shelf, the discovery cards, all running at native resolution with zero browser overhead.

What the native build actually buys you

The browser version runs inside Godot compiled to WebAssembly, and WebAssembly is genuinely impressive: a full game engine squeezed through a browser sandbox. But a sandbox is still a sandbox. There's a layer of abstraction between the game and the screen, and another between the touch event and the physics engine. Most of the time you don't notice. On a mid-range phone, sometimes you do.

The native build removes both layers. Godot talks directly to the GPU. Touch events arrive through the OS input pipeline with nothing in between. The result is a game that feels like it belongs on the device instead of visiting it through a window.

The crispness is the thing that surprised me most. Same art, same sprites, same toon outlines, but rendered at the phone's native resolution without browser scaling. The fruit looks cleaner. The barrel grain is sharper. The whole scene has a presence that the browser version approximates but never quite matches.

How it looks across devices

The layout reflows to fit whatever you hand it. Portrait on a phone is the natural orientation, the one the game was drawn for, and on a tablet the extra screen real estate lets the barrel and the preview shelf breathe. Landscape works too, whether you are holding a phone sideways or propping a tablet on a kickstand.

Fruit Alchemist on a phone in portrait orientation, barrel filling with merged fruit, discovery card showing a Pomegranate
Phone portrait: the default orientation and the one the game was designed around.
Fruit Alchemist on a phone in landscape orientation, barrel and preview shelf spread across the wider viewport
Phone landscape: the barrel centers and the UI panels redistribute to the sides.
Fruit Alchemist on a tablet in landscape orientation, showing the barrel, preview shelf, and discovery card with room to spare
Tablet landscape: more breathing room around the barrel, the preview shelf and discovery card stay readable at arm's length.
Fruit Alchemist on a tablet in portrait orientation with the barrel and UI panels stacked vertically
Tablet portrait: the preview shelf and discovery card tuck underneath the barrel.

Time Attack mode runs identically on all of them. Ninety seconds, double-speed dropper reload, no game-over from the danger line.

Time Attack mode on a phone in portrait, showing the countdown timer at 89.2 seconds and a score of 2,140
Time Attack on a phone: the countdown timer sits between the score and the menu button.

Same rules, same promises

Everything that is true about Legitsauce in the browser stays true on the app.

No energy meters. No lives that refill on a timer. No premium currency. No video ads wedged between rounds. No "watch an ad to continue" wall at the moment you care most. The same display-ad model that keeps the site running keeps the app running. Ads sit in the margins. The game canvas is yours.

No account required. Your scores and your Harvest Calendar stay on your device, same as they do in the browser. I don't want your data and I've built no mechanism to collect it.

The Daily Orchard mode, the Time Attack, the Zen mode, the barrel skins you unlock by showing up: all of it transfers to the native build, same as it plays on the web. One game, two ways to reach it.

What comes next

The Play Store listing is in review. The build is stable. I've been playing it on my own phone for weeks now, which is the only QA process I actually trust for a game like this: does it survive the couch, the bus, the five minutes before sleep? It does.

Mid-September is the target. When it goes live I'll update this post with the direct link. If you've been playing in the browser and wondering whether the app is worth the install, the honest answer is yes. Same game, noticeably better at being that game.

Play Fruit Alchemist free in your browser while you wait, or keep an eye on the store.