You're expected to deliver your IoT and edge devices on time. Once shipped, your customers expect the devices to work perfectly 100% of the time with regular updates that deliver new features. How can your product and engineering teams meet your deadlines and the growing demands of your customers? In this recorded webinar, Memfault CEO François Baldassari discusses how to utilize reliability engineering techniques to de-risk product launches and ship on time.

Building a management system for your IoT devices is a time-intensive, expensive, and difficult process. And once you build it, you're not done. Maintaining and updating the solution will continue to take up time and resources that will only increase as you scale the number of deployed devices. During this webinar learn how to employ reliable systems that won't break once you scale. Our speakers will cover.

Customers and business leaders expect bug-free products that work 100% of the time, but as a firmware engineer, you know that shipping a bug-free product is near impossible. Instead of trying to test every possible scenario before you ship, you need to focus on how you'll debug issues once your devices are in the field.

NXP and Memfault have collaborated to give IoT device manufacturers in-field device monitoring, crash reporting, and updating capabilities for faster product development, improved device operation, and reduced direct resource costs. Together, Memfault and NXP are helping IoT developers build smart cities, smart homes, IIoT, and automotive devices to save time and ease the worry of triaging and troubleshooting, allowing them to focus on building value-added features.

About the webinar: Executives and customers expect IoT devices to be delivered on time. And once they are shipped, they expect the devices to work well, last for a long time, and get regular updates that deliver new and unique features. How can product teams meet their deadlines and the growing demands of their customers? In this recorded webinar, Memfault CEO François Baldassari discusses how you can ship your devices on time (or even earlier) without sacrificing quality.

As embedded development teams build IoT products, there are often questions about what visibility they'll have into devices once they are in the field. How are the devices performing? Is battery power lasting as long as we planned and marketed? What caused this connectivity issue and how do we fix it? What features are customers using most? To properly assess the value of past and future product investments, embedded developers need to implement diagnostic capabilities that help monitor critical metrics that give them insight into overall fleet performance.

The Memfault Android OS SDK allows IoT developers to collect detailed diagnostics from Android devices on everything from low-level hardware or kernel issues to high-level application crashes, and automatically upload them to Memfault. In this webinar, Heiko Behrens introduces the Memfault AOSP SDK (support for Android 8 to 12) and covers these new features in the latest release (v4.0): Presentation: 0:00 – 44:25 Q&A from live audience: 44:26 – 58:54

The Memfault Android OS SDK allows IoT developers to collect detailed diagnostics from Android devices on everything from low-level hardware or kernel issues to high-level application crashes, and automatically upload them to Memfault.

When bugs inevitably make their way into production firmware, defensive programming practices give you peace of mind that your devices will keep running despite issues occurring in the background. However, defensive programming can lead to more issues than it solves if not used carefully. Often the better approach to take is to use the practice of offensive programming, which will help surface issues more quickly and easily and help you iterate towards bug-free firmware and a better overall product experience.

Even when you think there are no bugs in your fleet of Android OS devices, huge issues can come up at any time. How do you find and fix those issues before your customers notice them? With full device observability, you'll never have to worry about even the most high-impact bugs affecting your IoT devices in development or production.