Huahine Interactive · Fare, Huahine · French Polynesia
HUAHINE is a small studio on an island in the Pacific. We design, build, publish and keep running our own titles on Google Play — and take partner projects through the same process, from a playable prototype to a staged rollout.
across six live titles
446K ratings, Sept 2026
four games, two apps
nine localisations
Titles we own and run
We do not ship and walk away. Every title below is on Google Play right now, getting staged rollouts from the same people who built it.
All six titlesWhat we do
Concept, code, art, economy, compliance and the live service afterwards. The list below is the full set — nothing here gets handed to a vendor halfway through.
How we workConcept 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.
How a title gets made
Every project runs the same route. The vertical slice is a real go / no-go — plenty of good ideas have ended there, which is the point.
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.
How we hold the line
From week three of any project there is something installable on your phone. Progress you can hold beats progress in a status document.
We agree a frame and memory budget before production and test it on hardware people actually own. Flagship performance is a side effect.
We will design a season pass. We will not design a countdown that exists purely to make a child panic. It has cost us work and we are keeping the rule.
Six to eight people who each own a discipline end to end. Nothing gets handed to a vendor at the point where it stops being fun.
They shipped the vertical slice a week early and then spent that week telling us which third of our design to cut. That conversation saved the project.
We came for the Play compliance work and stayed for the LiveOps. Crash-free sessions went from 97.1% to 99.4% in the first two releases they ran.
Next opening
Tell us what you are building. You will get a straight answer about whether we are the right studio for it — and if we are not, a suggestion of who might be.
