Operations | Monitoring | ITSM | DevOps | Cloud

Product quality doesn’t stop when your devices are deployed. In fact, that’s when it matters most. And yet even with rigorous testing, all bets are off once your product hits the field. It’s impossible to anticipate every variable and environment your devices will encounter. So how can you make sure your customers continue to love your product—not only on day 1, but 6 months down the road? Find out exactly how to get the data you need to guide your team’s development decisions and deliver products that perform in the real world.

In this feature highlight video we provide a short overview of some of the updates we have made to dashboards and charts in Memfault.

In this feature highlight we take a look at our two, newly released chart types. Crashiness and reboot reasons.

In this video we take a look at the newly released Processing Log. The processing log is designed to give developers working with Memfault an extra level of visibility into any errors happening on the Memfault server side to help them more quickly debug any issues. You can read more about the processing log in our documentation.

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.

Listen to Dave's advice to anyone who is building a new IoT product. He specifically discusses how you should get started and what metrics to track.

In this clip, Dave discusses how Latch balances what new features to develop while also considering how to improve what already exists.

In this video we take a look at the newly released Processing Log. The processing log is designed to give developers working with Memfault an extra level of visibility into any errors happening on the Memfault server side to help them more quickly debug any issues.

Dave describes how he and his team feel after shipping a firmware update and having the data flow into Memfault. The quick summary: The Latch team sleeps quite well after shipping an update.

Ensuring high product quality & reliability extends beyond lab testing. Field conditions and ever-changing device ecosystems require continual adjustments for seamless connectivity, optimal battery life, and sustained interoperability. A robust pipeline to capture, analyze, and alert on device reliability data is critical to maximize yield, optimize performance, and stay ahead of problems that emerge in the field.