Service · App development

Custom IoT app development for your connected devices.

Custom apps for smart home, industrial IoT, fleet and asset tracking, smart buildings and Bluetooth devices. We build the mobile app, the web dashboard and the cloud backend that connect your sensors, machines and products to an interface your end users actually trust.

An IoT app is more than an interface: it is the top of a three-layer stack.

Internet of Things is the umbrella term for systems in which physical devices — sensors, machines, vehicles, buildings, consumer devices — are connected to a digital layer that displays, controls or orchestrates their data. For the end user, an IoT app is often the only visible part: the smart thermostat in the living room, the dashboard where a fleet manager tracks their vehicles, or the mobile app a maintenance engineer uses to read out a sensor on a machine.

Beneath that app, however, sit two layers that are just as crucial. The device layer is the hardware itself — sensors, actuators, controllers, sometimes a microcontroller with embedded firmware — and it determines which data is available at all and how reliable it is. The connectivity layer gets that data off the device: via Wi-Fi, Bluetooth Low Energy, LoRa, 4G, 5G or NB-IoT, and via protocols such as MQTT, CoAP or HTTP. Only on top of those two layers does the app layer sit — and that is where our core expertise lies.

We primarily build that app layer: a reliable mobile app, a web dashboard for administrators, a scalable cloud backend that ingests and analyses the device data, and the integrations that connect it all to your existing IT — from CRM to ERP to a maintenance management system. Where needed, we handle the device and connectivity layers together with hardware and firmware partners, so you have a single partner directing the entire project.

Our approach in four points.

App-first
We optimise for the end user, not for the hardware supplier
Cross-platform
iOS and Android from a single codebase using Flutter or React Native
Cloud-native
AWS IoT Core, Azure IoT Hub or GCP — depending on your stack
Secure by design
Device authentication, TLS, OTA updates and GDPR built in from sprint one

The IoT app projects we build.

IoT is broad — we are usually asked to build in three patterns. Almost every project is a combination of two or more.

Engagement 01

Consumer app for smart home and Bluetooth devices

End users, App Store and Google Play

A consumer app that lets your users control their thermostat at home, dim their lighting, view their security camera, or pair a Bluetooth product — such as a hearing aid, fitness device, BLE beacon or smart door lock. The core is a reliable onboarding flow in which the user discovers the device, connects it to their Wi-Fi network or phone, and can then operate it without hassle.

For BLE products — a growing segment in which we are increasingly in demand — we build the full Bluetooth handshake: scanning, pairing, GATT service discovery, characteristic read/write, notifications. That includes the edge cases that often cause problems in practice: reconnecting after the app has been in the background, a foreground service on Android for long-lived connections, and clear error handling when the connection drops. An app that keeps working even when the user is just out of range or briefly picks up their phone.

BLE pairingWi-Fi provisioningPush notificationsApp Store publicationMulti-deviceFamily sharing
Engagement 02

Industrial IoT and predictive maintenance

Machine monitoring for manufacturing and service

For manufacturers, machine builders and maintenance organisations that want to connect their machines to a mobile or web dashboard. The chain typically runs from an industrial sensor — vibration, temperature, energy, acoustics — via a gateway or PLC integration to a time-series database in the cloud, and from there to a dashboard that shows planners, engineers and management the same data in a form that suits their role.

We often connect this IoT platform directly to a maintenance management system and to wider manufacturing software: as soon as a sensor deviates from its baseline, an inspection task is created automatically in the CMMS. For machine builders with an installed base at end customers, we build a white-label app that lets their customers see the status of their installations themselves — a service layer on top of the product that adds value to maintenance contracts.

Vibration monitoringOPC UA / ModbusTime-seriesAnomaly detectionCMMS integrationWhite-label customer portal
Engagement 03

Fleet, asset and logistics tracking

Vehicles, containers, equipment and cold chain

For transport companies, equipment rental firms, infrastructure managers and logistics providers who want to track vehicles, containers, machines or high-value goods — not just by location, but by condition, usage and status. We build the mobile app for drivers and engineers, the web dashboard for planners and management, and the backend that combines GPS, telematics and sensor data into a workable whole.

For cold chain and pharma, temperature tracking with deviation alerts is a standard part of the build; for equipment rental, the focus is on usage hours, location and theft prevention. These projects almost always connect to your existing planning and invoicing systems — see also our page on fleet management apps and the broader topic of smart API integrations, which is how we build these integrations.

GPS trackingTelematicsCold chainGeofencingUsage hoursERP integration

What you have at the end.

A working IoT app in production — plus everything around it so you can manage, extend and scale it yourself.

Mobile app for iOS and Android

From a single Flutter or React Native codebase, or native where it's truly needed.

Web dashboard

For administrators, planners and management — the same data, a different role.

Cloud backend

Device ingestion, time-series storage, analytics and APIs for your stack.

Codebase + docs

Full source code, infrastructure as code and an architecture overview.

Management (optional)

Monitoring, OTA updates, security patches and ongoing development.

