MatchinGo

MatchinGo approached iMobdev with a simple, addictive idea and a rough mascot sketch: a tile-matching game built around an unmistakable angry-eyed character, playable across several visual worlds instead of just one board. Before development started, there was no engine, no economy, and no sense of how the same core mechanic could be reskinned into Shapes, Animals, and Fruits without building three separate games.

The pain points were concrete. There was no shared matching engine that could swap art themes without duplicating game logic, which meant every new theme risked doubling the build and QA effort. There was no monetization layer — no soft currency, no premium gems, no booster shop — so there was nothing to convert engaged players into revenue. And with no timer, freeze, or streak system in place, sessions had no sense of urgency to keep players coming back for another round.

Every month spent without a shippable build was a month of lost visibility in an extremely crowded casual-puzzle category, where day-one polish and a recognizable mascot are what separate a game that gets installed from one that gets ignored.

Technically, the game also had to run smoothly on low-end Android hardware as well as modern iOS devices from a single codebase, ruling out separate native builds for each platform.

MatchinGo launched with three fully playable themes sharing one lightweight engine, a working currency and booster economy, and a consistent mascot identity that carries across every screen, from the main menu to the pause overlay. The shared-engine approach meant new themes could be added as art reskins rather than full rebuilds, keeping future content cheap to produce.

The booster and rewarded-video system gave MatchinGo a real monetization funnel from day one, and the friends list laid the groundwork for social competition and retention. iMobdev continues to support MatchinGo as it adds new themes and refines its live-ops economy.