Mobile apps (iOS/Android)

Customers come back with one tap from their home screen instead of searching for you again. iOS and Android, at any complexity you ask for: from a single-screen tool to a product with payments, maps and an offline mode.

← All services

Who it is for

Intercity transport and bus operators whose customers live in a Telegram group
Service businesses with bookings: clinics, salons, repair, tutoring — anyone losing clients to missed calls
Marketplaces and delivery services that have outgrown a bot and a spreadsheet
Subscription products: parking, water delivery, gyms, online lessons — anything billed monthly
Founders who were quoted a large budget and six months for an app and want a cheaper way to find out whether anyone will use it

Problem

Our customers live in a Telegram group: 4,000 people, one admin and one phone.

Your Telegram

✓ 18:30 · arrived

A regular customer is back, one tap from the home screen.

What it looks like today

“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 with a large budget and six months of work, and we still had no way of knowing 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 with our accounting program, 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.

What changes in your business

A Telegram-first MVP with real users — 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 codebase for iOS and Android: 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.

Three steps, in this order.

Step 1
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.
Step 2
Telegram-first MVP
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.
Step 3
Native app
When the numbers say yes: one app for iOS and Android on the same backend as the MVP, subscriptions, store publishing, monitoring. Then releases, support and the next features at an agreed rate — or a clean handover to your team.

What you sign off on

A process map and a module breakdown: what gets built, and in what order
The mobile app itself, for iOS and Android
Integrations with the systems you already use, as far as those systems allow
Documentation and user instructions in plain language
Training for each role on your team

The price depends on the type of application: web, desktop or mobile.

Less than the problem costs you — or we tell you straight.

By agreement

We count what this costs you now — hours, missed customers, errors. The quote comes after, set against that number. The final price is agreed individually with each client.

Questions we get in the first chat.

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. Write to us on Telegram and we answer this within 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 database 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?

The review takes one week. We name the MVP and native-app timelines after it, once we have seen your flows; store review adds one to two weeks. 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 the budget of a full app.

We already use an accounting program. Can you work with it?

Yes. If you already use an accounting program or any other specialised software, we can integrate the app with it, provided that system allows integration. Data is then entered once and lands where it is needed.

Contact us.

Describe one process that eats your team's time. We'll tell you what to start with — and what the manual work costs you now.