When a custom IoT app is the right choice.

Four patterns in which a standard platform gets stuck and custom software pays off — based on the projects we see in practice.

Hardware

Your device is your product

If you are bringing a physical product to market yourself — a smart thermostat, a BLE fitness device, an industrial sensor, a wearable — the app is an inseparable part of your brand. A rented dashboard from a platform provider has a different logo, different behaviour and different priorities from yours. Your own app gives you control over the end-user experience and keeps the IP within your organisation.

Integration

Deep integrations with your IT landscape

When an IoT installation needs to exchange data with your own ERP, CRM, planning, invoicing or maintenance system, standard IoT platforms often get stuck at the last mile. A custom backend with APIs that fit your existing systems exactly saves you from endlessly exporting data via intermediate steps.

Scale

Many devices, or many events per device

For consumer products with tens of thousands of active devices, or for industrial installations that generate thousands of events per machine per day, the choice between platforms such as AWS IoT Core, Azure IoT Hub or your own MQTT cluster becomes very concrete. It's up to us to weigh that decision together with your architect — with an eye on cost at scale, not just for the first thousand devices.

Compliance

Privacy or sector requirements that generic platforms don't cover

Health tech under the MDR, energy or water meters under sector regulation, smart buildings under the GDPR, critical infrastructure under NIS2 or IEC 62443: for IoT with sensitive data or safety implications, audit trails, data residency and device attestation are not optional. Custom software lets you make all of that explicit.

Modules that appear in almost every IoT app.

The building blocks we draw on — the combination and depth differ per project.

Onboarding

Device discovery and pairing

A user's first five minutes are crucial. A smooth onboarding flow — Bluetooth scan, Wi-Fi provisioning or QR code pairing — determines whether a user keeps using your product or puts it in a drawer. This includes clear error handling when pairing fails and a simple flow for adding a second device.

Real-time

Live updates and push notifications

Sensor values that update instantly without the user having to refresh, alerts when a threshold is exceeded, and push notifications on iOS and Android via Firebase Cloud Messaging or APNs. For industrial applications we use WebSockets or MQTT over WebSocket; for consumer apps it's usually push-driven sync.

Offline

Local cache and sync

A good IoT app stays usable in a tunnel, a lift, a remote meter cupboard or a factory hall with no coverage. That means a local cache of last-known values, a queue for outgoing commands, and conflict-free synchronisation as soon as the network returns. For BLE apps this applies to the Bluetooth connection itself too — the app needs to know what it can keep doing without a server.

Dashboard

Visualisation and history

Time-series charts for temperature, energy, running hours or vibration data; heatmaps for smart buildings; map views for fleet and asset tracking; role-specific dashboards for management versus operations. Custom where it matters, Grafana embed where standard is perfectly fine.

Auth

Users, roles and device access

User authentication via email, magic link, social login or SSO; role management for accounts with multiple employees; device sharing for consumer flows where several family members control the same device. Including an audit log of who touched which device and when.

OTA

Over-the-air firmware updates

For products with embedded firmware: an OTA update pipeline with integrity checks, a rollback mechanism and phased rollout. We typically build the cloud side and the app side of that pipeline; where needed, we handle the embedded firmware side together with a hardware or firmware partner.

Analytics

Time series, anomaly detection and rules

A time-series database — InfluxDB, TimescaleDB or AWS Timestream — as the foundation, with a rule engine on top that detects deviations from the baseline and takes action: a notification to the user, a work order in the CMMS, a webhook to your own system.

Integrations

APIs to your existing stack

REST and webhook integrations with your CRM, ERP, ticketing system, planning or invoicing. For industrial IoT, often in the other direction too: data from your production systems that enriches the IoT app with context — which product is currently running on this machine.

Security

Device auth, TLS and encryption

X.509 certificates per device for mutual TLS, encryption at rest and in transit, key management via AWS KMS, Azure Key Vault or HashiCorp Vault, and a security baseline based on IEC 62443 or the NIST IoT framework. Privacy by design for consumer data, GDPR-compliant logging for personal device data.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

How an IoT app project works.

01Introduction→ 02Device and architecture scan→ 03Build in sprints→ 04Rollout and management
Step 01

Introduction

A no-obligation conversation about your device, your end user and your existing IT. What data is there, what is missing, and who will need to work with it.

Step 02

Device and architecture scan

We model the chain: device, gateway, protocol, cloud, app. We choose the platform — AWS, Azure, GCP or your own MQTT — and define the interfaces with your existing systems.

Step 03

Building in sprints

A working app in 2-week sprints. We test early with real hardware rather than simulators — you only see BLE quirks and network edge cases on real devices.

Step 04

Rollout and maintenance

Phased rollout to production: first a pilot group of end users or a single installation. App Store and Play Store publication. Ongoing management and expansion.

What we integrate with and build on.

For each project we choose what fits your hardware, your scale and your existing IT. For the broader context of where this project fits, see our page on app development. For the overlap with service and maintenance software: manufacturing software.

