About Fruit Ninja

Fruit Ninja throws fruit up from the bottom of the screen and asks you to slice it before it falls, drawing a blade trail with a swipe while leaving the bombs strictly alone. This is the official Halfbrick version for browsers, licensed through GameDistribution — the same game that defined an era of touchscreens, running directly in a web page with a mouse drag or a finger swipe standing in for the original touch gesture.

Halfbrick Studios, a developer based in Brisbane, Australia, released Fruit Ninja on iPhone in April 2010, when the App Store itself was barely two years old. It became one of the first genuine mobile mega-hits: within two years it was installed on roughly a third of all iPhones in the United States, and by its fifth anniversary in 2015 it had passed a billion downloads across platforms. Almost everything about how casual games are designed today owes something to what worked here.

What worked is worth naming precisely: the entire control vocabulary is one gesture. In 2010, most mobile games were ports that drew virtual buttons and joysticks onto glass, asking your thumbs to pretend the screen was a gamepad. Halfbrick instead built a game out of the input a touchscreen actually wants — a swipe — so the physical act of playing already felt good before any scoring system got involved. Slicing is satisfying at the level of the hand, the way popping bubble wrap is, and the game is honest about being built on that.

The bomb is the whole rulebook. Slicing fruit is always good; slicing a bomb ends a Classic run instantly. One prohibition is enough to turn flailing into aiming, because every wide, greedy swipe now carries a cost. The tension in a good run comes entirely from that single rule — the moment a bomb rises through the middle of a fruit cluster, the easy gesture suddenly requires precision.

Three modes reframe the same act. Classic gives you three missable fruit and instant death by bomb, so it plays as survival. Zen removes bombs entirely and runs on a timer, making it pure slicing without punishment. Arcade is a sixty-second score attack with special bananas that trigger frenzies, slow time or double points, and it is where the combo system — clearing several fruit in one stroke — and critical hits turn a toy into a technique. Same swipe, three different reasons to make it.

Tips for Fruit Ninja

• Wait half a beat before slicing a cluster. Fruit thrown together drifts closer at the top of its arc, and one stroke through three or more pieces scores a combo worth more than three separate cuts.
• Draw deliberate lines rather than scribbling. Wild zigzags feel fast but cross bomb paths you never registered — most Classic runs end on a swipe the player did not really choose to make.
• In Arcade, treat the special bananas as the actual objective. Frenzy, slow-motion and double-score bananas decide the final number far more than ordinary slicing does, so never let one fall.
• Use Zen mode as a practice room. With no bombs and no lives, it is the only place to drill long combo strokes without a run-ending penalty for greed.
• Slice near the top of the arc. Fruit hangs almost still at its peak, and cutting there buys you time to read what is rising next instead of chasing pieces on the way down.
• On a mouse, hold the button and carve curves instead of flicking short segments — the blade follows the pointer continuously, and a longer controlled stroke is how combos happen off glass.

Did you know?

• Halfbrick Studios released Fruit Ninja in April 2010 for ninety-nine cents, and by 2012 it was reported to be installed on about one in three iPhones in the United States.
• The game passed one billion downloads by its fifth anniversary in 2015, a figure that at the time put it behind only Angry Birds among mobile games.
• The one-gesture design proved portable beyond touchscreens: a Kinect version in 2011 had players slicing with their whole arms, and Fruit Ninja VR later did the same with motion controllers.
• The bomb is the game's only prohibition — every other object on screen rewards being sliced — which is why Classic mode generates tension from a single rule rather than a rulebook.