Notes from the bench.
What we learn designing boards and writing firmware: the decisions, the trade-offs and the failures worth knowing about before you make them.
Do I need a custom PCB for my product?
When an off-the-shelf development board is enough, when a custom PCB is worth the investment, and how to move from one to the other as a product develops.
Read the post →How to choose an electronics development company
What to look for in an engineering partner: hardware and firmware under one roof, prototype capability, manufacturing support, deliverables, IP ownership, and the fifteen questions to ask before you sign anything.
Read →How to turn an electronic product idea into a working prototype
The path from an idea to hardware that works: requirements, electronics, firmware, prototype, test, refine and production, with what happens at each stage and what you need to know going in.
Read →How much does it cost to develop a custom electronic product?
Indicative budgets for each stage of electronic product development, covering concept, proof of concept, prototype, MVP and production, plus what actually moves the number.
Read →Why your board works on the bench and fails in the field
Brown-out, decoupling, ESD and thermal margin are the four reasons a working prototype misbehaves once it ships. How to find each one before manufacture, not after.
Read →