Mobile MES Application Development for Production Control

The shop floor lacks stable internet, workers wear gloves and face vibration. Paper route sheets and Excel reports prevent full traceability — any ERP integration fails. Our mobile MES application for production control integrates output accounting and quality control modules. With over 10 years of experience and more than 15 successful implementations, our team specializes in industrial mobile solutions. Developing a mobile application for production control (MES) solves these issues: we create apps that collect shop floor data in real time, integrate with SAP ME, Siemens Opcenter, and any SCADA system. The solution has been deployed in over 15 implementations across Russian and CIS enterprises, from machine building to pharmaceuticals. On average, order processing time is reduced by 40%, and data entry errors drop by 70%.

How We Develop a Mobile MES Application for the Shop Floor

A shop floor is not an office. Devices must work with gloved hands (stylus or large touch zones), under vibration, and in the presence of industrial Wi-Fi interference from frequency converters. Screens must be readable in bright light or in dark areas. These requirements dictate device selection.

For heavy industry — rugged terminals: Panasonic Toughbook FZ-T1, Zebra MC9300, Honeywell CT40. They run Android 8+, support DataWedge, RFID, NFC. For light manufacturing — standard smartphones or tablets in protective cases. The average cost ranges from $1,000 to $2,000 per unit, but the solution pays for itself in 4-6 months through reduced defects.

Integrating the Mobile App with Existing MES

Most industrial MES (SAP ME, Siemens Opcenter, Wonderware) offer OData or REST APIs. However, SAP ME versions before 15.x use SOAP — requiring XML mapping. Retrofit with SimpleXml converter handles this, but WSDL schemas from SAP ME are large: auto-generation via wsdl2java saves time. REST APIs are 3 times faster than SOAP for frequent requests, so we migrate to REST when possible.

Production task synchronization uses a pull model with caching. The worker receives the shift task list upon login and then works offline. Critical events (start operation, stop, defect logging) are immediately queued for sending via WorkManager:

val syncRequest = OneTimeWorkRequestBuilder<OperationSyncWorker>()
    .setConstraints(
        Constraints.Builder()
            .setRequiredNetworkType(NetworkType.CONNECTED)
            .build()
    )
    .setBackoffCriteria(BackoffPolicy.EXPONENTIAL, 15, TimeUnit.SECONDS)
    .build()
WorkManager.getInstance(context).enqueueUniqueWork(
    "operation_sync_${operationId}",
    ExistingWorkPolicy.KEEP,
    syncRequest
)

The KEEP policy is important: if the network fails and the worker presses "complete" twice, only one sync task should be in the queue.

Common integration mistakes: forgetting MES API versioning — if the MES is updated without backward compatibility, the mobile app will stop syncing. We recommend testing integration on a staging environment before updates. Also ignoring data volume: at shift start, there may be 500+ tasks — pagination is necessary.

Output Accounting and Component Traceability

Scanning parts, assemblies, and finished products is a core function. Each part has a unique QR or DataMatrix with a serial number. During assembly: the worker scans the component → the system checks if it is suitable for the current operation → allows continuation or blocks with a reason. This processes up to 300 operations per hour with 99.9% accuracy.

At the application level, we make a request to the MES API with serial_number + work_order_id + operation_id. The response: "allowed" / "wrong component" / "component already used". The last case is critical: it catches duplicate scans and prevents double counting.

Quality Control and Defect Logging

The defect marking form is not just a "quantity" field. It requires selecting a defect code from a classifier (GOST or internal reference), attaching a defect photo, and indicating the location on the part.

On Android, we use CameraX ImageCapture for photos, compressing via Bitmap.compress(JPEG, 70) before sending — 50 MP photos are unnecessary. Location annotation uses a Canvas overlay on ImageView, storing tap coordinates as a percentage of the image size (not pixels, which change on resize). This system reduces complaints by 15-20% through accurate logging.

Why Offline Mode Matters

A production shop is an area of unstable Wi-Fi. Without offline mode, the app is useless. We design the architecture with local storage (Room) and synchronization via WorkManager. This guarantees that no operation is lost, even if the network goes down for 2 hours. In one project, offline mode reduced downtime by 30%: workers no longer waited for data to load.

Equipment Monitoring via OPC UA

If the MES is integrated with SCADA through OPC UA (OPC Foundation), the mobile app can display real-time machine parameters: RPM, temperature, vibration. The Prosys OPC UA SDK for Android is a commercial library with good documentation. Subscribing to MonitoredItem with a sampling interval of 1000 ms is sufficient for a production dashboard. Without this SDK, Eclipse Milo via JVM requires careful thread management and increases app size.

Role-Based Access

In production, roles are fundamental: a worker sees only their own tasks, a foreman sees tasks for their area, and a technologist sees all operations with editing permissions for norms. We use Spatie Permissions on the Laravel backend, with JWT tokens containing role claims. On mobile, permissions are checked before rendering screens, and also enforced on the backend with every request.

What Is Included in Mobile MES App Development?

We provide a full cycle:

1. Analysis: audit of your production, device selection, integration scheme design (REST/SOAP/OPC UA).
2. Prototype: in 2 weeks, we deliver an MVP using real data.
3. Development: Android/Kotlin + Jetpack Compose, code covered with unit and UI tests.
4. Integration: connecting to MES, SCADA, ERP; testing on the shop floor.
5. Documentation: API specs, user manuals.
6. Training: workshops for foremen and technologists.
7. Support: 12-month code warranty, 4-hour SLA for critical bugs.

Timeline and Economic Efficiency

A basic MES app (tasks, operations, defects, sync): 8-12 weeks. Full cycle with OPC UA, component traceability, defect photos, and BI integration: 4-7 months. Pricing is determined individually after analyzing the integration scheme. Typical investment is between $30,000 and $60,000, with ROI in 4-6 months. On average, the implementation pays for itself in 4-6 months, saving the enterprise up to $25,000 per year through reduced defects and paper workflow. Our clients report a 25% increase in overall equipment effectiveness (OEE).

We will assess your project in 2 days — just write to us. Request a custom mobile MES application to improve your shop floor productivity. Receive a detailed plan and accurate estimate.

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.