It’s easy to forget in the run-up to launching your next product that development doesn’t (and shouldn’t) stop after devices go into production. Anticipating and addressing issues after launch is crucial to maintaining a product’s quality, reliability, functionality, and customer satisfaction. This means engineers must be able to quickly respond to unexpected issues, improve the product based on real-world feedback, and set the customer service team up for success. Join this discussion with our panel of embedded engineering experts who have spent decades bringing products to market and learn how they’ve handled challenges that arose post-launch. They have countless insights and best practices into how to be prepared once a product goes to market and will be discussing topics such as: - Developing a plan on how to test/qualify firmware updates or design changes - Handling returns and repairs, customer support, and feature requests - Best practice workflows for debugging issues and emergency situations - Monitoring device health, product quality, and feature usage in deployment Discussion Panel: 0:00 – 56:28 Q&A from live audience: 56:29– 1:08:32 Resources: - https://memfault.com/ - https://embeddedartistry.com/ - https://winterbloom.com/shop

Coredump #019 : END-OF-YEAR CELEBRATION: Moments You Loved, Stories You Missed, and 2026 Predictions
75 views

Coredump #018: Hidden Complexity of Sleep Tech: Power, Comfort, and 8 Hours of Reliability
75 views

Coredump #017: Building and Scaling a Startup in the Ultra-Competitive Health Wearables Market
120 views

Feature Highlight: Saved issue search and notifications
90 views

COREDUMP #016: From Startup to Global Brand: Scaling Engineering at reMarkable
145 views

COREDUMP #015: Developing kid-safe tech at Gabb: what it takes and why it’s so important
63 views