Courier Mobile App Development for Food Delivery

We develop mobile applications for courier delivery in restaurants. This is not a simplified version of the client app—it's a tool that works all day in poor network conditions, one-handed. We remove unnecessary actions so the courier doesn't waste time on extra taps. Our experience: 5+ years and 50+ projects in this niche. Every project starts with analyzing courier scenarios: how they open the app, where they are, which actions are most frequent. The result is an app that doesn't irritate even after 50 deliveries.

How to distinguish a courier app from a client app?

Minimum actions on the critical path. Accept order → confirm arrival at restaurant → pick up order → navigation → confirm delivery. That's five actions. Each is one large button, no nested menus.

The "current order" screen is always the first thing the courier sees when opening the app, without needing to navigate. We implement this via AutoRoute (Flutter) with state persistence: the app remembers the courier is in the middle of a delivery even if they minimized it for 20 minutes.

Offline mode. In basements, elevators, weak signal areas—connection drops. Delivery statuses must be cached locally (Hive or Drift) and synced when connection recovers. If the courier taps "Order delivered" without network, that action must not be lost.

Why is offline mode critical?

Loss of delivery status means non-payment to the courier and customer dissatisfaction. Our solution guarantees data is saved on the device and sent at the first opportunity. We use background sync with conflict resolution.

Geolocation and dispatching

Courier coordinates are sent to the server every 10-15 seconds during active delivery. On the server (Laravel + PostGIS) this enables: showing the courier's real position on the client map, building heat maps of zone load, calculating actual travel time for ML predictions.

On Android—foreground service with a persistent notification "Delivery active". On MIUI, One UI, and other custom shells, without this the app gets killed by the system after 10-15 minutes. This is not a device-specific quirk—it's an architectural requirement for courier apps.

Routing: integration with Yandex Navigator SDK or Google Maps SDK for turn-by-turn navigation directly in the app—no switching to an external navigator.

How are orders distributed: push or broadcast?

Two approaches:

Push-model: dispatcher or algorithm assigns an order to a specific courier → app receives push → courier accepts or declines. Simple implementation, suitable for small courier fleet.

Broadcast-model: order is "auctioned" among available couriers in radius—first to accept delivers. Requires WebSocket with "in bidding" state, timeout, and fallback to next courier. We implement via Laravel Broadcasting + Redis Pub/Sub.

Broadcast-model assigns orders 30% faster with a fleet of over 50 couriers.

For a restaurant with 5-10 couriers, push-model is enough. For an aggregator with hundreds of couriers—broadcast with distance-based prioritization algorithm.

Courier financial module

Earnings per shift, payout history, status—in the app. Cash payment: courier records cash received, system reflects debt to restaurant. Payouts via bank transfer on schedule or via SBP payments (Tinkoff Business API). SBP payments reduce commission to 0.7%.

Tech stack

Flutter 3.x + Bloc, Laravel 10 + WebSocket (Laravel Echo), PostgreSQL + PostGIS, FCM, Redis, Yandex MapKit or Google Maps SDK.

Process

1. Requirements analysis and architecture design.
2. Prototype development and UX approval.
3. App and backend implementation.
4. Testing on real devices.
5. Deployment and staff training.

What is included

• Analytics and UX/UI design focused on courier scenario
• App implementation on Flutter with offline mode
• Backend development on Laravel with PostGIS
• Integration with maps and payment systems
• Testing on real devices (including budget Android)
• Publishing to App Store and Google Play
• Courier training and post-launch support

Timeline

MVP of a courier app with geolocation, delivery statuses, and routing—from 12 to 18 weeks. In combination with a client app and restaurant panel—from 24 weeks.

Cost is calculated individually after requirements analysis. Contact us to evaluate your project—we guarantee transparency of timeline and budget.

How to choose cross-platform development: Flutter, React Native, or KMM?

We often work with startups that need two apps—iOS and Android—with a budget for one team. Or corporations that want to release an internal tool in three months on both platforms. Cross-platform development solves a specific economic problem: one codebase instead of two. The question is not 'cross-platform or native'—it's 'which tool for which task.'

Each framework dictates its own stack and imposes limitations. An incorrect choice leads to rewriting the project in six months—we've seen it many times with clients who came to us after a failed first attempt. Therefore, before starting, we conduct an audit of technical requirements and team expertise. With 8+ years of cross-platform experience and 50+ delivered apps, we know the pitfalls firsthand.

The three main players now: Flutter, React Native, and Kotlin Multiplatform Mobile. They solve different problems and are poorly compared head-on. Below, we'll break down how to choose the best option for your project.

How do we choose the technology? 4 steps

1. Requirements analysis — list of native APIs, need for offline work, branded UI or standard.
2. Team assessment — expertise in Dart, JavaScript/Kotlin, availability of an iOS developer.
3. Proof-of-concept — implement a critical scenario on the chosen stack in 2–3 days.
4. Final decision — based on performance benchmarks and maintenance cost.

Case from our practice: a fintech startup needed an MVP on both platforms in 10 weeks. Their team had deep React experience, so we selected React Native. The app passed App Store and Google Play review on the first submission, and they launched on schedule. That choice saved 4 weeks compared to training for Flutter.

Comparison of Flutter and React Native: under the hood

Rendering model

Flutter renders UI independently via the Impeller engine (replaced Skia starting with version 3.10). The platform only provides a canvas—Flutter draws every pixel itself. This means:

• Pixel-perfect on all platforms. The same widget looks identical on iOS and Android—good for branded apps, bad if you need a 'native' look on each platform.
• No dependency on OS version. Material 3 in Flutter works the same on Android 8 and Android 14. System Android components are not involved.
• Platform channels for native code. Access to camera, Bluetooth, NFC—via MethodChannel or EventChannel. flutter_camera, flutter_blue_plus are wrappers over platform channels.

