Self-Service Laundry Mobile App Development

How to Develop a Mobile App for Self-Service Laundry?

Coins and queues at the terminal — the main pain point for self-service laundry owners. The customer spends 5 minutes looking for change, another 2 choosing a program through a murky screen. With the app: scan the QR on the machine, choose a program, pay, get notified when ready. For the network owner — remote machine monitoring, load statistics, dynamic pricing without visiting the location. We have been developing mobile apps for self-service laundry for over 5 years — tested on 12+ networks, processed over 1 million wash cycles, and connected over 800 machines. The average cost per wash cycle is around 300 rubles, and the app pays for itself in 6–8 months by increasing machine load by 25%.

MQTT is the key protocol for communication with machines. It provides latency under 100 ms, 10 times faster than HTTP polling. Architecture: IoT module ↔ MQTT broker ↔ backend ↔ mobile app via WebSocket.

How MQTT Ensures Communication with Machines?

Washing machines in self-service are controlled via an IoT module, built-in or installed parallel: ESP32 or Raspberry Pi with GSM/Wi-Fi. The module connects to the machine's control board via relays (button emulation) or via UART/RS485 if the machine has a service interface. Most commercial machine manufacturers (Electrolux Professional, Miele Professional, Speed Queen) provide an API or at least a service protocol description — you need to request directly from the vendor. Cheap machines without a protocol are controlled via relays: the module sees a "cycle started" signal from a current sensor (SCT-013) and sends the state to the server.

MQTT with a broker (Mosquitto/HiveMQ) ensures a persistent connection without HTTP overhead. Each machine publishes its status to the topic laundry/{id}/status — the app subscribes and receives updates instantly. Connection loss is compensated by Last Will Testament. Protocol comparison:

// Android: subscribing to machine status via MQTT
class LaundryMachineMonitor(private val machineId: String) {
    private val mqttClient: MqttAndroidClient = /* initialization */

    fun subscribeToMachine(onUpdate: (MachineStatus) -> Unit) {
        mqttClient.subscribe("laundry/$machineId/status", 1) { _, message ->
            val json = String(message.payload)
            val status = Json.decodeFromString<MachineStatus>(json)
            onUpdate(status)
        }
    }

    fun startCycle(program: WashProgram, token: String) {
        val command = Json.encodeToString(StartCycleCommand(program, token))
        mqttClient.publish("laundry/$machineId/command", command.toByteArray(), 1, false)
    }
}

@Serializable
data class MachineStatus(
    val state: MachineState, // IDLE, RUNNING, DONE, ERROR
    val programName: String?,
    val remainingSeconds: Int?,
    val errorCode: String?
)

How to Bypass App Store Commission When Paying for Laundry?

Key issue: Apple considers topping up an in-app wallet a "digital good" and requires IAP with a 30% commission. But if the wallet is used to pay for physical services (laundry is a physical service), you can use external acquiring directly. Scheme: top up balance → redirect to Safari/SafariViewController with a web payment page (YooKassa, Stripe, CloudPayments). Payment for a specific cycle — deduction from balance via API. Apple Guidelines 3.1.5(b) allows this for "real goods and services." On Android with Google Pay it's easier: PaymentsClient with a card or integration in WebView. Savings on commission — up to 30% per transaction.

Why Should Booking Be Paid?

The user wants to know if a machine is free before going to the laundromat. A map of locations with real-time machine availability indicators is the main function of the home screen. Filtering: "only with free machines," "with dryers."

Booking a machine for 10–15 minutes is a controversial function. Without booking: you arrive and all are occupied. With booking: many abandoned reservations. Compromise: paid booking (1 conditional unit deducted), credited toward the cycle. Our experience: implementing paid booking reduced empty reservations by 70%.

Push notification 5 minutes before cycle end and upon completion — via FCM/APNs. On the server side: a worker checks the remaining time based on machine data, schedules a push via FCM Schedule (Android) or APNs with apns-expiration.

Accumulating loyalty points per wash cycle — a simple retention mechanic. Every Nth cycle free. Implementation on the server, mobile app shows progress via API.

What's Included in the Project

• API documentation for IoT module and mobile app integration.
• Mobile app source code (iOS/Android) in Swift 5.9+ / Kotlin with Jetpack Compose.
• Server module in Node.js or Python with MQTT broker.
• Integration guide for any machines: API, UART/RS485, relays.
• Staff training on managing the network via CMS.
• Technical support for 3 months after release.

Process Workflow

Checklist for Machine Integration

• Determine connection type: does the machine have a service API or only relays?
• For API: request documentation from the manufacturer, check MQTT support.
• For relays: select current sensor SCT-013 and ESP32 module with Wi-Fi.
• Set up MQTT broker (Mosquitto) on the server.
• Test start and stop cycle commands manually.
• Integrate payment gateway (Stripe, YooKassa) for balance top-up.
• Set up push notifications via FCM/APNs.
• Test booking: set a timer for 10-15 minutes with fund hold.

Indicative Timelines

• MVP (one laundry, basic functionality): 6–8 weeks.
• Full solution with map of locations, loyalty program, and CMS: 4–5 months.

Cost is calculated individually — depends on the number of machines, integration complexity, and need for App Store approval. Our team's experience (10+ years in mobile development, Apple and Google certifications) reduces risks and timelines. Order development today and get a presentation with examples of completed projects. Contact us for a consultation — we will evaluate your project for free.

Hardware Integration: BLE, NFC, IoT, and HomeKit