App & frontend
FlutterReact NativeSwiftKotlinNext.jsReactBLE stack
Cloud & data
AWS IoT CoreAzure IoT HubGCP IoTMQTTInfluxDBTimescaleDBKinesis / Pub/SubGrafana
Connectivity & security
BLE / BluetoothWi-FiLoRaWANNB-IoT / 4G / 5GCoAPX.509 / mTLSOTA updatesIEC 62443

Frequently asked questions about IoT app development.

What exactly is an IoT app, and how does it differ from a regular mobile app?
An IoT app (Internet of Things app) is a mobile or web application that communicates, directly or indirectly, with physical devices: sensors, machines, vehicles, buildings or consumer devices. The difference from a regular app isn't in the UI but in the chain behind it: a device layer (the hardware), a connectivity layer (BLE, Wi-Fi, LoRa, mobile network) and a cloud backend for data ingestion and analysis. That makes building one more complex than a purely web-driven app, and places extra demands on offline behaviour, security and real-time updates.
Do you also handle the hardware and firmware, or only the app?
Our core focus is the app layer: mobile app, web dashboard and cloud backend. We don't do firmware and embedded development in-house, such as programming a microcontroller or designing a PCB. For projects where that is also needed, we work with established hardware and firmware partners we know well. That gives you a single point of coordination for the whole project, instead of two agencies working past each other. For projects where the hardware already exists, such as a Bosch sensor, a manufacturer's wearable or an industrial controller, we build on top of the existing protocols.
Flutter, React Native or native iOS and Android: what do you recommend?
For most IoT apps, Flutter or React Native are excellent choices: one codebase for iOS and Android, a faster turnaround, and by now excellent support for BLE, push notifications and background tasks. We opt for native (Swift for iOS, Kotlin for Android) when very deep integration with OS-specific features is needed, when performance requirements are very strict, or for Bluetooth cases where we need control down to the lowest level. We advise per project based on your device, your target audience and how you want to maintain the app, with no preference on principle.
How reliable is Bluetooth Low Energy in practice?
BLE is reliable in principle, but in practice there's a gap between the demo and a product that thousands of end users rely on for months. The difficulties lie in the edge cases: reconnecting after an app suspend on iOS, foreground services on Android for long-lived connections, handling multiple parallel devices, and reliable pairing across all phone models. That's why we always test on real hardware and on multiple physical devices, because simulators don't reveal these problems. A well-built BLE app never fails completely: if the connection drops, the user gets clear feedback and a recovery flow is immediately available.
Which cloud platform do you recommend: AWS IoT Core, Azure IoT Hub or GCP IoT?
All three are perfectly viable in production. We usually choose based on where your existing IT sits: if your organisation is already on Azure, IoT Hub is the obvious choice thanks to shared identity management and governance. For AWS shops, we almost always pick IoT Core in combination with Timestream or TimescaleDB. GCP IoT was elegant for a long time, but Google has since retired the managed IoT service, so these days we build on MQTT/Pub/Sub there. For projects with very specific scaling requirements, or a wish to keep data sovereignty closer to home, we sometimes host our own MQTT cluster with a European cloud provider.
How do you handle security and GDPR compliance for an IoT app?
Security is built into the architecture, not left to a final sprint. Our standard approach: per-device X.509 certificates for mutual TLS, encryption at rest and in transit, keys held in a managed keystore (KMS, Key Vault, Vault), an audit log of device and user actions, and an OTA update pipeline with integrity checks so you can patch firmware vulnerabilities. For GDPR: data minimisation as the starting point, a record of processing activities for device data, explicit consent flows in the app and, for large or sensitive projects, a DPIA. For industrial IoT we follow the IEC 62443 framework; for health tech and critical infrastructure we look at the relevant sector requirements.
What determines the cost of an IoT app project?
Four factors usually weigh the most: the number of device types the app must support (a single homogeneous flow versus several product lines), the complexity of the connectivity (purely cloud-driven, or BLE with an onboarding flow as well), the depth of the cloud layer (visualisation only, or also analytics, anomaly detection, OTA and multi-tenancy), and the integrations with your existing IT. A Bluetooth app for a single consumer product is a different project from an industrial platform with thousands of gateways, an ERP integration and compliance requirements. After a short scoping phase we give you an honest estimate. We don't publish a price list upfront, because without your context any figure is a guess.
How long until we can go live with a first version?
A well-defined first version, for example a consumer app with BLE onboarding for one product line, or an industrial dashboard on existing sensor data, can be running in a pilot within a few sprints. A broader project with multiple device types, its own cloud backend, an OTA pipeline and deep integrations takes several sprints. We always work in phases: first the core with a limited pilot group, then scaling up. Only once the core is running stably do we unlock the next layer.

Talk to us about your IoT app.

A no-obligation introduction of half an hour. We listen to your device, your end user and your cloud choice, and give you direction you can actually use, even if it turns out that a standard platform is the best route.

Edit content