Ajesh Pai

This session provides a practical, low effort steps to inspect and improve performance. - We will start with why you should care about performance - Look at the benefits of R8 - We will enable R8, and intentionally trigger a common crash (e.g., from reflection). - Use R8's tools like retrace to de-obfuscate the stack trace and find the true root cause. - Analyze R8's configuration path and output files (like configuration.txt) to understand why R8 removed the specific class or method. - Write a specific, narrow keep rule that fixes the bug without unnecessarily bloating your app. - Look at how to test R8 enabled builds - Add Profile guided optimizations to improve startup performance - Wrap it up This session will give you the tools and confidence to diagnose any R8-related issue and write precise, efficient keep rules. Attendees will leave this session knowing how to: - Implement R8 in a new or existing Android project correctly. - Debug minified apps by de-obfuscating stack traces to find the real source of a crash. - Analyze R8's build outputs to understand what code was kept, removed, and why. - Identify the root cause of common R8 issues, especially those related to reflection, serialization, or JNI. - Write effective, narrow keep rules that target the specific problem instead of using broad rules that harm optimization. - Verify R8's configuration to ensure your rules are being applied as expected and are having the intended effect. - Implement Profile guided optimizations