Industry: IoT & Connected Equipment
Platforms: iOS & Android
Type: Equipment Management App
Technology: React Native
Case Study
Building a Cross-Platform IoT Equipment Management App
Virtueinfo developed a cross-platform mobile application that helps users provision, organize, and monitor connected equipment across multiple locations — bringing account security, Bluetooth-assisted setup, Wi-Fi configuration, device status, history, alerts, and operational management into a structured mobile experience.
Project Overview
The project involved building an IoT mobile application for users responsible for connected equipment installed across one or more locations.
Each account can organize installations into locations and logical systems, associate compatible devices, review current operating information, and access historical activity. The application also guides users through discovering nearby hardware and connecting it to a local Wi-Fi network.
Virtueinfo implemented the application as a shared React Native codebase for iOS and Android.
The Business Challenge
Connected equipment is only useful when users can install and manage it reliably. Device commissioning can involve Bluetooth permissions, local network credentials, hardware availability, cloud registration, and platform-specific steps.
The solution needed to simplify this process without hiding important feedback. It also required a clear hierarchy connecting accounts, locations, systems, and devices rather than an unstructured equipment list.
Additional challenges included secure registration, authenticated API communication, consistent Bluetooth behavior, status visibility, event history, configurable notifications, and recovery from expired sessions or interrupted operations.
Our IoT Mobile App Development Approach
Virtueinfo separated the application into four principal concerns: identity and access for registration, verification, authentication, and profile management; asset organization for locations, systems, devices, and service resources; hardware commissioning for Bluetooth discovery and Wi-Fi provisioning; and operations for current status, history, alerts, and user actions.
Reusable components were created for recurring interactions, and navigation was divided into focused status, history, and action areas.
A centralized API layer applies authentication, processes errors, refreshes expired access tokens, and reduces duplicated networking logic. Hardware communication remains in dedicated Bluetooth and provisioning modules because it has a different lifecycle from ordinary cloud requests.
The Connected Equipment Management Solution
Virtueinfo delivered a mobile operations interface for the connected-device lifecycle.
Account Security and Verification
Users can create and verify an account, recover access, manage authenticated sessions, and strengthen sign-in with optional two-factor authentication — with preferences and profile details managed inside the app.
Bluetooth and Wi-Fi Provisioning
During installation, the application scans for compatible nearby devices and guides the user through connecting selected hardware to Wi-Fi through a Bluetooth-assisted workflow with clear status feedback.
Multi-Location Device Management
Users organize equipment by location, create logical systems, and associate devices — producing an operational hierarchy that remains understandable as installations grow.
Status, History, and Alerts
After commissioning, status screens present operating and connectivity information, historical views help users inspect recorded activity, and cloud messaging creates a foundation for timely operational alerts.
Key Features
Secure Account Onboarding
The application supports registration, sign-in, account verification, password recovery, and authenticated session management.
Two-Factor Authentication
An additional verification step can strengthen account access. Dedicated screens guide users through enrollment and code validation.
Multi-Location Equipment Organization
Users can manage multiple installation locations and group equipment into logical systems, producing a structure that remains understandable as installations grow.
Bluetooth Device Discovery
The app requests required permissions, scans for nearby compatible equipment, and presents discovered devices for selection with clear status feedback.
Guided Wi-Fi Provisioning
Users can discover available networks and provide Wi-Fi configuration to selected equipment through a guided Bluetooth-assisted workflow.
Device and System Management
Users can register, rename, associate, move, or remove devices through purpose-built screens connected to the appropriate location and system.
Current Operational Status
Status screens consolidate readings and operational indicators. Visual states help distinguish normal, cautionary, and unavailable conditions.
Historical Activity
System- and device-oriented history views let users review earlier status information and recorded events in context.
Alerts and Push Notifications
The mobile client handles notification permissions and integrates with a cloud messaging service, creating a foundation for operational updates.
Profile and Preference Management
Users can update profile information, verification details, notification choices, application preferences, and measurement units.
Technical Challenges and Solutions
| Challenge | Our Approach |
|---|---|
| Converting technical hardware setup into a usable workflow | Divided commissioning into guided discovery, selection, network configuration, and result states. |
| Supporting Bluetooth on iOS and Android | Centralized permissions, scanning, connections, and communication while retaining native configuration. |
| Connecting hardware actions with cloud records | Separated local provisioning from account and asset management, then linked devices to the operational hierarchy. |
| Managing expired sessions | Used a centralized API client that refreshes credentials and retries affected requests. |
| Preventing refresh conflicts | Coordinated waiting requests around one token-refresh operation. |
| Presenting complex relationships clearly | Structured the experience around locations, systems, and devices. |
| Communicating slow operations | Added loaders, validation, result dialogs, and feedback around scans, connections, and API calls. |
Security & Reliability
The application uses bearer-based authentication with access- and refresh-token handling. A centralized networking layer applies credentials and manages expired sessions.
Account security is supported through email or phone verification, password-management workflows, and optional two-factor authentication. Input validation, API error handling, loading states, and result dialogs help reduce incomplete actions.
Production deployments should additionally use platform-protected credential storage, controlled diagnostic logging, secure secret management, encrypted transport, and backend authorization checks.
Scalability & Performance
The location–system–device hierarchy supports a growing number of installations without presenting one unstructured equipment list.
Reusable components and centralized services make it easier to add equipment types and workflows. Shared state reduces repeated handling of user data, and coordinated credential renewal prevents competing refresh operations.
Server-side scalability, database performance, and infrastructure capacity depend on the associated backend platform and should be assessed separately.
Business Outcomes
- A simpler commissioning experience for non-specialist users.
- Centralized management of multiple locations and installations.
- Clear relationships between systems and physical devices.
- Better visibility into current equipment condition.
- Easier access to historical operational information.
- More consistent account-verification and security workflows.
- Reduced reliance on separate setup tools.
- A shared mobile experience across iOS and Android.
- A maintainable foundation for future device features.
Why Choose Virtueinfo for IoT App Development?
This project required more than conventional mobile screen development. It combined native permissions, Bluetooth communication, embedded-device provisioning, authenticated cloud APIs, application state, push notifications, and multi-level equipment management.
Virtueinfo brought these concerns together in a modular React Native application while keeping hardware communication, cloud integration, and user-facing workflows clearly separated — demonstrating an ability to build IoT mobile applications that bridge embedded hardware and cloud platforms while addressing operational workflows, platform differences, security, and maintainability.
Building an IoT or Connected Device App?
Let’s bridge your hardware and cloud platform with one dependable mobile experience.
Frequently Asked Questions
What is an IoT equipment management app?
An IoT equipment management app connects users with physical devices and their supporting cloud platform. It can assist with installation, configuration, device organization, current status, history, alerts, and account administration.
Can React Native be used for Bluetooth IoT applications?
Yes. React Native can support Bluetooth Low Energy through compatible native libraries. A reliable implementation still requires careful permissions, connection-state management, hardware testing, and accommodation of platform differences.
How does Bluetooth-assisted Wi-Fi provisioning work?
The app discovers a nearby device over Bluetooth. The user selects a Wi-Fi network and provides its credentials, which the app transfers through the supported provisioning protocol so the device can join the network.
How should multiple IoT devices be organized?
For distributed installations, a hierarchy such as account, location, system, and device makes equipment easier to find and manage. Search, filtering, and clear status indicators become increasingly important as deployments grow.
How can an IoT mobile app protect user accounts?
Common controls include secure authentication, account verification, short-lived access credentials, refresh-token management, optional two-factor authentication, protected credential storage, encrypted transport, and server-side authorization.
What happens when a device is temporarily offline?
A well-designed app distinguishes cloud, mobile, network, and device availability. It should present a clear unavailable state, avoid treating stale information as current, and provide appropriate retry guidance.
Can one React Native application support iOS and Android?
Yes. React Native provides a shared application layer while allowing native configuration where permissions, Bluetooth behavior, notifications, or lifecycle rules differ.
What should a company consider before developing an IoT app?
Important considerations include the device protocol, provisioning method, mobile permissions, backend APIs, identity model, firmware compatibility, offline behavior, security requirements, notifications, deployment scale, and field diagnostics.