I'll write the review now — no tooling needed for this one, it's a writing task with the research already supplied.
Bottom Line: Haiku, the Robot is a gorgeous, mechanically confident metroidvania that never quite escapes the shadow of the game it worships. It's an excellent 12-hour recommendation for anyone who finished Hollow Knight and wants that feeling again at two-thirds the difficulty and a fraction of the runtime — just don't expect it to surprise you.
The Gameplay Loop
The loop here is textbook, and I mean that as both compliment and criticism. You enter a room. You die to something. You learn the tell. You clear the room. You find a bench, a chip, a shortcut, or a wall you can't pass yet. You file that wall away and move on. Three hours later you come back with a blink and the wall was never a wall at all.
Mister Morris understands the rhythm of this. The gaps between ability grants are well-paced — long enough to make each new toy feel earned, short enough that you're never grinding through dead space waiting for the next unlock. That's a genuinely difficult tuning problem, and a lot of larger studios get it wrong. A solo developer nailing it deserves the credit.
Where the loop frays is navigation. This is the most consistent criticism in the player base and it's a fair one. The mid-game map is confusing in a way that doesn't feel like intentional disorientation — it feels like a mapping system that isn't doing enough work. In a genre where the map is the interface, that's not a cosmetic complaint. When you're standing in a corridor trying to remember which of four identical mechanical hallways led to the locked door you saw ninety minutes ago, the game has stopped being about exploration and started being about your own short-term memory. Good metroidvanias externalize that cognitive load. Haiku offloads too much of it onto you.
Combat and the Chip System
The combat is the best-argued part of the design. It's close-range and deliberate — you cannot kite, you cannot cheese, you have to walk into the threat radius and commit. Every swing is a decision with a recovery window attached. That's the correct design choice for a game this size, because it means the enemy roster doesn't need to be enormous to stay interesting. Five well-designed machine enemies in a room you have to enter is more compelling than twenty you can shoot from off-screen.
The bosses are where the game earns its 91%. They're demanding, readable, and built on the honest contract the genre requires: you lost because you misread the tell, not because the game cheated. Learning a Haiku boss feels like learning, not attrition. That's the hardest thing to get right in this genre and it's the thing Haiku gets most right.
The chip system is the closest thing here to an original idea, and it's a good one. Slotting upgrades to bend your build toward aggression, mobility, or survivability turns character progression into an active choice rather than a passive accumulation. The constraint is what makes it work — you can't have everything, so every chip you equip is a chip you're saying no to. Players love it, and they're right to. It's the one system where Haiku feels like it's making an argument rather than paying homage.
The Derivative Problem
We have to talk about it, because every player does.
Haiku doesn't just take inspiration from Hollow Knight. It takes the melancholy fallen-kingdom setting, the mute protagonist, the quirky NPCs delivering the dark backstory in fragments, the bench-rest structure, the charm-slot progression, and the restrained aesthetic. Swap bugs for robots and virus for infection and the diagram is nearly identical.
Here's my honest position: derivative isn't disqualifying. The genre is called metroidvania. It is literally named after the two games everyone copies. Nobody has ever been thrown out of this genre for being too influenced.
The real question isn't whether Haiku borrowed. It's whether it added. And the answer is: a little. The chip system has its own personality. The robot fiction gives the melancholy a different flavor — decay through corrupted code rather than biological infection has its own quiet horror to it. Corrupt Mode is a smart, cheap addition that respects the audience.
But those are refinements, not arguments. Haiku never has a moment where it turns to you and says here's the thing my ancestors didn't think of. It's a superb cover band. The musicianship is real, the setlist is safe.
Onboarding and Friction
To its credit, Haiku is approachable in a genre that often mistakes cruelty for craft. The difficulty curve is real but humane. The runtime — generally seen as fair for the price — respects that you have other games. For a player who bounced off Hollow Knight's Path of Pain and concluded the genre wasn't for them, Haiku is the on-ramp. That's a legitimately valuable market position and the game occupies it better than almost anything else on Steam.
The friction is in the bugs and rough edges. Player reports of technical problems track closely with that softened recent review score, and for a solo-developed game of this scope, that's understandable but not excusable. A metroidvania lives on trust — you have to believe the wall is a puzzle and not a glitch. Every bug spends some of that trust.



