Skip to content

Services

Mobile apps

iOS and Android from one codebase — or a PWA when no store is needed.

Cross-platform by default: one React Native codebase covers both platforms and shares code with the web. Native modules go in where the task genuinely hits the platform — background location, peripherals, permission-specific behaviour. The third option gets said out loud because it is often the right one: if the app is only for your own customers and never has to pass store review, a PWA is cheaper and updates the moment you deploy.

What the work covers

  • A React Native app covering iOS and Android from one codebase
  • PWA: home-screen install, offline mode, push where the platform allows it
  • Release builds and signing, CI setup, store submission to App Store and Google Play under your own developer accounts — the app stays yours after the engagement ends
  • Integration with your backend — or building the API for the app if there is no backend yet
  • Offline storage and sync: the app keeps working underground and in a warehouse
  • Every screen state: loading, empty, error, offline — not only the happy path

Who this fits

  • A fit: the scenario repeats — the app gets opened regularly, not once a year before a holiday
  • A fit: you need camera, location, offline, push — the things the web gives you badly or not at all
  • A fit: a web product already exists and part of its logic and API can be reused instead of built twice
  • Not a fit: an app that is a second website — the same content in a wrapper. App Store review objects to exactly that under Guideline 4.2 (minimum functionality)
  • Not a fit: the budget covers one platform but you need both — starting with a PWA and returning to the stores later is the honest route
  • Not a fit: the launch date is tied to an event. Release goes through store review, whose timing is not mine to control

Stack

  • React Native
  • Expo
  • TypeScript
  • SQLite
  • Fastlane
  • Next.js

What moves the price

  • One platform or both, and how strictly each platform's guidelines must be honoured rather than showing the same screen twice
  • Offline: whether the app merely caches data or has to resolve sync conflicts
  • Whether an API already exists. With no backend, it becomes a separate — and usually larger — part of the estimate
  • Push, in-app payments, maps, biometrics: each subsystem is priced on its own
  • Design: you supply the mockups, or screens are designed from scratch, including states and both platforms' conventions
  • Store preparation: privacy policy, data-collection declaration, age rating, screenshots

What you keep

  • Sources in your repository; signing certificates and keys on your own Apple and Google accounts
  • CI configured so a release build runs without me
  • Builds in TestFlight and the Google Play internal track before any user sees the app
  • Store listing material: description, screenshots, data-collection declaration, privacy policy
  • A written list of what the next major iOS or Android release will break, and what to do about it

Packages

Signal

Mobile

A React Native mobile app: one codebase, two platforms.

from $30,000

Timeline
from 10 weeks
Payment by stage
40 / 40 / 20

Included

  • iOS and Android from one codebase
  • Push notifications, and offline support on the screens that need it
  • Builds and store submission to App Store and Google Play, under your own developer accounts
  • Integration with your API, or a backend written for the app
  • Crash diagnostics that collect no personal data

Not included

  • Separate native projects in Swift and Kotlin
  • Annual developer-account fees for the stores
  • Games and real-time 3D
  • App marketing and ASO
Discuss this package

Retainer

Ongoing

Ongoing support: a block of hours every month and an agreed response window.

from $2,000/mo

Timeline
minimum 3 months

Included

  • Twenty hours a month for fixes and development
  • Incident response within two working hours — weekdays, 10:00 to 19:00 Moscow time
  • Dependency updates and triage of new vulnerabilities
  • Backups watched, and restores tested
  • A monthly report: what was done and where the hours went

Not included

  • Rolling unused hours into the next month — the fee reserves capacity rather than buying a pack of hours; for one-off work there is Hour
  • Round-the-clock on-call
  • A new product from scratch — that is a project of its own
  • Hosting, licences and third-party services
Discuss this package

Indicative pricing. Nothing on this page constitutes a binding offer.

Prices are in US dollars. The Russian site carries a separate rouble price list: a list in its own right, not a conversion at today's rate.

Timelines are indicative: they count the studio's working time and depend on scope, on how fast approvals come back, and on your data being ready. The binding date is set in the contract once the brief is understood.

Tax regime: sole proprietor on НПД. No VAT; every payment is receipted.

Payment: bank transfer or card. Settlement details are issued with the invoice.

This is not a public offer