My point is that the way Android team deals with NDK users seems like the NDK was imposed on the team, and they don't spend much developer time on it, looking from the set of open issues, outdated documentation where ndk-build is still used instead of cmake, integration with aar is still in progress, and set of available APIs.
https://code.google.com/p/android/issues/list?can=2&q=NDK&so...
I cannot deny they have done lots of progress, but there seems not to be much interest in having a comparable experience to the Java tooling.
And that as I mentioned it still is a work-in-progress, 2nd class developer experience (down to forcing JNI calls to C++ libraries on the device like e.g. Skia), compared with the Java based tooling on the Android SDK.
It doesn't seem to get the love an essential tool is supposed to get.
Even nowadays with Android N, the NDK is kind of WIP.