Product studio · Hong Kong

We ship apps in
30 days.

We design, build and run mobile and web products — Flutter, Next.js, AI agents. Three of them are our own, live on the App Store, Google Play and the Solana dApp Store with 500,000+ users across 16+ markets. Yours can be next.

We are operators,
not vendors.

Most studios have never shipped a product of their own. We have shipped three — and we still run them every day.

That changes what you get. Our screens have been through App Store review. Our payment flows have taken real money, in card and in crypto. Our retention loops have been tuned against real churn. When we build for you, you are not paying us to learn on your budget.

3apps live in the stores
500k+users across the portfolio
16+markets served
30days idea to launch

Our work

Three apps we designed, built,
shipped and operate.

Not case studies from a portfolio site. Download them. They are ours.

Wibu.ai

AI anime creator economy

Creators build and customise AI anime characters; fans chat, play and form relationships with them. Grown to 250,000+ registered users across 16+ markets on organic reach alone — no paid acquisition.

  • Character creation, persona and memory engine
  • Taste-profile onboarding that tunes the AI agent per user
  • Chat, group chat, quiz and story-mode games
  • 15-level relationship / bond XP system
  • Creator dashboard with transparent revenue share
  • Gems wallet, subscriptions, missions and streaks
FlutterNext.jsMulti-agent chatIn-app purchaseCrypto payments16+ locales
Wibu.ai character library
Wibu.ai chat
Wibu.ai agent preferences
Wibu.ai creator dashboard
Otona.ai

Interactive romance novels

Reading as roleplaying. Readers make choices that shape the emotional texture of a story without breaking the narrative — so quality stays consistent at scale. Multilingual from day one.

  • Multi-agent content pipeline: story, art, localisation
  • Custom reader with typography, pacing and audio controls
  • Chapter unlocks on a dual-currency economy
  • Reader levels, badges, missions and streaks
  • Next.js web app alongside the native app
FlutterNext.js 16Agentic contentStripe + IAPCrypto paymentsDual currency
Otona.ai discovery
Otona.ai continue reading
Otona.ai relationship level system
Otona.ai reader profile and badges
Kimochi.fun

AI companion, matched by an agent

Instead of an endless catalogue, an AI concierge learns your taste and hand-picks a companion for you — then suggests what to say so the conversation never stalls. Every companion is one of a kind and can be claimed exclusively.

  • Agent concierge that curates and explains its matches
  • Voice notes, AI portraits, music and short video in chat
  • Group chat with up to five companions
  • 15 relationship levels with decay if you go quiet
  • 100+ chat languages; gem economy with spend analytics
FlutterAgent orchestrationTTS + image + videoStripe + IAPCrypto payments100+ languages
Kimochi.fun agent recommendations
Kimochi.fun companion profile
Kimochi.fun group chat
Kimochi.fun gem usage
Also on the Solana dApp Store

Three stores.
Every way to pay.

All three of our apps ship to the App Store, Google Play and the Solana dApp Store — the crypto-native store pre-installed on Solana Mobile's Seeker device — from a single Flutter codebase, alongside a Next.js web app.

Card checkout, Apple and Google billing, and on-chain payments all map onto one in-app currency, so the product never forks into two economies. Most clients need the first two. If yours are crypto-native, the third is already built.

Card & walletStripe checkout, saved cards, regional methods, refunds and dunning.
In-app purchaseApple and Google billing, subscriptions, restore and receipt validation.
CryptoWallet connect, on-chain top-ups and token-gated features, mapped onto the same in-app currency as everything else.
Creator payoutsRevenue share, statements and payouts — the side of monetisation most builds forget.
DistributionApp Store, Google Play, the Solana dApp Store and a web app — one codebase, four channels.

What we do

Design, build, launch — then run it.

01

Mobile app design & build

One Flutter codebase, iOS and Android. Product design, UI kit, motion, and a build that survives store review — we have been through it three times.

02

Web apps

Next.js, React, TypeScript, Tailwind. Marketing sites, companion web apps, creator dashboards and admin consoles your team can actually operate.

