That's not to say Java is as bad as ObjC however ;) But something less verbose and more modern like Golang will be a great option to have.
...but to be fair, writing UI and graphical applications has never been it's strong point, and still is not.
Although you can write NDK applications which steal the raw graphics context to do whatever they like (mandala, xamarin, unity, etc.), tapping into the android UI layer is significantly slower and more complex.
Given that the NDK website still says:
In general, you should only use the NDK if it is essential to your
app—never because you simply prefer to program in C/C++.
(That said, the upcoming I/O has what, 4 or 5 slots devoted to NDK related things; clearly despite the android team, at least someone is paying attention to the fact that people use it. A lot. So you never know~)
For that usecase may be Google can extend ART to convert Go code into something that plugs into the ART and outputs something that can be mixed with the AOT compiled Java code.
The ticket for Go support on Android is open since 2012 and no one from the Android team seems to care.
The Go team has reopen the discussion of, maybe, trying to add support for it in the 1.4 release.