A mobile game your players keep coming back to after the first week

Every mobile game starts with a loop: the small set of actions a player repeats, and the reward that makes them repeat it. We prototype that loop first, usually in grey boxes, because a loop that is not fun without art will not be fixed by art. Only after it holds up on a real phone do we commit to the art style, the level count and the economy.

Then comes the technical choice. Most projects ship from a single engine, commonly Unity, so one team can release to iOS and Android together. The client talks to a backend that stores progress, runs leaderboards and checks purchases. Putting that logic on a server matters. If the game trusts the phone, the first modified build will hand out free currency and your economy is gone.

Plan on 8 to 14 weeks from signed scope to a store-ready build for a focused game. Larger worlds, multiplayer and 3D art push that out, and we say so at scoping, not halfway through.

Arabic support is more than translated strings. Text has to flow right to left, menus and progress bars have to mirror correctly, and a word that fits in English can overflow its button in Arabic. We test those screens early, with Arabic fonts, and we ask a native reviewer to check the wording so it reads naturally to a Saudi player rather than like a machine translation.

Payments decide revenue. Store billing runs through Apple and Google, and both platforms control what payment methods a player sees. Where a game sells outside the stores, for example a web top-up, we integrate local methods such as mada and STC Pay through a licensed gateway. Spending behavior also matters: many players prefer small, frequent purchases, so we design price points to match.

Data collected from players is personal data. We design sign-in, analytics and any child-directed features to align with the Personal Data Protection Law, and we keep a plain record of what the game collects and why.

Apple and Google review every release, and the common rejections are avoidable: unclear privacy answers, a wrong age rating, missing account deletion, or a purchase flow that bypasses store billing. We build a submission checklist from each platform's current guidelines and run it before every upload, so the review is a formality rather than a gamble.

We also stage the launch. A soft release to a small audience shows crash rates, load times on cheaper phones and the real day-one retention before you spend on promotion. Fixing those at small scale is cheap. Fixing them after a campaign is not.

After launch you own the source code, the art and the backend. We stay on for fixes and updates under a support plan, and the live-ops and analytics service picks up from here when you want events and seasons.