The Game That’s Unplayable—And Why That’s a Good Thing

I wanted to love Hop.earth. I really did. The idea—turning the entire real world into a racing game using OpenStreetMap—is the kind of audacious, childlike dream that makes you believe the internet still has magic left. I opened the link, ready to floor it through my own neighborhood.

Then I pressed ‘F’ to find a car. Nothing. I clicked around. The controls were a mess. No vehicle appeared. I was a ghost driver in a ghost town. The top comment on the thread read: “Buggy to the level of unusable.” Another: “Cursed buggy mess.” Fair.

But here’s the thing: I couldn’t stop playing. And neither could the people who called it a mess.

Buggy but fun beats polished but boring every time.

That’s not an excuse for sloppy engineering. It’s a signal that the core loop is strong enough to survive broken execution. Hop.earth has a problem: you can’t see your car, the controls are chaotic, and the whole experience feels like a prototype that escaped the lab. Yet the same players who curse it also say “buggy but fun.” They’re primed to love it. They want to love it. That’s not a bug report—that’s a product-market fit whisper.

You’ve probably played a game that was technically flawless but left you cold. We all have. The graphics were crisp, the physics were tight, the UI was a joy to navigate. And you uninstalled it after two hours because it had no soul. Compare that to Hop.earth: a broken map, no car, random crashes—and yet you’re laughing, swearing, and sharing the link with friends. Why?

Because the concept is so novel that the brain fills in the gaps. You’re not playing a buggy game; you’re imagining the possibility of a perfect game. The ambition is the hook. The execution is just the current obstacle.

If you’re building anything with open data—a location-based app, a real-time map, a game that uses the world as its canvas—you know this tension. You’ve got a map, you’ve got an idea, but the technical debt is a nightmare. You’re tempted to delay launch until every edge case is polished. Don’t.

What matters is not whether it works perfectly, but whether it sparks joy in its brokenness.

Most developers obsess over polish. That’s a mistake. Polish is the enemy of discovery. It’s the force that turns a bold experiment into a safe, forgettable product. Hop.earth is not safe. It’s a mess. But it’s a mess that makes people feel something—frustration, yes, but also wonder. That emotional cocktail is worth more than a thousand clean codebases.

Here’s the contrarian take: Hop.earth’s bugs are actually a feature. They force you to interact with the game differently. Without a visible car, you have to imagine your position. Without smooth controls, you have to learn the quirks. The friction becomes part of the experience. It’s the difference between a polished racing sim and a go-kart with a loose steering wheel. One is a simulation; the other is a memory.

So go ahead, launch your buggy mess. Just make sure it’s fun. Fix the stability, yes. Add the missing car, yes. But never sand down the rough edges that make it feel alive. The moment you polish away the imperfections, you polish away the soul.

Hop.earth isn’t a finished game. It’s a proof of concept that the real world is the ultimate playground. And the fact that people still enjoy it despite its brokenness is the most hopeful signal for location-based gaming I’ve seen in years.