When I started reimplemening this roguelike engine for iOS, I didn’t expect the project to take over my nights and weekends. But like many long-running dev projects, what kept it going wasn’t just technical momentum — it was support from people who cared.
That’s why I named the app Rocco Rogue.
Yes, it sounds like a character name or a punchy indie game title (and I’m fine with that). But the real reason is much simpler: Rocco is one of my best friends, and he played a huge role in helping this project come together.
Reimplemening a roguelike from scratch in Swift was a big undertaking. There were plenty of moments where I hit dead ends — UI frustrations, combat logic bugs, rendering headaches.
Rocco was the person I messaged first when I thought about shelving it. And more than once, he was the one who said:
"You‘ve been doing amazing work!"
Sometimes that’s all you need.
As the app took shape, Rocco gave me constant feedback on UX and game feel — especially from a mobile-first perspective.
Having someone close who isn’t afraid to call out flaws is invaluable when you’re too deep in the code to notice them.
Before the game can play responsively, Rocco was testing it.
He broke saves. He reported bugs I never would’ve found.
That kind of early pressure-testing helped make the core engine way more stable.
Sure, “Rocco Rogue” sounds like a cool adventurer. But it’s really a nod to collaboration.
Plenty of indie devs name projects after code names, aesthetic vibes, or abstract lore. I wanted to name mine after something that actually made the project possible.
It’s a small thank-you, baked into the app name.
Every solo project is secretly built by a small invisible team — the people who encourage you, help you test things, and remind you why you started.
For this one, that was Rocco.
So when the app boots up and you see the name Rocco Rogue, now you know: It’s not just a game name. It’s a credit.
(Also — fun fact: he’s one of the best mime artists I know.) SILENT ROCCO