Your Customers Judge the Hardware by Its App

0
min read
Smooth blue sphere resting on a light surface with a flowing, translucent turquoise ribbon-like shape extending behind it against a soft gradient background.

For a connected product, the app is most of what the customer touches: setup, control, updates, and on a lot of devices the only screen there is. So customers judge the hardware by the app, and when the app goes wrong the hardware takes the blame and the revenue hit. Sonos is the clearest proof, in its own filings. Companion app development has to be planned, funded and tested with the hardware, by people who will still be looking after it years after launch, and in our experience it is usually the line in the plan that starts last.

Why does the app decide how customers judge a device?

Because setup happens in the app, and setup is where connected products go wrong. Parks Associates' 2025 tracking of US households found 52% of people installing smart home devices themselves reported setup or connectivity issues, and its September 2025 research put difficulties with installation and configuration among the top three reasons for product returns. That is US data from a research firm that sells to the industry, but the shape will be familiar to anyone who has paired a speaker.

For many products the app is the only way in. The Veva home EV charger we built the app for has no screen, so installers commission it and owners control it entirely from their phones. Blackstar's Beam amps are controlled almost entirely from a phone too, and the reviews Blackstar quotes on its own product pages give the Beam app a line of its own: "The app is a gift that keeps on giving."

What happened at Sonos?

Sonos launched a rebuilt app on 7 May 2024 and, on the same day's earnings call, held its full-year revenue guidance at $1.6 billion to $1.7 billion. Three months later it cut that to $1.503 billion to $1.523 billion, set aside $20 million to $30 million to fix the app and win customers back, and held back two new products that "were ready to be shipped". By November its finance chief estimated the app had adversely affected revenue "by at least $100 million". The annual report lists what customers experienced: "missing features and performance issues, including trouble with set up and general unreliability". Sonos extended warranties by a year and paused share buybacks.

In January 2025 the board replaced the chief executive and gave his successor, Tom Conrad, a mandate "to improve the Sonos core experience for our customers". A month later Conrad told analysts that "so much of what we do that people perceive as hardware is actually software", and that Sonos had around 150 people in hardware and "more than double that" in software. Eighteen months after the launch, the 2025 annual report was still citing the app rollout as a reason revenue fell, and describing Sonos's software as the app, the firmware and the "cloud orchestration layer, which connects everything together".

Sonos's own diagnosis was speed and spreading too thin. The fixes it promised included setting quality benchmarks "at the outset of product development" and "introducing major changes to the app more gradually".

What happens when the app or the cloud is switched off?

The device loses whatever the app gave it. From 25 October 2025, Google removed the first and second generation Nest Learning Thermostats from its apps: no remote control, no notifications, no security updates, with the schedules still running on the wall. Belkin ended Wemo's cloud and app support on 31 January 2026, after which remote access and voice control stopped and new setup through the Wemo app became impossible.

Abandoned apps also keep running after nobody is looking after them. A September 2026 study of 61,500 IoT companion apps on Android that had gone at least two years without an update found security risks in 73.6% of them. It is a preprint, not yet peer reviewed, but it describes the other half of the same problem: when the maker stops paying for the app, the app does not stop.

What does the app have to keep up with that the hardware does not?

Every change Apple and Google make to how phones talk to devices. In five years the first screens of setup changed five times: iOS 13 required apps to explain why they need Bluetooth, iOS 14 added a prompt for local network access that every Wi-Fi device app now meets, Android 12 made Bluetooth scanning and connecting permissions the user has to grant at runtime, Android 13 did the same for nearby Wi-Fi devices, and iOS 18 introduced a new framework for discovering and setting up accessories. None of those changes touched the device's firmware, and every one of them meant an app update. That is why the app carries a running cost long after launch, which we publish as 15 to 20% of the build cost a year.

How should a hardware company plan companion app development?

As part of the product, from the first prototype. What that means in practice:

  • Build the app alongside the hardware, against prototype boards, so the protocol and the screens settle together. On Classeq's commercial dishwashers the app and the machines were developed in parallel, and the engineer app cut service time per unit by around 60%.
  • Design setup and pairing first, and test them on older handsets in every country you sell into.
  • Put the firmware update path in the first release, with fail-safes for a slow or dropped connection.
  • Plan for the cloud being unavailable. Veva's app walks the owner through reconnecting over a local hotspot when the charger drops off Wi-Fi, with no installer visit.
  • Make the engineer and installer side work offline (more in our post on offline mobile apps).
  • Release large changes to the app gradually, which is what Sonos now says it should have done.
  • Budget for the years after launch as well as the build.

Connected-device builds typically cost £40,000 to £100,000 excluding VAT and take 3 to 5 months. Our connected device and IoT page has the six products we have built apps for, from fire detector testers to a smart water bottle, and the sectors page shows where else that work sits. On the platform question, we build these cross-platform by default, for the reasons in our post on native vs cross-platform.

If you are building a connected product and the app is still the last line in the plan, get in touch.

What is a companion app?
An app that sets up, controls, updates or collects data from a physical device, usually over Bluetooth or Wi-Fi. For screenless products such as a home EV charger or a headphone amp, it is the main way the owner uses the device.
How much does companion app development cost?
Connected-device builds typically cost £40,000 to £100,000 excluding VAT and take 3 to 5 months. Running costs, covering support, maintenance and operating system updates, are typically 15 to 20% of the build cost a year.
Should the app be built at the same time as the hardware?
Yes. Building against prototype hardware lets the Bluetooth protocol, the firmware and the screens settle together, and avoids rework when the hardware changes late. It also means setup and firmware updates are designed in from the start.
What happens to a smart device if the company stops supporting the app?
It loses whatever the app provided. Google's first and second generation Nest thermostats lost app control in October 2025 but kept their schedules; Belkin's Wemo devices lost remote access, voice control and new setup when the app and cloud closed in January 2026.

Check out more articles

We build products that perform. Let's build yours.