03

AI agents & LLM systems

Multi-agent pipelines in production: content generation, persona and memory engines, localisation, moderation, recommendation, support.

04

Monetisation & crypto

Subscriptions, in-app purchase, virtual currency, Stripe, wallet connect and on-chain payments, creator revenue share and payouts.

05

Gamification & retention

Missions, XP, levels, badges, streaks, leaderboards, relationship systems. The loops that decide whether anyone is still there in week four.

06

Launch & store readiness

ASO, listings, screenshots, age ratings, AI-content compliance, submission and appeal — App Store, Google Play, the Solana dApp Store and your web app.

07

Localisation at scale

UI and AI-side content across dozens of languages, driven by agents rather than a translation vendor's invoice.

08

Operations

The part nobody else offers: we run the app after launch. Content, community, moderation, support, LiveOps and reporting.

How the 30 days works

Four weeks, four phases,
one app in the store.

Each phase is priced and paid separately, and each one ends with something you can hold. The point is to get a real app in front of real users fast — then let what they do decide what gets built next.

  1. Days 1–7

    Foundations

    Mockups, design system built in code, app skeleton, navigation, auth, platform modules.

    You get: the first build on your phone, in week one.
  2. Days 8–21

    Build

    Your locked backlog, feature by feature, on Flutter and the Gen A modules.

    You get: a demo build every week.
  3. Days 22–27

    Integrate & QA

    Payments, analytics, content loaded, full bug bash.

    You get: a release candidate on TestFlight.
  4. Days 28–30

    Launch

    Store listings, ASO, screenshots, submission, launch checklist.

    You get: your app submitted, live as soon as review clears.

End to end, first call to live app: about five weeks — a few days to agree the brief, 30 days to build it, and a few more for store review.

Why 30 days is real

We are not
starting from zero.

Every module below is already built, shipped and hardened across three live apps.

Your build assembles them and layers your product on top. The four weeks come from that — not from cutting corners, and not from throwing thirty people at it.

Auth & onboardingProfilesWallets & virtual currencySubscriptionsIn-app purchaseStripeWallet connectOn-chain paymentsMissions & XPLevels & badgesStreaksLeaderboardsChat with memoryPersona engineGroup chatAI image genVoice / TTSVideo genSocial feedNotificationsModeration queueCreator dashboardRevenue share & payoutsAdmin consoleAnalyticsCMSi18nStore submission playbook

Build and operate

A lean team, because
agents do the volume.

Most clients can get an app built faster than they can staff the team to run it. We keep a small senior pod on your product and put AI agents underneath it — the same setup that lets us operate three consumer apps at once.

Content

Stories, characters, images, prompts and copy generated at volume, reviewed by a human before it ships.

Localisation

UI strings and AI-side content across dozens of languages, kept in sync as the product changes.

Moderation

First-pass agent review of user content and chat, with clear escalation paths to a person.

Support

Tiered answers drawn from a maintained product wiki, escalating to your team only when it needs to.

Engagement

Retention nudges, mission calendars, re-activation flows and LiveOps events, run on a schedule.

Reporting

Regression sweeps and a daily metrics digest, so you learn about a problem before your users tell you.

Working with us

Fixed price per phase.
Stop whenever you want.

Each of the four phases is quoted as a fixed fee and paid on its own, and each one ends with something you can hold. Carry on when you are happy, stop when you are not — you own everything we have made either way.

No open-ended bills

Every phase is a fixed fee agreed before it starts. Nobody discovers the cost at the end of the month.

You own everything

Repositories, infrastructure and store accounts transfer to you at handover. No lock-in, no licence trap.

One weekly demo

A build on your phone every Friday and a written update. You always know exactly where the project is.

Scope locks in week one

Phase 1 produces the backlog and the price for the rest. Later requests are quoted openly, never absorbed silently.

One decision-maker

You nominate one person who can approve scope and design. It is the single biggest predictor of a project landing on time.

Direct access

You talk to the people building it. No account manager relaying messages to an offshore floor.

