Do you publish in our accounts or yours?

Yours. Developer accounts, repositories and infrastructure are in your name from the start, so there is no handover and no lock-in.

How long until the first build on my phone?

A TestFlight or internal-track build goes out every week from the first week of development. The first store release is usually 10 weeks after the scope call.

What happens after launch?

Crash monitoring, OS and store-policy updates, and new features on a monthly plan. Or a clean handover to your team with docs and a walkthrough.

Service 02 · iOS and Android · React Native

Mobile apps that make it to the store.

From a scope call to a listing on the App Store and Google Play. One React Native codebase, native modules where they matter, and a team that has shipped its own apps through the same review queue.

Get an estimate What's included ↓

Shipped with this service2026

01AlarmyxiOSLive 02DocseeiOSLive

03Your app—○ Next

01 — What's included

Everything between the idea and the listing.

You can take the whole chain or hand us the part that is stuck.

01Scope and estimateA written scope, screen list and estimate after one call. You can take it to another team; it stays useful.5 days

02UX and UI designFlows, a clickable prototype and final screens for both platforms, designed by the people who will build them.Figma

03React Native buildOne TypeScript codebase for iOS and Android. Native Swift or Kotlin modules where the platform demands it: audio, background tasks, widgets.React Native · TS

04Back-end and APIAccounts, sync, push, payments and the admin panel behind them. Or integration with the back-end you already run.Node.js · PostgreSQL

05Store releaseListings, screenshots, privacy labels, review answers. In your developer accounts, so the apps are yours from day one.App Store · Google Play

06Support and updatesCrash monitoring, OS updates, new features on a monthly plan. We run our own apps the same way.Monthly

02 — Why React Native

Two stores, one codebase, native where it counts.

For most products, React Native gets you to both stores for the cost of one app and keeps one team responsible for the whole thing.

Where the platform matters, we write the native part: background audio and alarms, widgets, camera pipelines. Alarmyx rings from a locked phone because of a native module, not in spite of React Native.

If your app is a camera, a game or a 3D tool, we will say so on the first call and recommend fully native.

Core

React Native, TypeScript, Expo where it fits

Native

Swift and Kotlin modules, widgets, background tasks

Services

Push, in-app purchases, analytics, crash reporting

Quality

Device lab, TestFlight and internal tracks before every release

03 — How it runs

What you get, week by week.

Week 1

Scope

You get: screen list, written scope, estimate, a dated plan.

Weeks 2–3

Design

You get: a clickable prototype to test with real users before a line of code.

Weeks 4–10

Build

You get: a TestFlight build every week, a demo call, the code in your repositories.

Launch

Release

You get: both listings live, monitoring on, handover docs, a support plan.

04 — Pricing

Fixed scope

For an app with a defined screen list. Price and date in writing; changes estimated separately.

Dedicated team

For a product that keeps evolving. A senior engineer and a designer on your board, monthly, cancel with 2 weeks' notice.

05 — Questions

About mobile projects.

React Native for most products: one codebase, both stores, one team. Fully native when the app is a camera, a game or a 3D tool. We tell you which on the first call, and we have built both.

Get an estimate

Send us the idea. We send back a plan.

A paragraph is enough. You get a written scope and an estimate after one call, whether or not you go on with us.

Get an estimate See the Alarmyx case →