We sat down with Petra Vanhoof, founder of a mid-sized mobile studio that has shipped four platform games in the past six years, to talk about what businesses actually face when commissioning or building this type of project.
Where do most budgets go wrong early on?
Platform games look simple from the outside. But the physics alone, getting a character to feel right when jumping between tiles, takes weeks of iteration. Most clients come in expecting it to be cheaper than a 3D game. It rarely is.
Petra says her studio always runs a two-week prototype phase before any full contract is signed. The purpose is not to show off visuals. It is to expose where the controls feel off on specific devices, because Android fragmentation alone can push QA costs up significantly.
We tested one title across 60 Android devices. Eleven of them had input lag issues that did not show up on emulators at all.
Engine selection as a business decision
Unity still dominates for mobile platform games, but Godot is catching up for smaller scopes. The real question is not which engine is better technically. It is which one your maintenance team can support after launch.
Petra recommends that any business commissioning a mobile game negotiate source access or at least ask for documented architecture before delivery. Updates to iOS or Android policies have broken live games before, and having a vendor disappear is a real scenario.
Monetization tied to platform mechanics
The monetization model should be decided before level design starts, not after. If you are planning an ad-supported model, levels need natural pause points. If it is premium, the difficulty curve needs to justify the price upfront.
Getting that order reversed is one of the most common and expensive mistakes Petra sees in client projects.