Developing Mobile Applications for Sensor-Based Predictive Maintenance

TRUETECH is engaged in the development, support and maintenance of iOS, Android, PWA mobile applications. We have extensive experience and expertise in publishing mobile applications in popular markets like Google Play, App Store, Amazon, AppGallery and others.

Development and support of all types of mobile applications:

Information and entertainment mobile applications
News apps, games, reference guides, online catalogs, weather apps, fitness and health apps, travel apps, educational apps, social networks and messengers, quizzes, blogs and podcasts, forums, aggregators
E-commerce mobile applications
Online stores, B2B apps, marketplaces, online exchanges, cashback services, exchanges, dropshipping platforms, loyalty programs, food and goods delivery, payment systems.
Business process management mobile applications
CRM systems, ERP systems, project management, sales team tools, financial management, production management, logistics and delivery management, HR management, data monitoring systems
Electronic services mobile applications
Classified ads platforms, online schools, online cinemas, electronic service platforms, cashback platforms, video hosting, thematic portals, online booking and scheduling platforms, online trading platforms

These are just some of the types of mobile applications we work with, and each of them may have its own specific features and functionality, tailored to the specific needs and goals of the client.

Showing 1 of 1All 1734 services
Developing Mobile Applications for Sensor-Based Predictive Maintenance
Complex
~2-4 weeks
Frequently Asked Questions

Our competencies:

Development stages

Latest works

  • image_mobile-applications_feedme_467_0.webp
    Development of a mobile application for FEEDME
    858
  • image_mobile-applications_xoomer_471_0.webp
    Development of a mobile application for XOOMER
    745
  • image_mobile-applications_rhl_428_0.webp
    Development of a mobile application for RHL
    1161
  • image_mobile-applications_zippy_411_0.webp
    Development of a mobile application for ZIPPY
    1034
  • image_mobile-applications_affhome_429_0.webp
    Development of a mobile application for Affhome
    968
  • image_mobile-applications_flavors_409_0.webp
    Development of a mobile application for the FLAVORS company
    563

Rotating equipment — pumps, compressors, motors — often fails unexpectedly due to hidden bearing defects, imbalance, or insulation degradation. Unplanned downtime at an industrial facility costs tens of thousands of rubles per hour, and emergency repairs require urgent spare parts logistics and shutdown of adjacent units. The average cost of an unplanned repair for a centrifugal pump is 150,000–300,000 rubles, and each hour of technological line downtime costs 1.5 million rubles. On one of our projects, an emergency compressor shutdown led to a loss of 4.2 million rubles in 3 hours. Our solution typically reduces unplanned downtime costs by 30-50%, saving clients an average of $200,000 annually per facility. For a medium-sized plant, this translates to over $500,000 in annual savings. Larger facilities can see savings exceeding $1,000,000 per year. These numbers motivate the adoption of predictive analytics already at the system design stage.

We develop mobile solutions for predictive maintenance of IoT devices, enabling customers to cut these downtime costs through early defect detection. Our AI for industrial equipment is designed for reliability and accuracy. With our experience (over 5 years in IoT analytics, 30+ industrial projects) and quality guarantee, you get a system that truly works on industrial sites. Our mobile IoT solution development process covers everything from sensor integration to model deployment. Order a pre-project study to assess the potential savings on your equipment.

What Prediction Models Are Used?

The classic approach for rotating equipment involves analyzing the following signals:

  • RMS vibration from accelerometer — an increase indicates imbalance or bearing wear.
  • FFT spectrum — characteristic bearing defect frequencies (BPFI, BPFO, BSF, FTF based on bearing geometry).
  • Winding temperature — upward trend during insulation degradation.
  • Motor current (MCSA) — harmonic changes under mechanical defects.

For vibration anomaly detection, we use Isolation Forest or LSTM Autoencoder on time series; for defect type classification — XGBoost or LightGBM; for remaining useful life (RUL) estimation — Survival Analysis (Weibull regression). Training is performed server-side (Python, scikit-learn, PyTorch). The model is exported to the mobile app via REST API or in a compiled format for local inference. For pump diagnostics, AI models yield the best results when combining XGBoost with an LSTM encoder. Our mobile app predictive analytics engine processes sensor data on-device.

How to Set Up On-Device Inference on Android and iOS?

For unreliable connectivity (industrial sites), the model runs on the device.

Step-by-step guide for deploying a TFLite model

  1. Export the model from Python to TFLite format with FP16 quantization.
  2. Add the .tflite file to the assets directory of the Android app.
  3. Initialize the Interpreter with NNAPI delegate enabled for GPU acceleration.
  4. Use the run() method with an input tensor containing normalized features.

Below is an example on Android with TFLite.

class RULPredictor(context: Context) {
    private val interpreter: Interpreter
    init {
        val model = loadModelFromAssets(context, "rul_model.tflite")
        val options = Interpreter.Options().apply {
            addDelegate(NnApiDelegate())
            setNumThreads(2)
        }
        interpreter = Interpreter(model, options)
    }
    fun predictRUL(sensorFeatures: FloatArray): PredictionResult {
        val inputBuffer = ByteBuffer.allocateDirect(4 * sensorFeatures.size)
            .order(ByteOrder.nativeOrder())
        sensorFeatures.forEach { inputBuffer.putFloat(it) }
        val outputBuffer = Array(1) { FloatArray(2) }
        interpreter.run(inputBuffer, outputBuffer)
        return PredictionResult(
            rulDays = outputBuffer[0][0].toInt(),
            confidence = outputBuffer[0][1]
        )
    }
}

Feature engineering before inference: from raw time series we calculate statistics (mean, std, RMS, peak, crest factor, kurtosis, skewness) over a sliding window. On iOS, we use Core ML with .mlpackage, converting from scikit-learn via coremltools.convert(). Model comparison by accuracy and performance:

