Industry: Agricultural Technology
Platforms: iOS & Android
Type: Remote Monitoring & Control App
Technology: React Native & TypeScript
Case Study
Building a Real-Time Remote Monitoring & Control App for Field Equipment
Virtueinfo partnered with an agricultural technology company to design and build a cross-platform mobile application that gives farm operators real-time visibility and remote control over distributed field equipment — combining live telemetry, interactive mapping, and remote command execution in a single mobile experience built for large rural properties with inconsistent connectivity.
Project Overview
The client operates in the agricultural technology sector, providing connected equipment and infrastructure used in large-scale farming operations. Their equipment generates continuous operational data — position, sensor readings, and status — that operators need to monitor and act on from the field.
Virtueinfo built the mobile companion application that connects farm operators, farm managers, and equipment dealers to this equipment network. The app serves as the primary day-to-day interface for checking equipment status, reviewing historical activity, and issuing remote commands without requiring an on-site visit.
The Business Challenge
Operators managing agricultural equipment across large, often remote properties faced several practical limitations. Checking on equipment status traditionally required physical presence or older, less accessible telemetry tools, while position, sensor data, and historical activity lived in separate contexts rather than a single operational view.
Rural network conditions made real-time data delivery and command execution unreliable with naive networking approaches, and operators and dealers needed to manage multiple properties and accounts from one login — with different access levels for owner-operators versus dealer and reseller accounts.
Above all, users needed actionable control, not just monitoring: the ability to actively issue commands to equipment rather than viewing read-only status.
Our Approach
Virtueinfo approached the project as a long-term mobile engineering partner. Discovery covered field-usage conditions, existing backend telemetry systems, and the operational workflows of different user types — owner-operators versus multi-site dealer accounts. The architecture was designed for a mobile client capable of consuming both request/response APIs and real-time event streams, with resilience built in for degraded network conditions.
The core monitoring, mapping, and control feature set was developed iteratively, using a component- and store-based structure to keep the growing feature surface maintainable, integrated with the client's existing backend services, real-time messaging infrastructure, mapping data, and push notification systems.
Testing ran across device types and simulated poor-connectivity conditions relevant to rural field use, followed by ongoing maintenance and feature delivery — including support for a backend platform migration carried out without disrupting the live mobile experience.
The Solution
The delivered application is organized around several core capabilities.
Unified Equipment Dashboard
A consolidated view of all sites and equipment tied to a user's accounts, with live telemetry delivered via a persistent connection rather than manual refresh.
Interactive Mapping
A map-first interface showing equipment location, status, and relevant environmental overlays such as rainfall, with clustering to keep large equipment counts readable.
Remote Command Execution
The ability to issue operational commands to equipment directly from the app, including scheduling future actions.
Historical Reporting
Charts and logs of past activity, sensor readings, and events per site, kept separate from live views so both stay fast.
Multi-Account Access
Support for both single-property users and higher-level accounts that manage multiple properties or sub-accounts from one login.
Notification Management
Configurable push alerts tied to equipment and account-level events, so operators hear about what matters without alert fatigue.
Key Features
Real-Time Equipment Status
Live position and operational-state updates are pushed to the app as equipment state changes, giving operators up-to-the-minute visibility without manual polling.
Interactive Field Mapping
A clustered map view displays all equipment across an operator's properties, with satellite and weather-overlay options for situational context.
Remote Command & Control
Operators can send operational commands to connected equipment directly from their mobile device, including scheduling future actions.
Historical Activity & Sensor Charts
Time-series charts surface sensor and rainfall history per site, helping operators spot trends and irregularities.
Multi-Property & Dealer Account Support
A group-based account model lets a single login manage one property or, for higher-tier accounts, oversee multiple properties and sub-accounts.
Event & Message History
A searchable log of equipment events and operational notes per site supports troubleshooting and record-keeping.
Configurable Push Notifications
Users can tailor which equipment and event types trigger mobile alerts.
Equipment Warranty Registration
An in-app flow lets users register purchased equipment for warranty coverage.
Resilient Field Networking
Automatic retry logic and dual real-time transport mechanisms help the app stay usable under the intermittent connectivity common in rural areas.
Technical Challenges and Solutions
| Challenge | Our Approach |
|---|---|
| Delivering real-time updates over unreliable rural network connections | Implemented dual real-time transport — WebSocket plus a fallback streaming channel — with automatic retry logic on standard API calls. |
| Rendering large numbers of equipment markers on a map without performance degradation | Implemented marker clustering and scoped real-time subscriptions per property rather than global data streams. |
| Supporting both single-property users and multi-property dealer accounts from one codebase | Designed a group-based account model with account-level scoping rather than hardcoded per-user roles. |
| Migrating from a legacy backend to a modern cloud-hosted API without disrupting live users | Supported both endpoints during a transition period, allowing a phased cutover. |
| Keeping a growing feature set maintainable | Adopted a modular store-based state architecture to isolate feature domains and simplify testing. |
| Managing third-party library quirks across iOS and Android | Used targeted dependency patching to resolve platform-specific issues without forking entire libraries. |
Security & Reliability
Account-scoped authentication ties each session to a specific property or account, limiting data access to what that account is authorized to see. Tiered account access distinguishes standard property-level accounts from higher-level accounts that manage multiple properties.
Device-level identification is used alongside account credentials for API and real-time channel authorization.
Crash and error monitoring is integrated to proactively surface and diagnose issues in production, while retry-tolerant networking reduces the risk of failed operations under unstable connectivity rather than silently failing.
Scalability & Performance
Marker clustering keeps map rendering performant as the number of monitored equipment units grows, while scoped real-time subscriptions ensure each client only receives data relevant to its own account and properties.
Separation of live and historical data paths — the real-time channel versus paginated history screens — keeps the live experience responsive while still supporting deep historical review.
The cloud-hosted backend supports horizontal scaling of the API layer independent of the mobile client release cycle.
Business Outcomes
- Centralized operational visibility: a single mobile view of equipment status across all properties instead of fragmented or on-site checks.
- Reduced physical site visits: remote monitoring and control cut reliance on in-person inspection for routine status checks.
- Improved responsiveness: real-time alerts and live status let operators react to equipment events more promptly.
- Simplified multi-property management: dealer and multi-site accounts manage several properties from a single application.
- Smoother platform evolution: the backend migration was executed without disrupting the mobile user experience, demonstrating a maintainable long-term architecture.
Why Virtueinfo
Virtueinfo brought together mobile engineering depth and real-time systems experience to deliver an application that had to work reliably in genuinely difficult field conditions — not just in a lab or office network. Our team designed for intermittent connectivity from the outset and built a scalable real-time architecture capable of supporting a growing device fleet.
A clean, modular codebase made it possible to support a live backend migration without customer-facing disruption. This combination of resilient mobile architecture, real-time systems design, and long-term maintainability reflects the kind of engineering partnership Virtueinfo brings to complex, field-deployed software products.
Monitoring Equipment Across Remote Sites?
Let’s put real-time visibility and control of your field equipment in one mobile app.
Frequently Asked Questions
How do you build a mobile app for real-time equipment monitoring?
Real-time equipment monitoring apps typically combine a persistent connection such as WebSockets for live data with a standard REST API for historical and account data. The client subscribes to scoped data channels so each user only receives updates relevant to their equipment.
What technologies are best for a cross-platform IoT monitoring app?
React Native is a strong choice because it allows a single codebase to target iOS and Android while still accessing native device capabilities like push notifications, maps, and background processing.
How can a mobile app remain reliable on poor rural networks?
Reliability under poor connectivity typically requires retry-aware networking, fallback communication channels — such as combining WebSockets with Server-Sent Events — and local caching so the app degrades gracefully instead of failing outright.
How do you support individual users and multi-account dealer access?
With an account- or group-scoped data model, where access and visible data are determined by the account context rather than hardcoded user roles — allowing higher-tier accounts to manage multiple properties or sub-accounts.
How do you migrate an app's backend without disrupting users?
A phased migration approach — where the mobile client can talk to both the legacy and new backend during a transition period — allows teams to cut over gradually and roll back if issues arise, minimizing risk to live users.
Can an app support both live monitoring and remote control?
Yes — by combining a real-time data channel for status updates with authenticated command endpoints for control actions, a mobile app can safely support both passive monitoring and active remote control of connected equipment.
Why use map-based clustering with many tracked devices?
Marker clustering groups nearby devices on a map at lower zoom levels, which keeps rendering performant and the map readable as the number of tracked devices grows, especially across large geographic areas.
How do you design push notifications for operational alerts?
Effective operational alerting lets users configure which event types and devices trigger notifications, preventing alert fatigue while still surfacing the events that matter most to their workflow.