Listen in Sam's voice (generated with ElevenLabs)
There's a game that almost destroyed the studio that made it — not because it failed, but because of how it succeeded. Jetpack Joyride, made by Halfbrick Studios out of Brisbane, Australia, was released in 2011 and became one of the most important mobile games ever made. It invented mechanics that every major endless runner after it would copy. It was the game that made the freemium model feel good instead of predatory. And it nearly broke the company that shipped it, because Halfbrick pivoted to make it, bet everything on one swing, and then had to figure out how to follow it up. That tension — between the game that proved the model and the cost of proving it — is the story worth telling.
Let me start with where Halfbrick came from, because context matters here. Halfbrick was founded in 2001 in Brisbane as a Game Boy Advance developer. That's not a glamorous origin story. They made licensed titles for handheld consoles — games tied to film properties, games that needed to fit in a cartridge, games that measured success in box copies on a shelf in a Target. They were good at it. They built real engineering chops. But they were in a business where the developer was the least powerful player in the value chain — the publisher dictated the game, the license dictated the content, the platform dictated the format.
The iPhone changed everything for studios like Halfbrick in the way it changed everything for every small studio: suddenly there was a direct channel to consumers, no publisher required, no disc manufacturing, no retail negotiation. But the early App Store was also chaotic in ways that made it hard to build strategy around. Games went to the top of charts for random reasons. Marketing was primitive. The signal was unclear.
Halfbrick's first major mobile hit was Fruit Ninja, which shipped in April 2010. Fruit Ninja is deceptively simple — swipe to cut fruit, avoid bombs, don't miss. The mechanic is so clean it feels inevitable in retrospect. But the insight behind it was real: touchscreens reward swiping, and swiping through things is satisfying in a way that no prior form factor could deliver. Fruit Ninja sold for 99 cents and was a genuine hit. It gave Halfbrick financial runway. It proved that their instincts for mobile mechanics were good. And it raised the question of what came next.
What came next was Jetpack Joyride, and the origin of the game is a story about constraints becoming clarity. The lead designer was Luke Muscat, who pitched the game internally not as an endless runner but as something simpler and more direct: you press the screen to fire a jetpack, and the jetpack carries you up. Release the screen and you fall. That's the game. One input. Constant movement forward. Obstacles you must navigate with that single mechanic.
The reason that simplicity works — and this is worth spending a moment on — is that single-input games on mobile are almost always better than multi-input games. Your thumb is doing one thing. The cognitive bandwidth is freed up to read the environment, to make decisions about when to hold and when to release. When the input is binary — on or off — the skill expression comes from timing, not from remembering which button does what. Jetpack Joyride reduced the control scheme to its minimum viable form and then built complexity entirely through the level environment. That's excellent design.
The obstacle vocabulary Halfbrick developed is worth examining specifically. The electric zappers are a chain of spheres connected in patterns that rotate or pulse. The missiles are homing, which sounds unfair but isn't — there's a warning system, a targeting reticle that gives you just enough time to react. The laser beams sweep in patterns that are readable if you're watching ahead of your character. Every obstacle type in Jetpack Joyride teaches you something about how to avoid it, and none of them are pixel-perfect in their demands. The game is punishing but not random. That distinction matters enormously for player psychology.
Barry Steakfries — the protagonist, a man in a tracksuit who steals a jetpack from a laboratory — came from an earlier Halfbrick game called Age of Zombies. He was a stock character in a game that didn't take itself seriously, and that tonal choice turned out to be load-bearing. Jetpack Joyride is a game that knows it's absurd. You're a guy in a track suit using a machine gun jetpack to fly through a military lab collecting coins and power-ups while scientists run away from you. There's a vehicle system where Barry pilots everything from giant robots to teleportation bubbles. The game does not pretend to be something it isn't. That self-awareness created space for comedy, for weird power-ups, for cosmetic items that didn't need to make physical sense.
The freemium conversion is where Jetpack Joyride made history. The game originally launched as a paid download for 99 cents on August 31, 2011. Six weeks later, Halfbrick made it free. The reasoning was data-driven: the paid barrier was limiting downloads, and the game was well-designed enough for in-app purchases to sustain the business without a paywall. The pivot to free coincided with an update that added the gadget system — purchasable upgrades that made runs longer and easier without being required to complete the game.
This sounds routine now. In 2011 it was a genuine moment in the evolution of mobile monetization. The conventional wisdom was that free-to-play meant pay-to-win, or it meant predatory mechanics designed to extract money from players who weren't paying attention. Jetpack Joyride showed that you could design a free game where the monetization felt fair — where spending money was genuinely optional, where the core experience was complete without a purchase, where players who didn't spend money still had a great game. The in-app purchase as a goodwill gesture rather than a tollbooth. That model is so ubiquitous now that it's hard to remember when it wasn't.
The mission system was the other major mechanic innovation. Every run in Jetpack Joyride gives you three active missions: things like 'travel 500 meters without using a vehicle' or 'collect 50 coins during a single missile dodge' or 'zap yourself and then immediately explode.' Missions create context around runs that would otherwise be pure score-chasing. They give players a reason to attempt different play styles. They create micro-narratives within individual play sessions — you're not just running again, you're working on that missile dodge mission. The completion of missions unlocks stars that unlock gadget slots. The system ties together monetization, skill development, and player motivation into a single loop.
It's worth noting what Halfbrick was up against when Jetpack Joyride shipped. Temple Run had launched in August 2011 — literally the same month — and was already climbing the charts. Temple Run defined a certain flavor of endless runner: third-person, 3D corridor, swipe to turn. It was a massive hit. The two games occupied the same moment in the App Store but made completely different design choices. Temple Run was more cinematic and spatial. Jetpack Joyride was more elemental and systemic. Both succeeded. But Jetpack Joyride's systems depth — the missions, the gadgets, the vehicles — gave it longer legs. Players who mastered Temple Run eventually left. Players who engaged with Jetpack Joyride's systems found more to do.
The difficulty with this kind of success is what it does to the team that created it. Halfbrick grew rapidly after Jetpack Joyride. The game peaked at number one in 35 countries. It won Apple's Game of the Year. It was downloaded more than three hundred million times before the decade was out. But sustained hit-making is not a skill you acquire by having one hit — it's a skill you have to build on a different timescale, with different institutional practices, than the conditions that produced the original success. Halfbrick tried to follow up Jetpack Joyride with multiple new projects, scaled up their studio substantially, and found that none of the follow-ups replicated the success. By the mid-2010s they had to restructure significantly, cutting staff, simplifying the organization.
This is a pattern you see across the history of mobile gaming. The studio that makes the one great game gets the funding and the resources and the team size that large games require, and then discovers that those inputs don't guarantee proportional outputs. Creativity doesn't scale linearly with headcount. The conditions that produced Fruit Ninja and Jetpack Joyride — small team, direct responsibility, clear ownership, minimal bureaucratic overhead — are exactly the conditions that large success tends to destroy.
Halfbrick's response to that challenge was, eventually, to return to those conditions. They reduced to a smaller core team. They focused back on what they did well. They kept Jetpack Joyride alive with updates across more than a decade — a remarkable run for a mobile game. A sequel, Jetpack Joyride 2, launched in late 2022 on Apple Arcade, moving to a subscription model that removed in-app purchases entirely. The core mechanic was preserved while the business model evolved.
What Jetpack Joyride got right that most games don't is the relationship between input simplicity and system complexity. The genius of holding to go up and releasing to go down is that it's a mechanic you understand in three seconds and develop nuance with over hundreds of runs. The zappers and missiles and laser beams compose into scenarios that require reading and reaction. The vehicles introduce temporary changes to the core mechanic — the gravity suit inverts the input, the star vehicle changes the speed profile — that create variety without requiring the player to learn a completely new game. Every layer of complexity in Jetpack Joyride is built on top of the single-input foundation. Nothing requires the player to do two things at once.
I think about Jetpack Joyride when I think about what makes a mobile game worth studying. Not the graphics, which are charming but not technically impressive. Not the audio, which is good without being memorable. The mechanic design and the systems design. The way a small team in Brisbane looked at a new platform and asked what kind of game a touchscreen wanted to be — not what kind of game could be ported from a console, not what kind of game the license required, but what the hardware was specifically good at. The answer was: one thumb, one decision, infinite variation. They got that right, and everything else followed.
A game made by a small studio in Brisbane is still being played and updated by new generations of players today. That's what good product work looks like.