Changing to a different image format may not be possible because WhatsApp still needs to show historical images, and these images are not stored on a central se

Changing to a different image format may not be possible because WhatsApp still needs to show historical images, and these images are not stored on a central server where they can be migrated. Also, it's called the "Android NDK" and not the "Android C SDK" - a big part of what the NDK gives you is not C-specific. It makes almost no difference whether you compile your code with GCC vs rustc, at the end of the day you're creating a native shared library and loading it from a java application. For example, these instructions from 2017 show how little work is involved https://mozilla.github.io/firefox-browser-architecture/experiments/2017-09-21-rust-on-android.html https://mozilla.github.io/firefox-browser-architecture/exper... and support has only improved since then. Using static analysis tooling on C/C++ code is more work than the above to set up, so I really do believe that Rust is the easiest way to reduce the chance of these kinds of bugs happening again.