How To Build A Smartwatch: Software - Setting Expectations & Roadmap
2 days ago
- Pebble 2 Duo shipping: 70% delivered, 14% in transit, 16% shipped next week; sold out with no more production.
- Company operates with 5 full-time employees (vs. 180 previously) to ensure sustainability; prioritize core features and manageable growth.
- Software development trade-offs: core functions must work reliably, but bugs, rough edges, and occasional broken features are accepted; focus on stability over new features.
- Software roadmap priorities include: getting PebbleOS ready for Pebble Time 2, improving battery life from 17 to 30 days, adding language packs, quality-of-life improvements, PebbleKit Android, adjustable watch settings from mobile, notifications overhaul, developer SDK enhancements, voice assistant, and watchface generator.
- PebbleOS history: built on FreeRTOS with $15M+ investment and 20 firmware engineers; open sourced by Google in 2025 after Fitbit acquisition.
- Key PebbleOS strengths: constraints-driven creativity, efficient protocol, backwards compatibility, excellent SDK that enabled 10,000+ apps/faces, and community-driven development.
- Core plans: retain existing UI/UX, preserve backwards compatibility, replace old mobile apps with new open-source libpebble3 library, and add local speech-to-text.
- Firmware work includes supporting new microcontrollers (nRF52840, SiFli), reducing power consumption, and integrating Moddable JavaScript runtime.
- SDK improvements: web-based Pebble Cloud SDK (under 1 minute to start), new code examples, APIs for touchscreen/speaker, and easier app submission.
- Appstore enhancements: better discoverability, filtering non-working apps, highlighting new watchfaces, and exploring a donation subscription funnel for developers.