Nearly three
decades of
simplifying.

"I submitted my first game at 2am, went to bed, and woke up at 7am to an email from my ISP. Account suspended — excessive bandwidth. The game had hit the top of the charts while I slept."

That was 2008. It wasn't planned, it wasn't a business strategy — it was a developer who made something and released it into the world. The response was immediate and overwhelming. By morning, myBad Studios existed in everything but name.

The mission that hasn't changed

The way my brain works is analytical. Any complex problem breaks down into clear steps, each one simpler than it first appeared. The challenge — and the satisfaction — is finding that path and then packaging it so completely that anyone else can follow it without ever having to retrace the thinking.

Drag a prefab into your Unity scene. Set a URL field to point at your WordPress site. Press play. Your players are now logging in, saving data, checking leaderboards — all through a database you control, with no backend code written. That's not simplification as a feature. That's simplification as a philosophy.

From Unity to Unreal to iOS

Over a decade was spent in Unity. The WordPress for Gaming plugin suite grew from a single login component into a full cloud platform for game developers — cloud saves, achievements, leaderboards, virtual currency, cross-game data sharing, all through a WordPress installation the developer already owned.

When the pivot to Unreal Engine began, the same philosophy followed. And when a cousin needed a way to manage staff attendance across seven remote farm sites, MBS Attendance was born — PAYE, UIF, facial recognition, NFC badges, offline sync and all.

The products are wildly different. The thinking behind them never is.