Industry: Industrial Field Operations
Platforms: iOS & Android
Type: Connected Equipment Operations App
Technology: React Native
Case Study
Building a Connected Industrial Dispensing Operations App
Virtueinfo developed a cross-platform mobile application that connects field operators, backend transaction services, and nearby industrial equipment — guiding users through asset validation, operational data capture, equipment connection, and controlled dispensing workflows while accounting for unreliable field connectivity.
Project Overview
The project involved building a connected mobile solution for industrial dispensing and field operations. Operators needed one guided interface through which they could sign in, select an authorized dispensing point, identify a vehicle or operational asset, record required readings, connect to nearby equipment, and manage the transaction lifecycle.
The application combines a structured business workflow with Bluetooth-enabled equipment communication, backend APIs, message-based device control, multilingual support, and managed-device deployment.
The Business Challenge
Industrial dispensing involves more than recording a transaction. Each activity may depend on an authorized operator, a valid asset, the correct dispensing point, required meter readings, a job reference, equipment availability, and confirmation from central services.
A fragmented process creates real operational problems: operators move between disconnected systems, transaction context gets lost between the mobile device and physical equipment, and poor connectivity interrupts time-sensitive field work. Hardware communication failures can leave users uncertain about transaction status, inconsistent device configurations complicate distributed deployment, and manual data entry reduces operational consistency.
The application therefore had to coordinate people, software, connectivity, and physical hardware through a clear and reliable workflow.
Our Approach
Virtueinfo translated the operational process into a structured mobile journey, from authentication and asset identification through equipment connection and transaction completion. Business steps were mapped to explicit mobile states, with the interface, API, and hardware communication layers kept clearly separated through reusable BLE and MQTT adapters.
The engineering approach handled mobile permissions and platform differences, preserved transaction context locally, and designed deferred operations for connectivity interruptions — so essential workflows continue when the network does not cooperate.
Session-expiry and token-renewal handling were introduced across the API layer, and the application was prepared for controlled deployment on managed devices, with support for incremental testing of hardware and transaction workflows.
The Solution
The resulting application provides a focused operational workflow for connected dispensing.
Guided Operator Workflow
An operator authenticates and selects an available dispensing point. The application validates the relevant vehicle or asset, collects an odometer or operating-hours reading, and requests an additional job reference when required.
Bluetooth Equipment Connection
The application scans for approved nearby equipment and establishes a BLE connection, coordinating device communication through BLE and message-based services while backend APIs manage the business transaction.
Synchronized Transaction Control
The user can follow the transaction state in the application, while start and stop events are synchronized with central services so business records and equipment activity stay aligned.
Offline-Aware Continuity
Local persistence and deferred queues help preserve relevant actions when network connectivity is interrupted, processing queued work when connectivity returns.
Key Features
Secure Operator Sign-In
The application provides authenticated access and maintains session state between launches. Token renewal and session-expiry handling return operators to sign-in when their session can no longer be refreshed.
Guided Dispensing Workflow
A step-by-step interface leads operators through dispensing-point selection, asset identification, readings, optional job information, device connection, and transaction control.
Vehicle and Asset Validation
Operational identifiers are checked through backend services before equipment control begins, keeping transactions associated with the correct business context.
Configurable Operational Data Capture
The workflow can request an odometer reading, operating-hours value, or job reference according to backend-provided requirements.
Bluetooth Equipment Connectivity
The application discovers nearby BLE equipment, requests required mobile permissions, establishes a connection, and retrieves the information needed for subsequent communication.
Coordinated Device Messaging
A message-oriented communication layer supports command delivery and equipment responses. Transaction-aware processing keeps device activity aligned with the corresponding backend operation.
Offline-Aware Transaction Handling
When connectivity is unavailable, selected API operations and device messages can be stored locally with transaction and deduplication identifiers for later processing.
Transaction-State Monitoring
The application checks the current transaction state and responds to changes initiated by backend services or operational equipment.
Multilingual Interface
Internationalization support allows operators to switch between supported languages while preserving their preference locally.
Managed-Device Readiness
The Android implementation includes capabilities suitable for dedicated operational tablets, including kiosk-oriented management support.
Technical Challenges and Solutions
| Challenge | Our Approach |
|---|---|
| Coordinating mobile, backend, and hardware state | Structured the workflow around explicit transaction stages and separated API and equipment communication into dedicated layers. |
| Reliable nearby-device discovery | Implemented platform-aware permissions, controlled scans, device deduplication, connection checks, and disconnect handling. |
| Preserving message order | Dependent device messages are processed sequentially and correlated with their transaction. |
| Intermittent network access | Selected API calls and device messages can be recorded locally and processed when connectivity returns. |
| Avoiding duplicate deferred actions | Queue entries use transaction references and idempotency-oriented identifiers. |
| Managing authenticated sessions | Request handling includes expiration checks, token refresh, session updates, and forced sign-out when renewal is no longer possible. |
| Supporting multiple platforms | Shared React Native logic is combined with native integrations where device behavior differs. |
| Controlled operational deployment | The Android application includes dedicated-device capabilities suitable for centrally managed field hardware. |
Security & Reliability
The solution uses authenticated API sessions and refresh-token lifecycle handling. When a session can no longer be renewed, stored authentication state is cleared and the operator returns to the login workflow.
Input validation is applied to required fields, while platform permissions control access to Bluetooth, location-related scanning, and notifications. Logging out clears application session data and disconnects active BLE devices.
Reliability is supported through network reachability checks, transaction-state monitoring, device connection handling, and transaction-aware local queues. Production deployment should additionally enforce encrypted sensitive storage, restricted diagnostic logging, secure transport, backend authorization, signed builds, and regular security reviews.
Scalability & Performance
The shared React Native codebase reduces duplication across Android and iOS while allowing native implementations for specialized communication requirements.
The application limits BLE discovery periods and deduplicates scan results. Local persistence reduces repeated retrieval of workflow context, while connectivity checks prevent avoidable online requests.
Deferred records are grouped by transaction and device, and ordered message processing helps preserve command dependencies when queued work resumes. The dedicated-device architecture also supports repeatable rollout across distributed operational endpoints.
Business Outcomes
- A more consistent operator workflow with centralized transaction validation.
- Better alignment between business records and equipment activity.
- Reduced dependence on disconnected manual processes.
- Clearer guidance for vehicle, asset, and job-data entry.
- Improved continuity during temporary connectivity loss.
- Consistent behavior across managed field devices.
- Easier extension of hardware and backend integrations.
- Better maintainability through separated communication layers.
Why Virtueinfo
Virtueinfo was technically suited to this project because it required more than conventional mobile application development. The work combined cross-platform UI engineering, native mobile integration, BLE communication, MQTT messaging, authenticated APIs, offline-aware data handling, multilingual UX, and dedicated-device deployment — brought together in an architecture aligned with the operational workflow.
This experience is relevant to organizations building connected field-service tools, industrial applications, equipment-control interfaces, fleet workflows, or other software that bridges physical devices and central business systems.
Building a Connected Field Operations App?
Let’s bridge your equipment, operators, and business systems in one reliable mobile workflow.
Frequently Asked Questions
How do you build a mobile app for industrial equipment?
Start by mapping the operator workflow and equipment states. Maintain clear boundaries between the interface, business APIs, local storage, and hardware communication layer. Real-device testing is essential because wireless connectivity and equipment behavior cannot be validated through interface tests alone.
Why use React Native for an industrial mobile application?
React Native allows Android and iOS applications to share much of their interface and business logic. Native modules can still support specialized requirements such as Bluetooth communication, kiosk controls, or platform-specific messaging.
How can a mobile app communicate with nearby industrial hardware?
Bluetooth Low Energy can discover and communicate with nearby equipment. A production implementation must manage permissions, scanning, connection state, device compatibility, command validation, timeouts, and disconnections.
What is the role of MQTT in a connected-device application?
MQTT provides lightweight publish-and-subscribe messaging between applications, services, and connected devices. It is useful for asynchronous commands, telemetry, status updates, and distributed message delivery.
Can an industrial mobile app work with unreliable internet connectivity?
Yes. Selected operations can be stored locally and synchronized after connectivity returns. Reliable implementations should use transaction identifiers, deduplication, ordering rules, retry controls, and backend idempotency.
How can dispensing transactions be associated with the correct asset?
The application can validate an asset identifier through a backend service and capture required supporting information before enabling the transaction. Central services should enforce the underlying authorization and business rules.
How are dedicated field tablets managed?
Enterprise device-management tooling can enroll tablets, install applications, apply kiosk policies, control updates, and monitor device health. A phased pilot is recommended before wider rollout.
What should be tested in a connected industrial mobile app?
Testing should cover validation, API failures, token expiration, Bluetooth permissions, scanning and reconnection, equipment responses, message ordering, offline recovery, duplicate prevention, upgrades, and real-world operation on supported hardware.