> C++ libraries etc We do have limited resources, so we have to prioritize what gets done first. We couldn't have provided good C++ APIs before we were even ab

> C++ libraries etc We do have limited resources, so we have to prioritize what gets done first. We couldn't have provided good C++ APIs before we were even able to provide good C++. We now do provide a pretty good C++ language experience, but this is still not at the top of the todo list. No one else I've spoken to thinks this is more important than the other work we're doing. > Actually provide build infrastructure to create NDK libraries that can be shared across Android projects, instead of forcing us to somehow cram library and header files into AAR packages while having build scripts extract them for correct placement where cmake and ndk-build expect to find them. cdep never went anywhere, while conan and vcpkg aren't the right answer when many NDK libraries need Java code to come along due to JNI wrappers for like 90% of Android APIs. This is what I've been working on for most of the year. > like how long it took to fix the header files This only took a single release (the rest of the time was to give users a chance to transition), and we did plenty of other things in the same release, so I'm not sure what you're getting at. > Easier CMake support for multiple libraries on our projects, which is found lacking versus how easy it is on ndk-build. Not sure what you mean here, but it sounds like CMake is what you don't like? Just use ndk-build then.