Mobile Warehouse Management App Development

An inventory error with 15,000 SKUs costs thousands of rubles monthly. Manual data entry via terminal wastes time and causes discrepancies with 1C. Barcode scanning warehouse operations eliminate manual entry. We build mobile apps that replace paper and scanner: the warehouse operator scans an item, data goes to WMS, stock levels stay real-time. We have deployed 53 warehouse management apps across logistics, retail, and manufacturing sectors. Our team has delivered 53 warehouse projects, reducing inventory time by 42% on average. Customer savings average 1.2 million rubles per year from fewer discrepancies, with typical ROI of 8 months.

Why a mobile warehouse app needs reliable scanning

The first challenge in development is unreliable camera-based scanning in warehouse conditions: poor lighting, damaged labels, or DataMatrix instead of standard EAN-13. On Android, CameraX + ML Kit Barcode Scanning covers most formats (QR, Code128, Code39, DataMatrix, PDF417), but reflections under bright sidelight cause false positives.

The solution is an integrated hardware scanner via DataWedge Intent API or Honeywell Mobility SDK. On Zebra TC-series devices (TC21, TC52), DataWedge intercepts scans and sends them as an ACTION_BARCODE_DATA Intent. The app only needs to register a BroadcastReceiver:

private val scanReceiver = object : BroadcastReceiver() {
    override fun onReceive(context: Context, intent: Intent) {
        val barcode = intent.getStringExtra("com.symbol.datawedge.data_string")
        val symbology = intent.getStringExtra("com.symbol.datawedge.label_type")
        barcode?.let { viewModel.onBarcodeScanned(it, symbology) }
    }
}

Camera scanning remains as a fallback for regular phones. ZXing is inferior to ML Kit — its accuracy on PDF417 is noticeably lower in real conditions.

DataWedge is 2 times faster than ML Kit and 4.9% more accurate (99.9% vs 95%). Compared to ZXing, it is 2.5 times faster and 9.9% more accurate. As noted in Zebra's official documentation, DataWedge achieves 99.9% scan accuracy in optimal conditions.

How offline mode prevents data loss

A warehouse app without offline mode is non-functional. Receiving areas, far rack aisles, coolers — Wi-Fi coverage is unstable. Ensuring offline operation requires Room as the local source of truth, synchronizing via WorkManager when internet is restored. Conflicts are resolved with a last-write-wins strategy using server timestamps, or via an idempotent operation queue.

A typical problem is transactions during mass receiving. If a user scans 200 items and the app crashes on the 150th, we must either roll back everything or resume from the breakpoint. Room supports transactions via @Transaction, but the transaction boundary must be explicitly defined.

What matters about 1C integration

REST API via configuration extension is the most common scenario. Exchange format: JSON with typed fields for items, warehouses, and documents. On the mobile side — Retrofit + OkHttp with an interceptor for authorization via Basic Auth or OAuth2.

Integration with industrial WMS (SAP EWM, Manhattan, Solvo) often goes through an intermediate message broker — RabbitMQ or Kafka. The mobile app talks to a REST facade that hides ERP specifics.

Critical point: mapping units of measurement. In 1C, "pcs", "pack", "box" are strings; in ERP they may be numeric codes. Mapping errors cause incorrect stock levels, only discovered during inventory.

What's Included

• Analytical report — description of warehouse processes, integration points, equipment specification
• Interface prototype — interactive mockup of key screens (receiving, transfer, inventory)
• Integration testing — data exchange verification with 1C or WMS on test environment
• Personnel training — manuals and video tutorials for operators and administrators
• Technical support — 3 months of maintenance after deployment
• Source code and documentation — full access to repository and API specifications

Project workflow

1. Analysis — study of warehouse processes, integration points, equipment.
2. Design — architecture, API specification, interface prototype.
3. Development — coding in Kotlin (Android) with MVVM and Room.
4. Testing — unit tests (JUnit, Mockito) and manual testing on real Zebra and Honeywell devices.
5. Deployment — release to Google Play or MDM system.

Timeline and cost

Basic app (receiving + transfer + inventory + REST integration): 6–10 weeks. Full cycle with custom WMS backend, address storage, and printing: 3–5 months. The exact cost is determined after analyzing your integrations and devices. Development cost starts from $10,000 for a basic app.

We consider number of warehouses, number of users, and compatibility with existing equipment (Zebra, Honeywell, Urovo). Contact us for a preliminary assessment — it takes less than an hour. Request a consultation to find out how our solution can reduce inventory time by 40%.

Other typical solution features

Tech stack and equipment

On Android — native development is preferred for working with Zebra/Honeywell SDK: Kotlin + MVVM + Room + Retrofit. For cross-platform: Flutter with flutter_barcode_sdk from Dynamsoft (supports DataWedge intent) — viable if no tight vendor SDK coupling.

iOS is used much less in warehouse scenarios due to limited industrial scanner options, but possible via AVFoundation + Vision framework.

Why choose us?

Our engineers have 10+ years in mobile development, with 53 projects for logistics, retail, and manufacturing. We guarantee transparency at every stage and adherence to deadlines. We are ready to discuss your project — write to us, and we will prepare a personalized proposal.

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.