Mobile App Development for Dry Cleaning / Laundry Services

Imagine: a customer drops off a shirt for dry cleaning, and two hours later can't find out if it's ready. Calling the call center—busy, the administrator is on lunch. Such order losses amount to 20–30%. Companies that implement a mobile app see repeat orders increase by 30–40% and call center load decrease. We've built dozens of such solutions—from local laundries to chains with dozens of locations. Let's break down the technical part.

Why do customers lose orders without an app?

The main pain is chaos in order statuses. Without automation, customers don't know where their items are, and administrators spend hours on phone clarifications. We build a clear status machine: new → picked up by courier → under assessment → in progress → ready → being delivered → handed over. Each transition triggers push notifications via FCM/APNs and updates in real time (WebSocket or Firebase Realtime Database). The customer receives a photo of items upon pickup and an assessment report—transparency that builds trust.

The second common problem is inconvenient booking and slots. Without a calendar, couriers arrive haphazardly, increasing wait times. We implement a smart calendar with available time slots, geolocation for delivery zone calculation, and route planning (MapKit/Google Maps SDK). If you have your own fleet, real-time tracking—like in food delivery apps—reduces customer wait time by 15–20%.

What's included in the work

Each project starts with a business process audit. We provide:

• documentation with status and trigger schemas
• integration plan with your CRM (REST API, WebSocket)
• UI mockups (Figma) for iOS and Android
• a finished product with admin panel and database
• instructions for publishing on App Store and Google Play
• employee training and 3 months of warranty support

How we choose the stack and implement the status machine

For most projects, we choose cross-platform: React Native (TypeScript) or Flutter 3.x (Dart). Backend—Laravel or Node.js with REST API. Database—PostgreSQL or MySQL. Here's a typical implementation of the "order—confirmation" process using Flutter:

// Example of a status machine using Bloc
class OrderStatusCubit extends Cubit<OrderStatusState> {
  final OrderRepository repository;

  OrderStatusCubit(this.repository) : super(OrderStatusInitial());

  Future<void> advanceStatus(String orderId, OrderStatus newStatus) async {
    try {
      await repository.updateStatus(orderId, newStatus);
      emit(OrderStatusUpdated(newStatus));
      // Send push via FCM
      await FirebaseMessaging.instance.sendMessage(...);
    } catch (e) {
      emit(OrderStatusError('Error updating status: $e'));
    }
  }
}

We use BaaS (Firebase, Supabase) for rapid prototyping, but in production we prefer a custom backend—it gives full control over logic and security.

Why cross-platform is the best choice for dry cleaning

Native development for iOS and Android requires two teams and stretches timelines by 1.5–2 times. React Native and Flutter allow covering 95% of functionality with one codebase, saving budget without sacrificing performance. For example, complex status transition animations or smooth scrolling of the service catalog—all doable without lags. The cross-platform approach enables launching the app 1.5–2 times faster than native development.

How is CRM integration done?

We provide integration via REST API or WebSocket. During analysis, we study your internal CRM structure and set up synchronization of statuses, order data, and customers. This avoids accounting gaps. If the CRM doesn't provide an API, we set up an intermediate layer through a message queue (RabbitMQ).

Process of work

Timelines and cost

MVP with booking and statuses—6–9 weeks. Full product with courier tracking, payments, and multi-location—3–5 months. The cost is calculated individually during the analysis phase—we'll give you an exact figure after reviewing your case.

How we set up push notifications

1. Register the app in Firebase Console (Android) and Apple Developer (iOS).
2. Generate APNs keys and upload to Firebase.
3. Initialize Firebase Messaging on the client and get the device token.
4. On the backend, save the token in the database and send notifications on status change.
5. Handle notification receipt in the app to update the UI.

Our experience and guarantees

8+ years in mobile development, 30+ projects for service industries (dry cleaning, cleaning, delivery). The team holds certifications in Flutter (Google Associate Developer) and React Native. Every app comes with a warranty—bug fixes for 3 months after launch. Get a preliminary assessment of your project—write to us or request a callback on the website. Contact us for a consultation and we will prepare a proposal within 2 days.

Used App Store Review Guidelines and Firebase Cloud Messaging.

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.