Lessons we’ve learned after starting to work exclusively on IoT projects
summary
Hardware projects slow down product cycles, add hidden complexity and demand different tooling: firmware PDFs, vendor SDKs, long customs delays (prototype stuck two weeks equals a sprint), and supply chain ETAs like ETA 2028 that kill timelines. Bluetooth behavior varies across phones, debug loops are 2x longer, and QA needs more headcount. Telemetry is mandatory; mock devices and libraries such as Nordic iOS Bluetooth mock or blizzy speed development. A Raspberry Pi–based device-mimicking platform is under development to shorten integration time.
AI-written summary · about
chapters (14)
- 0:00Introduction and speaker background
- 3:55Focus shift to IoT and PxD
- 7:06Hardware complexity in IoT
- 13:10Communication challenges across teams
- 18:10Project setup and CI/CD in IoT
- 21:24Testing complexity with peripherals
- 24:36Learning curves and time estimation
- 26:45Bluetooth’s hidden complexities
- 28:52Prototyping and technical debt
- 30:59App lifecycle and background tasks
- 31:20Importance of telemetry in IoT
- 33:09Supply chain impact on projects
- 35:57Mock devices for faster development
- 37:41Closing remarks and contact info
related talks
48mHow Developers Can Prepare for IoT Standards
33mHow to Bring Your IoT Prototype to Production
27mIoT is hard, keep hustling
41mEVERYTHING IS BETTER WITH(OUT) BLUETOOTH
09mZephyr RTOS in Industry Research & Product Development
31mA Zephyr User Story
35mFail Fast IoT: accelerated innovation with cloud-powered hardware
46mDeep into the IoT Trenches: How to Build a Connected Product