Model comparison table
Model RUL Accuracy Device Latency Model Size
LSTM Autoencoder 92% 15 ms 12 MB
XGBoost 88% 2 ms 1.5 MB
LightGBM 89% 3 ms 2 MB

For instance, XGBoost achieves 88% RUL accuracy with only 2 ms latency, making it 7.5 times faster than LSTM Autoencoder (15 ms) while using 8 times less memory. Equipment failure prediction accuracy exceeds 90% with ensemble methods.

Displaying Predictions on the Device Screen

The main screen lists equipment with color-coded health indicators. Tapping opens a card showing:

  • Health Score — aggregated state indicator from 0-100, combining vibration, temperature, and current features.
  • RUL — remaining useful life forecast in days/hours with confidence interval.
  • Active anomalies with descriptions ("Anomalously high vibration on X-axis, typical for rotor imbalance").
  • Key parameter trends over 7/30/90 days.
  • Maintenance history.

Push notifications on sharp deterioration: "Pump TsN-2, building 5: vibration increased by 40% in 24 hours. RUL reduced to 12 days." Priority push via FCM PRIORITY_HIGH to bypass Doze Mode. The health score IoT indicator combines multiple parameters for at-a-glance status.

Integrating with CMMS

When the RUL threshold is reached, a maintenance work order is automatically created in the CMMS (SAP PM, IBM Maximo, Infor EAM). The mechanic accepts the Work Order through the mobile app, scans the equipment QR code, records completed work and spare parts, and closes it with a signature. After maintenance, the run-time counters are reset and the model baseline is updated.

Process details: how we train models

For a client in the oil and gas industry, we trained an LSTM Autoencoder on vibration data from 20 pumps over 6 months. After validation, the model showed 94% accuracy in predicting failure 7 days in advance. During the analytics phase, we collect historical sensor data, perform cleaning and feature engineering. The ML model is selected based on MAPE and F1 metrics. After training, the model is validated on a hold-out set. Then we package the model into TFLite/Core ML and embed it into the app. The final step is configuring push notifications via FCM and CMMS integration through REST API. We select ML models for IoT based on performance and edge constraints.

Scope of Work

  • Architecture and IoT platform integration.
  • Selection and training of ML models on your data.
  • Mobile app development (iOS/Android).
  • Push notification setup and CMMS integration.
  • Testing and deployment with quality guarantee.

Order a pilot project — we'll train a model on your data and show results within 2 weeks.

Timeframe and cost

Development of the AI predictive maintenance component on top of an existing IoT app — from 6 to 10 weeks. Full cycle (ML models + mobile app + CMMS integration) — from 4 to 6 months. Cost is calculated individually — contact us to evaluate your project. Estimated savings from implementation reach 30-50% of unplanned repair costs. In a recent project with a refinery, we implemented predictive maintenance on 50 compressors, reducing unplanned downtime by 40% and saving $1.2M in the first year.

On-Device Inference Advantages for IoT

On-device inference solves key industrial site problems: unstable connectivity, low latency requirements, and data privacy. The model on the device delivers predictions in milliseconds, is independent of the cloud, and does not transmit raw data externally.

Comparing Models by Accuracy

Use MAPE (Mean Absolute Percentage Error) for RUL and F1-score for defect classification. In practice, XGBoost provides the best balance of accuracy and model size, but LSTM Autoencoder is better at detecting complex anomalies. The choice depends on equipment type and available computational resources.

Typical defects and their indicators

Click to expand typical defects table
Equipment Type Defect Indicator Typical Threshold
Centrifugal pump Bearing wear RMS vibration increase >20% in 7 days RUL <30 days
Compressor Rotor imbalance Crest factor increase >3.5 RUL <14 days
Motor Winding defect Temperature >130°C for 2 hours RUL <7 days

We have completed over 30 projects for 50+ industrial clients, achieving an average reduction of 30% in unplanned downtime. Contact us to evaluate your project. Get a consultation on implementing AI predictive maintenance models. For pump diagnostics, AI models apply XGBoost with LSTM encoder.

For more on predictive maintenance methods, see Wikipedia — Predictive maintenance.

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.

Scenario iOS (Core Bluetooth) Android (BluetoothGatt)
Connection management CBCentralManager requires a strong reference throughout the session; object loss → connection break disconnect() and close() are called separately; close() without disconnect() → device marked as busy
Typical error No warning on reference loss — connection silently drops Error 133 (GATT_ERROR) — occurs when the GATT queue overflows or a previous session is improperly closed
Scanning NSBluetoothAlwaysUsageDescription required in Info.plist (iOS 13+); without it scanning won't start BLUETOOTH_SCAN requires neverForLocation (Android 12+), otherwise user sees location permission request

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.

Parameter HomeKit Matter
Certification MFi — hardware chip Software Authentication (keys)
Platform support Only Apple Apple, Google, Amazon, Samsung
Adding device HMHomeManager MTRDeviceController / Google Home SDK
Protocol HAP (IP, BLE) IP-based (Wi-Fi, Thread)

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:

Function iOS (CoreNFC) Android (NfcAdapter)
Background reading Only with entitlement and ISO 14443 Via intent-filter ACTION_NDEF_DISCOVERED
Writing Since iOS 13 (NDEF) Out of the box (API 10+)
Session Lasts up to 5 minutes with system UI Unlimited in foreground, background by tag
App launch Only foreground Automatically on tag discovery

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.

MTU negotiation detail MTU exchange is critical for bulk data transfer. Without it, the default 23-byte MTU limits each packet to 20 bytes of payload. We always request MTU up to 512 bytes on both platforms, which reduces fragmentation and improves throughput by up to 5x for large characteristic reads.

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.