Do you design the hardware?

No. We design the product around it: the apps, the wearable experience, the commerce and the data platform, plus the decisions that cross between firmware and software.

We have an app and a device that do not feel like one product. Can that be fixed?

Usually yes, and usually without rebuilding either. The seams are normally in device states, pairing and data that disagrees between surfaces, which is a design and specification problem before it is an engineering one.

How do you handle devices already in the field?

They set the constraints. The plan has to carry versioning and migration from the start, because you cannot update every unit and the app has to keep working for all of them.

Connected products

IoT, mobile and wearables

Five products, 60+ countries, award-winning

A connected product is never one product. It is hardware, an app on two platforms, a wearable, a commerce layer, a data pipeline and a support burden, and the customer experiences all of it as a single thing with your name on it.

One system, not four projects

The usual failure is organisational. Hardware, firmware, apps and the web platform are built by separate groups on separate timelines, and the seams show up in the customer experience: inconsistent states, pairing that fails in a way nobody owns, data that disagrees between the app and the dashboard.

We design across the whole chain, so the decisions that cross boundaries get made deliberately by someone with sight of all of them.

Shipping into the physical world

Hardware is unforgiving. A firmware decision made casually in spring is a recall conversation in autumn, and the app has to support every unit already in the field. So the product plan has to carry versioning, migration and the long tail of devices you cannot update.

Add distribution: multiple territories, multiple languages, multiple retail and direct channels, and an analytics picture that has to make sense across all of them.

Where this comes from

The first IoT-enabled air quality ecosystem spanning iOS, Android and wearables, with the commerce and analytics platform behind it. Five products, sold in more than 60 countries, award-winning, and later acquired by a global consumer group.

Questions you may have

Do you design the hardware?: No. We design the product around it: the apps, the wearable experience, the commerce and the data platform, plus the decisions that cross between firmware and software.
We have an app and a device that do not feel like one product. Can that be fixed?: Usually yes, and usually without rebuilding either. The seams are normally in device states, pairing and data that disagrees between surfaces, which is a design and specification problem before it is an engineering one.
How do you handle devices already in the field?: They set the constraints. The plan has to carry versioning and migration from the start, because you cannot update every unit and the app has to keep working for all of them.

More capabilities

Get in touch

Talk to us about this kind of work.

Tell us what you are building and what makes it hard. A short note is plenty, and it comes straight to Juan and Andrew.

Start a conversation