Connected hardware: designing the box, the app and the brand as one launch
People don’t experience a connected device as hardware plus an app plus a brand. They experience one thing: the box arrives, they open it, they try to make it work, and then they either use it every day or put it in a drawer. Each of those moments is usually owned by a different team. Launches tend to fail in the gaps between them.
I’ve designed for three very different connected products: a weather station that timelapses your sky, an origami-inspired MacBook workstation, and a mesh WiFi system. They taught me the same lesson three ways. Design the box, the setup and the daily moment as one product and one launch, with one voice.
Three hardware stories
BloomSky (2013–2014) was a hyper-local weather station that did more than report the weather. It captured a timelapse of your sky every day, which turned weather data into a daily piece of art. I worked across the product, branding, photography and web.
Sparrow Dock (2014) was a workstation for the MacBook whose form came from origami fold logic. It started as an internal product-agency project and was released for crowdfunding. I designed the logo and identity, and the photography and video that told the fold story.
Plume (from 2016) was mesh WiFi at a time when almost nobody knew what that meant. Pods, packaging, app and brand all had to explain a new category while feeling effortless. The Plume brand and Plume app case studies cover that work.
The first five minutes
The first five minutes decide whether a connected product gets a second chance. They span three surfaces that rarely share an owner.
Packaging. At Plume, the original packaging presented the pods in sockets reminiscent of jewelry, with hexagons that pulled out like a drawer. Even the feel of the cable got design attention. That sounds excessive until you remember that the box is the first piece of interface a customer touches. It sets expectations for everything after.
Pairing. Setup is where most connected products lose people. The physical step (plug it in, place it, press something) and the digital step (find it, name it, connect it) must feel like one sequence. Every handoff between box instructions and app screens is a chance to get lost.
First value. The sooner the product does its thing, the better. A connected device should show that it’s working before the customer has to do anything else: a live reading, a first result, a visible sign that the system is awake. Silence after setup reads as failure.
Daily delight: making data feel like a reward
Once set up, a connected device has to earn its place every day. Utility is necessary and not enough. The products people keep using give them a small reward for looking.
BloomSky’s daily sky video was that reward. Weather numbers are useful, but a timelapse of your own sky is something you want to watch. The data became a daily moment, and the brand’s job was to frame it.
The general principle: find the moment in your data that people would look at even if they didn’t need to. Design the daily experience around it.
Educating a new category
In 2016, nobody had heard of mesh WiFi. Customers knew routers with bigger antennas and extenders that never quite worked. Explaining distributed WiFi, bands, channels and cloud optimization in full would have lost them.
We were selective about what to explain. Mostly we conveyed trust: it simply works. Where explanation was needed, we used friendly diagrams, often animated, and cinematic video. The best example is the question every customer asked: "how many pods do I need?" Instead of a measurement formula, we used an analogy: think of it like a lightbulb. Put one where you want WiFi, the way you’d put a light in a room.
That line had to work on the box, in the setup flow and in support conversations. Category education isn’t a marketing campaign. It’s a sentence the whole product repeats.
Launch creative in one voice
Hardware launches are compressed. Photography, video, the product page, packaging and early updates all land at once, often under a deadline that won’t move. The risk is that each piece is made by someone different and speaks differently.
For Sparrow Dock, the images sold the fold as a feeling, not a spec sheet, and the identity, the product page and even the apparel spoke with one attitude. For BloomSky, product, brand, photography and web came from the same small team. That coherence matters more than polish on any single asset. My photography practice ran through all of this work; for hardware, the image is often the first product experience.
Support is part of the launch
Connected products generate support conversations that pure software doesn’t: where should it go, why is it blinking, is it broken or is it my internet? Those conversations are part of the product experience, and they’re shaped long before launch.
The most effective support design happens upstream. Language that works on the box and in the app, like Plume’s lightbulb analogy for pod placement, also works in a support script, which means customers hear one consistent answer. Status lights and in-app states that match each other reduce "what does this mean?" calls. And setup flows that confirm success clearly ("you’re connected, here’s what happens next") prevent the anxious follow-up.
At Plume, the support side grew into a full product line of its own: portals and dashboards for service providers’ support teams. That work started from the same insight. A connected product’s quality is judged as much by how problems get resolved as by how rarely they happen. If I were planning a hardware launch today, the support script would be drafted alongside the packaging copy, by the same people, in the same voice.
What changes when the device has an agent in it
Connected devices are starting to include assistants that can act, not just report. That raises the stakes on everything above.
Today I’d design a connected product’s agent with the same one-voice discipline as the box and the app. When it acts on its own, like moving a device to a cleaner channel or adjusting a setting, it should say what it did and offer an undo. When it’s unsure, it should ask, not guess. And its tone should match the packaging and the brand, because to the customer it’s all the same product.
One launch, one voice
For connected hardware, the box, the setup flow, the daily moment and the brand are one launch. Give them one owner if you can and one voice regardless. I’ve written more about running product and brand as one system; hardware is where that idea is easiest to see and hardest to fake.
Related Product and brand as one system: what eight years at Plume taught meDesigning data-dense dashboards: role-based views that surface the next actionDeep-tech brand and product: making an invisible product visible