Reference Products: A middle path between build vs. buy for IoT P
summary
Particle claims a middle path: packaged open-source hardware plus hosted services that cut DIY risk and off‑the‑shelf rigidity. It ships a finished product Tracker One, an open SOM with an m8 port for add‑on sensors, and cloud tracking services with configurable features and smart defaults. Device firmware is open Device OS LTS and dev tools include a web IDE, VS Code extension and CLI. Early results: about one third of new customers pick the ready unit, reporting faster time‑to‑market and tens‑of‑thousands saved on services.
AI-written summary · about
chapters (22)
- 0:00Intro
- 0:37About Will
- 1:25Benefits of Open Source
- 2:19What is Particle
- 3:43Open Source
- 6:37DIY vs Buy
- 9:32Why most IoT initiatives fail
- 11:21IoT accessibility
- 12:38IoT accessibility constraints
- 14:42Empowering organizations
- 15:30What are reference products
- 18:55Reference product consumption models
- 20:56Hardware consumption models
- 22:14Adding sensors
- 24:09Device management configuration
- 25:31What does this all mean
- 26:53Open reference products
- 28:18Benefits of reference products
- 29:02Con of reference products
- 30:31Summary
- 34:38Backtrack
- 37:29Dev Tools
related talks
18mBuild, Buy, or Modify? Making Smarter Hardware Choices for LoRaWAN Integration
14mExploring IoT device implementation strategies
16mEnterprise IoT software: Build vs. buy
03mpacks IoT in a box
18mReality Check on Total Cost of Ownership in Asset Tracking
35mEnd-to-end IoT Development with Zephyr
33mHow to Bring Your IoT Prototype to Production
30mOffline IoT - Building Resilient Connected Devices without the Internet