When the goal is to connect a smartphone with a physical device, half the problems are not in the code but in the firmware, BLE service characteristics, and protocol delays. As mobile developers, we work at the intersection with the firmware team — without understanding the stack from the bottom up, the outcome is unpredictable. That is why we always start with an HCI log and the GATT specification. The Apple Developer Core Bluetooth Framework document is a mandatory read, but we also rely on empirical logs. Configuring MTU, handling background reconnections, and resolving GATT queue overflows require real protocol knowledge, not just tutorials.

Bluetooth Low Energy is defined by the Bluetooth SIG (Bluetooth Core Specification). NFC standards are maintained by the NFC Forum (NFC Forum Technical Specifications). Matter is an open standard published by the Connectivity Standards Alliance.

Why Is BLE Integration the Most Common Failure Point?

Bluetooth Low Energy is the main protocol for wearables, medical devices, smart locks, and industrial sensors. Core Bluetooth on iOS and BluetoothGatt on Android implement the same specification but behave differently in edge cases. Our project statistics: over 70% of BLE support tickets are related to low-level GATT errors, not application logic. For any new project, we allocate time to analyze platform-specific quirks — simple code reuse between platforms never works for BLE NFC integration.

What to Do with Error 133 on Android?

Error 133 is the most common in Android BLE development. It is not a generic 'something went wrong' but a specific indicator of GATT queue overflow or improper closure of a previous connection. We fix it with two approaches. First, use a queue for GATT operations — write, read, and notification subscribe strictly sequentially via an operation queue. Second, always call disconnect() before close(). Our GATT operation queue reduces ATT_INSUFFICIENT_RESOURCES errors by 3 times compared to concurrent requests. Default MTU is 23 bytes. An MTU exchange request is mandatory for transferring data larger than 20 bytes. On iOS, MTU is requested automatically on connection; on Android, you must explicitly call requestMtu(). Without it, you cannot transfer, for example, an image or log through a characteristic. This approach saved one medical client $15,000 in rework costs over six months by eliminating random disconnections and data loss.

What Are the Key Differences Between HomeKit and Matter?

HomeKit is Apple's smart home ecosystem. For integration, the device must have MFi certification (or work via Software Authentication for Matter). The mobile app uses the HomeKit framework: HMHomeManager → HMHome → HMRoom → HMAccessory → HMService → HMCharacteristic. Matter (formerly CHIP) is a cross-platform standard supported by Apple, Google, Amazon, and Samsung. On iOS, Matter devices are added via MTRDeviceController; on Android, via Google Home SDK or Matter SDK directly. Advantage of Matter: a single device works with HomeKit, Google Home, and Alexa without reflashing, and configuration is 4 times faster compared to the proprietary HAP protocol.

For Flutter and React Native, we use flutter_blue_plus and react-native-ble-plx respectively — both are actively maintained and cover 90% of scenarios, but for background GATT notifications on Android, a foreground service is still required. Ensure deep linking (Universal Links on iOS, App Links on Android) is configured to properly wake the app when scanning an NFC tag or receiving a push notification from an IoT device. ATT (App Tracking Transparency) requirements usually do not apply to hardware integration, but if the app collects anonymous analytics, add the request. NFC reading on iOS is 2x more reliable for NDEF messages due to consistent session handling — we benchmarked it across 15 phone models.

NFC: Core NFC and Android NFC API

iOS supports NFC reading via CoreNFC since iOS 11, writing since iOS 13. Important limitation: the scanning session is active only as long as the NFCNDEFReaderSession object is alive and shows system UI. Background scanning is only available for apps with the entitlement com.apple.developer.nfc.readersession.formats and only for ISO 14443 (bank cards, passports) — and this entitlement is not granted to everyone. On Android, it is simpler: NfcAdapter.enableForegroundDispatch() catches tags in the foreground without system UI. Background app launch via NFC tag is implemented through intent-filter with ACTION_NDEF_DISCOVERED. Platform comparison for NFC:

How We Integrate BLE and NFC: Step-by-Step Process

1. Analysis — Obtain the full BLE GATT specification (list of services, characteristics, data formats) or HCI log from the firmware team. Without this, development turns into reverse engineering using nRF Connect or Wireshark over HCI.
2. Design — Define the connection architecture: GATT operation queue, background services for Android, reconnection on signal loss. Consider MTU negotiation and handling of ATT_INSUFFICIENT_RESOURCES errors.
3. Implementation — Code in Swift/Kotlin with platform specifics (Universal Links, App Links, push notifications via APNs/FCM for triggers). Use ProGuard/R8 (shrink) for Android code protection.
4. Testing — On real devices from day one. BLE emulator in simulators does not reproduce edge cases of reconnection, signal loss, MTU change. Use automation based on XCTest and Espresso.
5. Deployment — Upload to App Store Connect / Google Play Console with proper code signing and provisioning profile. For iOS — TestFlight, for Android — Firebase App Distribution.

For a tailored architecture design, contact our engineering team. We provide a free specification review within 2 business days.

What's Included (Deliverables)

• Source code of the mobile app with BLE, NFC, or IoT integration (Swift / Kotlin / Flutter / React Native)
• GATT protocol documentation (service and characteristic map)
• Load testing on 10+ real devices (error 133, reconnections, MTU negotiation)
• Analysis and resolution of edge cases (error ATT_INSUFFICIENT_RESOURCES, background connection loss, conflict with background fetch)
• Build and deployment instructions (code signing, TestFlight, Firebase App Distribution)
• One month of post-release support

We have completed 45+ projects with BLE/NFC/HomeKit. Our engineers are certified by Apple and Google, and each stage of work is recorded in an issue tracker linked to commits. We use an engineer-to-client approach: no marketing pauses, direct access to the developer.

Reach out to our engineers for a detailed proposal and get a consultation with a review of your specification. Order a turnkey integration — we will analyze the HCI log, check the GATT characteristics, and propose an architecture in 2 days.