§ 03 / Mobile

Building mobile apps for iOS and Android.

Apps people don't delete after the third launch. React Native — when you need speed and one codebase across both platforms. Native (Swift and Kotlin) — when performance, AR/VR, deep system integrations or specialty hardware matter.

§ 03.1 What we build

→ MVP

Mobile MVP

The first public version for testing hypotheses. Auth, the key flow, payments, push, baseline analytics. 4–6 weeks to the store.

→ B2C

Consumer apps

Delivery, services, marketplaces, lifestyle. Geolocation, maps, queues, in-app chat, ratings, reviews, referral programs.

→ B2B

Enterprise apps

For field staff: invoices, photo reports, barcode scanning, offline mode, integration with 1C, CRM, ERP.

→ Native

Swift / Kotlin

When you need maximum performance: video, AR camera, Bluetooth peripherals, CarPlay / Android Auto, HealthKit.

→ Release

Store submission

App Store Connect and Google Play Console setup, icons, screenshots, descriptions, handling rejections, updates.

→ RuStore

RuStore and alternative channels

RuStore, AppGallery, APK distribution via your own page, OTA updates. Relevant for clients in Russia.

§ 03.2 How we pick the platform

React Native / Expo — when the app is mostly forms, lists, chats, maps and CRUD. Development is 1.5–2× faster, one codebase.

Native (Swift + Kotlin) — when you need a seamless native UX, deep camera / sensor work, iOS / Android SDK integrations, real-time video. Or when the app is the core of your business and saved dev time doesn't justify the trade-offs.

Flutter / Ionic / Cordova — we don't do these. Not on principle — we just don't think they're the best fit for how we work.

§ 03.3 What's included

User-flow design: what the user does in the first 30 seconds, week, month.
Design in Figma (or working with your designer).
Development and testing on real devices.
Payments integration: Apple Pay / Google Pay, YooKassa, Stripe, Telegram Payments.
Push notifications, email, deep links, onboarding, A/B tests.
Analytics: Firebase, Appsflyer, AppMetrica, PostHog.
Crash monitoring: Sentry, Firebase Crashlytics.
Store submission, help with handling rejections.
CI/CD: builds, automated tests, auto-publish to TestFlight / Internal Testing.

§ 03.4 Timeline

MVP (one platform)

4–6 weeks

React Native, one key flow, auth, payments, analytics. Submission to a single store.

App for both platforms

6–10 weeks

iOS + Android, multiple flows, backend integrations, maps, notifications, both stores.

Native Swift + Kotlin

8+ weeks

When native UX or deep hardware integration is critical. Two codebases — essentially two developers' worth of work in one head.

Pricing is always custom — it depends on platforms, flow complexity and SDK integrations. We'll quote on the first call.

§ 03.5 FAQ

React Native or native — which is better?

Depends on the task. For 70% of apps, React Native saves budget and time without a noticeable quality hit. If the app is the core of your business and people will use it daily — native is the safer bet.

What if the app gets rejected by store moderation?

It happens — when store guidelines are missed. We put it in the contract: passing moderation is our risk, post-rejection fixes are included in the price.

Do we need our own developer accounts?

Yes — we need your App Store Connect and Google Play Console accounts. The app must be owned by your company. We'll help you register if you don't have them yet.

What about post-launch support?

Included: 30 days of bug fixes after release. Beyond that — on demand: hourly work, a proper retainer, or handover to another developer.

§ — Write to us

Tell us about
the app.

hi@weiss.help ↗

or via Telegram · phone

First 20-minute call — free. Quote within 24 hours.