Tagged connected-hardware
3 pieces
- · 6 min read
Edge or Cloud Inference: A Decision Table
This is usually argued on latency and cost, which are the two least decisive inputs. The questions that actually settle it are whether the system must work with no connectivity, whether the data can legally or contractually leave, and whether you can reach the device to fix what you got wrong.
- · 7 min read
The Update That Bricks the Fleet: OTA Failure Modes
An over-the-air update is the only operation where a bug can remove your ability to fix the bug. That single property should determine the entire design, and it produces requirements that look excessive until you consider what the alternative costs: a truck roll per unit, or a fleet you cannot reach at all.
- · 7 min read
Ship It Once, Reach It Never: Designing for Hardware You Cannot Touch
When a unit leaves the building, the set of decisions you can still change shrinks to almost nothing. The design question becomes which properties must be right at manufacture and which can be deferred, and getting that split wrong is the most expensive mistake in connected hardware because it is discovered across an entire production run at once.