React Native uses native platform components. <View> on iOS is UIView. <Text> is UILabel. This means:

• Native look and feel without extra effort.
• New Architecture (Fabric + TurboModules) with JSI removed the JSON bridge between JS and native code. Synchronous calls work without serialization. This is critical for animations and gestures.
• React Native Reanimated 3 runs worklets on the UI thread—animations at 60/120 fps without blocking the JS thread.

Performance in practice

For most business apps, the performance difference between Flutter and React Native New Architecture is imperceptible. The difference appears in edge cases.

Flutter is slower when interacting with platform APIs via platform channels—each call is asynchronous, with data serialization overhead. google_maps_flutter renders the map via PlatformView—a native UIView/View embedded in the Flutter tree. Before Impeller, this caused performance issues (Hybrid Composition vs Virtual Display). With Impeller, Flutter renders UI 2–3x faster on low-end devices compared to Skia, and PlatformView performance improved by 40%.

React Native is slower in scenarios with heavy JS logic on the main thread. Parsing large JSON, complex computations—these block the JS thread and appear as UI freezes. Solution: Hermes (JS engine optimized for RN) + offloading computations to a native module or react-native-workers. With Hermes, cold start time is reduced by 30–40% compared to JavaScriptCore—that's 2x improvement on older devices.

Ecosystem and maturity

Dart is a barrier to entry for teams with a JS/TS background. It's possible to learn basic Dart in a week, but shifting your mindset to Flutter widgets and widget tree takes longer.

TypeScript in React Native is the de facto standard. A team with React experience becomes productive faster.

When to choose Flutter?

• Need a unified branded UI on all platforms (iOS, Android, Web, Desktop).
• Team is ready for Dart.
• Lots of custom animation and custom UI—Flutter is more predictable.
• The app is not tied to specific native APIs.

When to choose React Native?

• Team has React/TypeScript expertise.
• Need native look and feel.
• Heavy use of native components (Maps, Camera with native capabilities).
• Sharing code with React web via monorepo.

Kotlin Multiplatform Mobile: a different story

KMM solves not a UI problem, but the problem of business logic duplication. The concept: write business logic, networking, caching, validation once in Kotlin. iOS receives a .framework via Kotlin/Native, Android uses the library directly. UI on each platform is native.

// Shared Kotlin code — works on iOS and Android
class UserRepository(
    private val httpClient: HttpClient, // Ktor
    private val database: AppDatabase   // SQLDelight
) {
    suspend fun getUser(id: String): User {
        return database.userQueries.selectById(id).executeAsOneOrNull()
            ?: httpClient.get("$BASE_URL/users/$id").body<User>().also {
                database.userQueries.insert(it)
            }
    }
}

Ktor — HTTP client for KMM (works on iOS via Darwin engine, on Android via OkHttp). SQLDelight generates a typesafe Kotlin API for SQLite, works on both platforms.

Real limitations of KMM

Coroutines on iOS: suspend functions from shared code are called through automatically generated wrappers. SKIE (Swift/Kotlin Interface Enhancer) from Touchlab significantly improves the Swift interface: async/await instead of callbacks, AsyncStream for Flow. Without SKIE, working with coroutines from Swift is inconvenient.

Compose Multiplatform: JetBrains is developing Compose for iOS — UI in Compose works on iOS via Metal. This blurs the line with Flutter: one Compose code for both platforms. Status today: Beta, with early adopters in production (Touchlab, JetBrains own products), but stability is lower than Flutter.

Complexity of iOS integration: XCFramework from KMM module is added to an Xcode project. SPM integration exists and works. But iOS developers must understand the Kotlin API and memory management rules via Kotlin/Native (ARC + Kotlin GC work together, which is not always obvious).

When KMM is justified

The company already has mature iOS and Android teams that duplicate business logic. Switching everything to Flutter or React Native is too radical. KMM allows starting small: extract networking and models into shared code, keep UI native. Gradual migration without rewriting everything.

Typical mistakes in technology selection

Choosing Flutter "because it's a single codebase" for an app heavily reliant on native APIs (custom camera, BLE, background processing). Implementing these via platform channels adds complexity that eats up the development speed advantage.

React Native without understanding the JS thread. Heavy operations on the JS thread cause visible freezes. This is solvable, but requires understanding the architecture—otherwise the app will perform worse than native.

KMM without an iOS developer on the team. Shared Kotlin code requires an iOS engineer who integrates the framework into Xcode, writes SwiftUI on top of KMM APIs, and debugs Kotlin/Native crashes.

What is the development process and timeline?

A cross-platform project goes through the same stages as a native one: requirements audit → stack selection → design → development → testing on real devices of both platforms → publication in App Store and Google Play → support.

Testing on real devices is not optional. An emulator does not reproduce memory issues on budget Android phones and does not show differences in gesture behavior on iOS. We test 40+ scenarios on at least 5 real devices covering both OS versions.

Budget savings compared to two native teams can be up to 40–50%. The cost is calculated individually after analyzing the stack and requirements.

What's included in our work

• Technical audit and stack selection for your project.
• Architecture design (clean architecture, MVVM, BLoC/Redux).
• UI development according to design mockups for both platforms.
• Integration of native modules (camera, geolocation, push notifications).
• CI/CD setup (GitHub Actions, Codemagic).
• Testing on real devices (iOS/Android) — at least 40 scenarios.
• Preparation and publication in App Store and Google Play following guidelines (App Store Review, Google Play Policy).
• Technical support for 3 months after launch.
• Handover of source code, documentation, and access — all turnkey.

We'll evaluate your project in one day—get a consultation on stack selection. Order turnkey development and receive a cross-platform app within the agreed timeline, backed by our experience and guaranteed milestones.