The Space Between
Most hardware companies pour their budget and attention into two things: the physical product and the companion app.
Industrial designers obsess over form, ergonomics, and how the device fits into someone’s life. Digital designers obsess over flows, brand expression, and how the app feels. Both are essential, but neither discipline, on its own, guarantees the product experience will hold up.
The second a customer opens that box we spend so much time obsessing over and powers on their shiny new thing, they aren’t just interacting with a device or an app. They are stepping into a designed ecosystem: charging, pairing, syncing, over-the-air updates, and the error states we never thought they’d hit.
One rough edge and that holy-shit-this-is-awesome moment turns into broken, fast (ask anyone who watched pairing fail on step 2 or 3 or had to do a forced firmware update standing in the dirt). The real test of hardware is not the device or the app. It’s the space between them.
The Seams That Break Products
The fastest way to kill a hardware and software product isn’t bad industrial design or a janky app experience. It’s the seams no one designed. The Bluetooth pairing that dies at the BLE handshake or permissions step. The dead battery a user wasn’t warned about. The firmware update that bricks a device in the field.
It only takes one of those moments for a product to go from cool to unreliable. Once users lose trust, it almost never comes back.
Most customers don’t care if a product is from a company that’s the new early stage startup hotness or a BigTech™ behemoth with bottomless pockets. They compare it to the most polished thing in their pocket: Leica, WHOOP, Oura, Nest, and yes, Apple. That’s the bar whether we like it or not.
Design Beyond the Surface
Too often, design gets framed as surface polish. The reality is broader.
When design is only surface polish, shit breaks. When design is seen as the craft of the whole experience, products feel inevitable.
The best products aren’t the ones with the flashiest features. They are the ones that make failure states invisible.
WHOOP makes firmware updates insanely fast and disappear into the background. Most updates feel invisible, which is the point.
Oura is gorgeous and discreet, but if Bluetooth drops mid-sync the ring feels dead until the app recovers. With no on-ring feedback, you’re waiting on the app to recover.
Withings builds beautiful watches and scales, but fragile pairing and sketchy profile recognition can crush the experience. Step on the scale and your weight doesn’t sync? That is a dealbreaker. My Withings scale is now just a dumb scale with a nice display. Ain’t nobody got time to troubleshoot that.
Drones are awesome. DJI delivers a really magical flight experience with live video, until you are grounded in the field by a forced firmware update. Or worse, your controller app freezes mid-flight because the cable slipped or wireless dropped.
Insta360 nails app-first reframing and editing, but wireless transfers are slow and what media is on the phone and still on camera isn’t crystal clear.
Camera apps across the board still bury fresh clips deep in your library because of timestamp drift (clock drift, bad RTC, no recent sync) when the device clock has not been synced. That tiny metadata bug makes users think their footage disappeared. Leica is raising the bar here and that’s an entirely other post worth writing at some point.
These aren’t random bugs. They are symptoms of design blind spots. When no one owns them, users pays for them.
How to Fix the Seams
When you design the seams on purpose, you buy yourself three things:
Trust: Users believe your product just works.
Efficiency: Your team stops firefighting preventable issues.
Time: You get to build the next feature instead of writing support docs.
It doesn’t take miracles. It just takes intention.
Firmware updates. Download quietly in the background over Wi-Fi, verify, then install on user time. Prompt only when it is time to install, not when your customer is standing on a trail about to shoot.
Media libraries. Assume non-sequential timestamps are unreliable, group clips by import session. Show “Recently Captured” instead of forcing users to dig through misfiled metadata. Also, offer a quick ‘Sort by import’ toggle. It saves lives.
Battery cues. Do not depend solely on app notifications. Build lightweight, proactive on-device signals such as LEDs, haptics, so customers are not blind when their device dies.
Pairing flows. Treat failure states like first-class citizens. Don’t just say “Pairing failed.” Tell them if it was permissions, Bluetooth off, or token exchange, then auto-retry.
None of these fixes will make a marketing or pitch deck sexier. They will make your product feel inevitable.
Inevitability is the whole game because the truth is most users forgive ugly. They don’t forgive broken.
Who Owns This Work
The seams fall into a blind spot because no single discipline is clearly responsible for them.
Product defines what gets built, but they’re not designing the lived experience.
Engineering explores what is possible, implements, often patches over gaps, but they aren’t accountable for how it feels.
Industrial and digital designers go deep in their respective domains, but the in-between sometimes slips through the cracks.
The seams need explicit ownership. Product design at the ecosystem level. The person or team responsible for how the entire experience comes together across device, firmware, and app.
At GoPro, when I worked on the hardware team, there was a small design team that sat between industrial design, firmware, and app. They looked across the whole flow, from pairing in the app to button layouts, haptics, and what shows up on the device screen. It’s rare to see a team explicitly tasked with that layer. Even then, some seams were hard to smooth, which tells you how challenging this work is.
If nobody’s accountable for this layer, a product can feel accidental. Accidental isn’t a strategy.
The Payoff
Companies that invest in seam design early buy themselves three unfair advantages:
They ship with fewer recalls, returns, and one-star reviews.
They look bigger than they are, because the seams make their product feel world-class.
They attract better teams and investors, because people want to work on products that work.
Getting there isn’t instant. Designing at the seams takes extra cycles up front. It forces us to slow down and think through the failure states that most teams gloss over and the lates AI vibe-coding tool will likely ignore. That time isn’t wasted. Every edge case we anticipate now saves ten customer support tickets later, an expensive RMA we didn’t need, and ten times the trust in the market.
This isn’t just about good design practice. It is about survival.
The Space Between Is the Product
Hardware matters. Software matters. But neither matters if the space between them is broken. That space is where trust is won or lost. It is where products stop feeling like prototypes and start feeling inevitable. The founders who invest in that layer are the ones who build companies that last. If you want staying power, start here.