
Not only that, but they can crash the JVM (Java Virtual Machine) before returning control to the Java/Kotlin code. But crashes on the native side (i.e in low-level C/C++ code) are often complicated and hard to understand. If you’ve worked on any of those 100 applications, or on similar large applications, that’s a lot of opportunity for something to go wrong!Īndroid developers should be comfortable debugging native crash stack traces (“tombstones” in Android-speak). And 85% of those apps contain native code with 1000+ individual native libraries.


The 100 most popular Android applications have been installed 54 billion times (as of December 2018).
