S-05 / Mobile apps (iOS/Android)Services

Mobile apps (iOS/Android)

iOS and Android, at any complexity you ask for: from a single-screen tool to a product with payments, maps and an offline mode.

Book an audit Message on Telegram ↗

S-05.1Problem

What it looks like today

Our customers live in a Telegram group: 4,000 people, one admin and one phone. “Where is the bus”, “is there a seat at 18:00”, “did my Payme go through” — all of it lands on the same person, every day, Sundays included. We have asked for an app quote twice. Both came back above $20,000 and six months, and nobody could tell us whether people would actually install it.

We do not need an app for its own sake. We need bookings that do not depend on one admin, payments through Payme or Click that we can reconcile in 1C, and a subscription that renews itself. If that works in Telegram first — fine. But we want a path to the App Store and Google Play without rewriting everything a second time.

S-05.2Outcomes

What changes in your business

A Telegram-first MVP with real users in 30 days — bot plus Mini App with Payme/Click, before a single line of native code. This is how the intercity bus product replaced a 4,000-member chat.
One React Native/Expo codebase for iOS and Android on Supabase: one team, one backlog. Target: a fix reaches both stores in the same release, not two months apart.
Subscriptions that renew themselves: Payme/Click, receipt in Telegram, a reminder before expiry and one-tap renewal — no admin chasing payments in the group.
Interfaces and notifications in Uzbek (Latin), Russian and English, written by people and tested with users of all ages. The bus lesson: if a 60-year-old cannot book a seat, the design is wrong.
An admin panel and a live dashboard: bookings, payments, subscribers, no-shows — instead of counting in a chat.
Store publishing, crash monitoring and a runbook. Developer accounts, repository and data are in your company’s name from day one.

S-05.3How it works

Three steps, in this order.

01Step 1
Audit: Telegram or app?
One week. We map the flows — booking, payment, renewal, support — and the unit economics, and decide what has to be native and what can live in Telegram. You get a one-page product brief and a fixed price for the MVP.
02Step 2
Telegram-first MVP in 30 days
Bot and Mini App with Payme/Click, real bookings, real payments, real users from your existing group. We measure what people actually do — bookings per day, renewal rate, support questions — before spending a dollar on native code.
03Step 3
Native app and retainer
When the numbers say yes: one React Native/Expo app for iOS and Android on the same Supabase backend, subscriptions, store publishing, monitoring. Then a monthly retainer for releases, support and the next features — or a clean handover to your team.

S-05.4Deliverables

What you sign off on

Product brief and flow map: booking, payment, renewal, support (one page per flow)
MVP: Telegram bot + Mini App with Payme/Click checkout
React Native/Expo app for iOS and Android, published under your developer accounts
Supabase backend: Postgres schema, row-level security, sign-in by phone or Telegram
Subscription billing: plans, receipts, renewal reminders, failed-payment handling
Admin panel and dashboard: bookings, payments, subscribers, no-shows
Crash and uptime monitoring, release checklist and runbook
Source code, store listings and documentation in your company’s name

S-05.5Price

What it costs.

By agreement

Exact quote after the free 30-minute audit.

S-05.6Proof

We run what we build.

Fact 01
Telegram-first product replacing a 4,000-member chat: bookings and subscriptions before any native app.
Fact 02
Parent portal as a Telegram Mini App on Supabase with Payme/Click — the same backend pattern the apps use.

S-05.7Questions

Questions we get on the first call.

Do we need an app at all, or is Telegram enough?

Usually Telegram first. The intercity bus service ran as a bot and Mini App for a 4,000-member audience before anyone talked about stores. Go native when you need what Telegram cannot do: background location, offline mode, push outside Telegram, an App Store presence for trust, or users who are simply not on Telegram. The audit answers this in a week.

Whose App Store and Google Play accounts does the app ship on?

Yours. We open the developer accounts in your company's name and hand you access on day one — the app ships under your name, not ours. The code sits in your repository, and the push certificates and signing keys stay with you. Even if you move the work to another team, nothing has to be re-published in the stores.

Where is our data stored, and what about the personal-data law?

In a Postgres database (Supabase) that belongs to your project, with row-level security and daily backups. Uzbekistan’s personal-data law requires citizens’ personal data to be stored on servers inside the country, so we collect the minimum and can run the database on a server in Uzbekistan when your lawyer says it must be. Payments never touch our servers — Payme and Click handle card data.

How long does it take, and what happens after the MVP?

Audit: one week. Telegram-first MVP: 30 days to real users. Native app: plan 60–90 days after the MVP, plus one to two weeks of store review. After the MVP you have three honest options: the numbers say go native, the numbers say stay in Telegram and grow there, or the numbers say stop — and you spent a Mini App budget to learn that, not $20,000.

Who owns the code, and can it talk to our 1C?

You do. Apple and Google developer accounts are opened in your company’s name, the repository is transferred at handover, and we keep access only for as long as a retainer runs. 1C, your CRM and Payme/Click reconciliation connect through an integration layer we design with you — see Systems & Integration Design if the back office is the hard part.

S-05.8Next step

Start with the free 30-minute audit.

Five questions, one call. You leave with the workflow to automate first and a cost estimate.