How We Work

The principle Decide the scope first, then write the code

Most mobile projects fail on scope, not on technology. Features get added mid-flight, the deadline moves, the budget follows it, and nobody can point to the moment it went wrong.

So we spend real time at the start defining the required functionality, the user journey, the project scope and the technical requirements. It is the least glamorous part of the project and the one that decides whether it lands.

Written scope
Build every 2 weeks
One point of contact

Mobile game production workflow from concept art to playable build

Step by step From the first call to long-term support

forum

Discovery Call

A conversation about the business problem, the audience and the deadline. No documents required from you at this stage — we ask the questions.

outbox You receive: Written summary and a rough feasibility answer within two working days.

fact_check

Scoping and Estimate

We define the required functionality, the user journey, the project scope and the technical requirements before any development begins.

outbox You receive: Feature list, scope boundaries, timeline and a fixed estimate.

design_services

Design and Prototype

User journeys, wireframes and a clickable prototype. For games, a playable core loop you can hold in your hand and judge honestly.

outbox You receive: Clickable prototype or playable build, plus the design system.

code

Production Sprints

Two-week sprints with a build at the end of each one. You see progress on a real device, not in a status report.

outbox You receive: Installable build every two weeks and a written sprint summary.

bug_report

QA and Device Testing

Functional, regression and performance testing on a real device matrix, with particular attention to low-end Android hardware.

outbox You receive: Test report, device coverage matrix and a fixed defect list.

rocket_launch

Launch and Store Release

Store listings, creatives, submission, review responses and a staged rollout so problems are caught before everyone sees them.

outbox You receive: Published application, store assets and release documentation.

monitoring

Measure and Tune

The first weeks after release decide the product. We watch the funnels, fix what the data exposes and tune the balance.

outbox You receive: Post-launch report with retention, funnel and stability figures.

engineering

Maintenance and Support

OS updates, store policy changes, crash response and small improvements on a predictable monthly schedule.

outbox You receive: Monthly maintenance report and an agreed response window.

Working together What it is like day to day

person_pin

One Point of Contact

A project lead who knows your product and can answer without checking with three people first.

dashboard

An Open Board

You can see every task, its status and who is on it, at any hour, without asking anyone.

calendar_month

Two-Week Sprints

Each sprint ends with an installable build and a short written summary of what changed and what is next.

currency_exchange

Costs Before Work

When something genuinely changes, you get the schedule and cost implication in writing before anyone starts.

inventory

Everything Handed Over

Code, art sources, documentation and store accounts stay yours throughout, not at the end as a favour.

schedule

Predictable Hours

We work within agreed hours and respond within one working day. Emergencies have an agreed definition.

Quality Tested on the devices your players actually own

Most of the mobile market is not running a flagship. We profile on real mid-range and budget hardware throughout production, not in the week before release.

Discuss Your Project

Functional, regression and soak testing on every release candidate
A device matrix that includes low-end Android, not only the newest iPhone
Frame time, memory, battery and build-size budgets agreed up front
Crash and ANR monitoring wired in before the first external build
Staged rollout so a problem reaches 1% of users, not 100%
Store review preparation, including the rejections nobody warns you about

FAQ Questions we get before signing

It depends entirely on scope, and we will not pretend otherwise. A focused MVP usually lands in a different bracket than a mid-core game with a live back end. After the discovery call and scoping session you receive a written estimate with a fixed price for a fixed scope, so you can make the decision with real numbers.

A hyper-casual prototype can be playable in weeks. A casual title with a meta layer is typically four to nine months. Mid-core games with servers, PvP and live operations run from nine to twelve months. Scoping gives you a realistic timeline before you commit.

Both. A large share of our work is improving, rebuilding or taking over an existing mobile product. We start with a technical audit so you know what is worth keeping before any work begins.

You do. Source code, project files, art sources and documentation belong to you from the first commit, and store accounts stay in your name. Handover documentation is part of every delivery.

Unity and Godot for games, Flutter and React Native for cross-platform applications, Swift and Kotlin when native is the right call. The choice is made during scoping based on your product, not our preferences.

Yes, and it is more common than people expect. We begin with a code and asset audit, give you an honest assessment of the state of the project, and propose either continuation or a targeted rebuild of the parts that need it.

More questions are answered on the contact page.

Start with a scoping call

A short conversation about the problem, the audience and the deadline. No documents required from you.

Your name * Please enter your name.

E-mail * Please enter a valid email address.

Company

Subject

Budget range

Timeline

How can we help? * Please add a few details about your project.

We reply within one working day.