It’s 2022. The pressure to deliver features in your Android apps and games faster than your competitor is huge. Luckily you’ve invested in an automated pipeline to roll changes to production, both your microservices and your apps! You have automated tests, feature flags and controlled rollout groups. Instead of doing heavy weight manual testing up front, you rely on the safety net these rollout groups provide. You rest on your laurels knowing this is vastly faster, cheaper, better than doing it the old fashioned way. All is well, right? Wrong! Although you limit their blast radius, you still have errors, crashes and ANRs and these are still affecting real users - the very ones you are trying to delight! It might make sense to risk churning a user from an opportunity cost perspective - but it’s far from ideal. In this session, we’ll take you through how you can make sure you reap the benefits from pushing changes to production often while minimizing the risk of annoying your loyal customers. We’ll explore the Backtrace SDK that you can use in your Android games and apps that allow you to detect, deduplicate and resolve NDK crashes, ANRs, and errors from your apps written in C, C++, Kotlin,