After launch
— optional
ScaleA monthly product squad for whatever real usage tells you to build next.
OperateWe run the app — content, localisation, moderation, support, LiveOps — with agents doing the volume.
Neither is required. Decide after you have launched, not before.

Every project is quoted on its scope. Tell us what you are building and you will have a number, and a date, within two working days. Ask for a quote →

Questions

The things clients
always ask first.

Can you really build an app in 30 days?

Yes, for a first version with a scope we have agreed together. It works because we are not starting from scratch — auth, wallets, subscriptions, in-app purchase, missions and XP, chat with memory, moderation, admin console and analytics are already built and hardened across our own three apps. Your build assembles those and layers your product on top. A project that cannot reuse them is a different conversation, and we will tell you that in week one rather than in week four.

What does it cost?

Every project is quoted on its scope, so there is no single number. What we can promise is the shape: four phases, each a fixed fee agreed before it starts, with the price for phases two to four fixed at the end of week one. Send us a paragraph about what you want to build and you will have a real number within two working days.

What do you build with?

Flutter for mobile — one codebase for iOS and Android — and Next.js, React and TypeScript on the web. Postgres and Node on the back end. For AI: multi-provider LLMs, vector memory, image and video generation, text-to-speech, and our own agent orchestration. All of it is running in production in our own apps today, not on a slide.

Do I own the code?

Yes. Repositories, infrastructure and store accounts are transferred into your name at handover, with billing moved across. The reusable platform modules stay ours, licensed to you perpetually for the app we build — you never have to come back to us to keep your product running.

Can you publish to the App Store and Google Play?

We do it as part of the Launch phase — listings, ASO, screenshots, age ratings, privacy labels, AI-content compliance, submission and any review appeals. Our apps are live in 16+ markets on both stores, including categories that get extra scrutiny for AI-generated content, so we have already learned where the rejections come from.

What is the Solana dApp Store, and do I need it?

It is a crypto-native app store that ships pre-installed on Solana Mobile's Seeker device, and it is a fourth distribution channel alongside iOS, Android and web. All three of our own apps ship there. You almost certainly do not need it unless your users already hold a wallet — but if they do, we have done the submission before and it costs you very little extra on top of the same Flutter build.

Can the app take crypto payments?

Yes — wallet connect, on-chain top-ups and token-gated features, mapped onto the same in-app currency and ledger as card and in-app purchase. That last part matters: done badly, crypto payments fork your product into two separate economies that never reconcile.

What does “AI agents in operation” actually mean?

Not a chatbot bolted onto a landing page. In production today, agents generate story, character and image content at volume; keep dozens of languages in sync; run first-pass moderation with human escalation; answer support from a maintained product wiki; drive retention and mission calendars; and run regression sweeps and a daily metrics digest. It is what lets a small senior team operate three consumer apps at once — and it is available to you as a monthly service after launch.

Do you work with clients outside Hong Kong?

Most of our clients are. We work asynchronously with one weekly demo call, and the shared project tracker is updated every Friday so you are never waiting on an email to know where things stand. Reach us on email, Telegram, WhatsApp or WeChat.

What happens after launch?

Thirty days of bug support are included at no charge. After that it is your call: take the code and run it yourself, take a monthly squad to keep building, or have us operate the app for you. We raise that conversation at a retro two weeks after launch — once you have seen what real users actually do — and not before.

Stack

FlutterDartNext.jsReactTypeScriptTailwindNodePostgreSQLStripeApp Store ConnectGoogle PlaySolana dApp StoreWeb deployWallet connectMulti-provider LLMsImage & video generationTTS / voiceVector memoryAgent orchestration

Start a project

Tell us the idea.
We’ll tell you what
30 days buys you.

Send a paragraph about what you want to build and roughly when you need it live. You will get a real answer from someone who has shipped, not a brochure.

Click any handle to copy it. Prefer email? Open your mail app →  ·  Message on Telegram →

EntityGEN A LIMITED, Hong Kong
PlatformsiOS · Android · Web · Solana dApp Store
We replyWithin one working day