Services
We are not a work-for-hire pipeline with a games team bolted on. Every discipline below sits inside the same six-to-eight person studio that runs our own Play catalogue.
Concept to store listing in Unity or Godot. We take the parts other studios outsource — economy design, performance budgets, store assets — and keep them in one team.
Native Kotlin and Compose, or Kotlin Multiplatform when a second platform is a real plan rather than a hope. Offline-first by default.
Closed testing, data safety forms, target API bumps, Play Billing, pre-launch reports, staged rollouts and the policy correspondence nobody enjoys.
Season calendars, offer design, remote config and the analytics to tell whether any of it worked. We prefer economies that survive without dark patterns.
Key art, in-game UI, icon and feature-graphic sets, store video. One art lead across the whole title so the icon and the tutorial look like the same game.
A frame budget agreed up front and tested on a rack of real low-end hardware, not just a flagship and an emulator.
The route to the store
Phase 3 is where we recommend stopping if the slice is not fun. Saying so early is the most valuable thing we do.
Audience, comparable titles, the one thing the game or app must do better than anything else on the store. Ends with a written brief and a budget range.
A build on your phone, not a deck. We test the core loop with real players before anyone writes production code.
One level, one flow, final art quality. This is the go / no-go gate — and the point where scope gets honest.
Content, systems, store assets and compliance in parallel. Playable build every Friday, no exceptions.
Closed and open testing in two or three markets. We read retention and crash-free rates, then fix instead of launching.
Staged rollouts, season content, policy upkeep and a monthly report you can actually read. Most of our titles are still in this phase.
Tooling
We pick engines and services we can still support in five years, and we keep the build pipeline in the repository so a project can be handed to another team without a knowledge transfer meeting.
Straight answers
Yes — roughly half our work is partner projects. We take them on the same process as our own, including the Friday build and the vertical-slice gate. Publishing stays in your Play account under your name.
Discovery is a fixed fee. After that, most original games land between a three-month app build and a twelve-month game build, staffed at four to eight people. You get a budget range at the end of discovery, before production is committed.
Often. We start with a two-week audit of the build, the store listing and the crash data, then tell you honestly whether it is worth continuing or rebuilding. Both answers have happened.
Google Play is where we are genuinely good. We build with Kotlin Multiplatform or Unity so an iOS release stays possible, and we will say so plainly when a project needs a studio that lives on both stores.
Overlapping hours from UTC-10 to UTC+3. Replies within two working days.