Coredump Sessions
Coredump Sessions
Podcast Description
Coredump Sessions is a podcast for embedded engineers and product teams building connected devices. Hosted by the team at Memfault, each episode features real-world stories and technical deep dives with experts across the embedded systems space.
From Bluetooth pioneers and OTA infrastructure veterans to the engineers who built Pebble, we explore the tools, techniques, and tradeoffs that power reliable, scalable devices. If you're building or debugging hardware, this is your go-to for embedded insights.
Podcast Insights
Content Themes
The podcast focuses on various aspects of embedded engineering, featuring topics like open-source firmware, Bluetooth technology, and device scalability, with episodes such as the discussion around the open-sourcing of Pebble OS and its implications for developers and the industry.
Coredump Sessions is a podcast for embedded engineers and product teams building connected devices. Hosted by the team at Memfault, each episode features real-world stories and technical deep dives with experts across the embedded systems space.
From Bluetooth pioneers and OTA infrastructure veterans to the engineers who built Pebble, we explore the tools, techniques, and tradeoffs that power reliable, scalable devices. If you’re building or debugging hardware, this is your go-to for embedded insights.
In this Coredump Session, Tyler Hoffman joins us as host and Yoto co-founders Ben Drury and Filip Denker shared how they built one of the fastest-growing brands in kid tech around a simple idea, a screen-free audio player designed for real family life. They discussed how feedback from kids shaped key hardware decisions across multiple generations of devices, and how the team balanced durability, battery life, and connectivity as Yoto scaled globally. The conversation also explored how their approach to device monitoring and updates evolved alongside their growing fleet.
Key Takeaways
- Yoto built its product around a deliberately constrained experience: no screens, no ads, no microphones, and controls simple enough for a two-year-old to use independently.
- The company treated audio content as the core product, combining licensed entertainment, music, podcasts, and interactive experiences to drive long-term engagement.
- Early prototypes were built with Raspberry Pi hardware to validate real-world usage quickly before investing in custom production hardware.
- Children became the primary usability test group because their behavior immediately exposed friction points and design flaws.
- Hardware constraints drove innovation. Limited controls and minimal inputs forced the team to create more intuitive product interactions.
- Yoto evolved through multiple hardware generations as real-world family usage exposed challenges around durability, connectivity, and battery performance.
- Device observability and fleet monitoring became increasingly important as Yoto scaled globally and needed visibility into issues occurring in the field.
- OTA update strategy matured alongside fleet growth, helping the team manage reliability improvements and software iteration remotely.
- Regulatory complexity around connected kid devices continues to increase, particularly around cybersecurity and children’s data protections.
- Community became a major product advantage, with parents contributing feedback, creating custom content, and shaping future product improvements.
Watch this episode on YouTube [ADD Playlist YT Link from here)
Follow Memfault
Other ways to listen:
Disclaimer
This podcast’s information is provided for general reference and was obtained from publicly accessible sources. The Podcast Collaborative neither produces nor verifies the content, accuracy, or suitability of this podcast. Views and opinions belong solely to the podcast creators and guests.
For a complete disclaimer, please see our Full Disclaimer on the archive page. The Podcast Collaborative bears no responsibility for the podcast’s themes, language, or overall content. Listener discretion is advised. Read our Terms of Use and Privacy Policy for more details.