Industry guide · 12 min read ·
IoT and connected device app development
Before you brief a IoT app development company, it helps to know which parts of a IoT app are genuinely hard. This guide covers the market reality, the feature set that is table stakes, the three engineering problems that decide whether the product survives contact with real users, the compliance load, the numbers to measure, and what the work costs.
The market reality
In connected hardware, the app is the product's face and the return-rate lever. Most negative reviews of IoT products are about pairing, wifi provisioning and firmware updates — three things that are pure software problems.
Everything below follows from that. If a proposal you receive does not address it directly, the team has priced the screens and ignored the product.
The feature set that is table stakes
None of this differentiates you. All of it is required before anyone will take the product seriously, so it belongs in the v1 budget rather than the phase-two wish list.
- Guided pairing with honest failure messages and retry paths
- Wifi provisioning that handles captive portals and dual-band networks
- Over-the-air firmware updates with rollback and progress that never lies
- Live telemetry plus historical charts
- Multi-device, multi-user and household sharing
- Diagnostics screen support teams can actually read
The three problems that actually decide the outcome
BLE is unforgiving — Connection state machines, background reconnection, permission changes per OS version, and radio behaviour that differs by OEM. Test on a broad hardware matrix with the real device, not a simulator.
Firmware update safety — Interrupted updates must never brick hardware. Staged rollouts, checksum verification, resumable transfer and a recovery path are mandatory, and every one of them needs deliberate app UI.
Telemetry volume and cost — Decide sampling rate, on-device aggregation and retention early. Streaming raw sensor data to the cloud at full rate is how connected products end up with a cloud bill larger than their margin.
Compliance and risk
Product security expectations are rising fast — the EU Cyber Resilience Act, US labelling schemes, radio certification, and privacy rules covering telemetry that can identify a household.
Schedule compliance work in parallel with the build, not after it. Every team that treats it as a launch-week gate misses their date, and the fixes are architectural rather than cosmetic.
The numbers that matter after launch
Instrument these before you ship. A IoT app without measurement is a guess with a release cycle.
- First-time pairing success rate
- Firmware update completion and failure rate
- Support contacts per thousand devices activated
- Device reconnect success after network change
- Return rate attributable to setup experience
What it costs and how long it takes
Companion apps for connected hardware typically run $80,000 to $250,000. Pairing, provisioning and OTA account for far more of the effort than the dashboards do.
A realistic timeline is two to three weeks of discovery, three to five weeks establishing design and core flows, then eight to fourteen weeks of build and QA before a production launch. Parallelising design and engineering after the first flows are settled is what keeps that schedule honest.
Recommended stack
Native iOS and Android — BLE, background execution and permissions are too platform-specific to abstract safely — over an MQTT or equivalent telemetry backend.
The right answer depends on your roadmap, not on what a vendor staffs most easily. Ask any firm to justify its recommendation against the specific hard problems above.
Choosing a IoT app development company
Ask for a shipped product in this category that you can install today. Ask which named engineers will work on yours. Ask how they handled the three hard problems above on that project, specifically. Then ask what they would do differently now.
WVE Labs is a digital product company founded in 2015. Product strategy, design and engineering sit under one roof, and mobile has been at the heart of the studio for more than a decade — it remains one of our deepest areas of expertise. We have delivered for startups, growth companies and established organisations including Sony, Honda, Guardian, Marriott, USC, Maui Jim and California State University. Engagements start at $25,000.
- A live, installable product in this category
- Named senior engineers, available before contract
- A specific answer to each hard problem above
- Weekly demos on a working build, not status decks
- Full ownership of code, cloud accounts and store listings
The takeaway
The difference between a IoT app that works and one that quietly dies is almost never the interface. It is dispatch logic, data pipelines, offline behaviour, compliance and measurement — so brief for those, and hire the team that talks about them unprompted.