Native anti-SDK activity in terms of UI

Question

I did a lot of research and even experimented with the NDK for Android (not so much for the SDK). What I could not find is a clear and precise definition of what the NDK cannot do (besides the lack of exception handling and rtti).

I compiled the code for the game and the game engine for Android (completely written in NDK), but it seems that it is not supported as many would like. Not only that, but I would like my game to be a sexy UI without having to write everything from scratch in OpenGL.

Although I'm sure this is easier in Java, I would like to know if the NDK / UI components go to the point where they are even comparable to Java in terms of I / O touchscreen, sound, and graphical interfaces. In the worst case scenario, I can write a UI in Java and just call my own methods from this, but I would like to be able to do more if possible.

Thanks.

Edit

If C ++ is even somewhat compatible with the Java UI, it would be great to know which of the two gives more control and customization. For example, while a Java implementation may be easier to use, does the programmer have many options for fine-tuning the “look” that resembles something specific?

Answer 1

The official NDK can make exceptions and rtti is just fine. Read the file "docs / CPLUSPLUS-SUPPORT.html" distributed using the Android NDK.

In C ++, the only thing you cannot do is implement the Java interface, inherit the Java class, and define a new Java class. Otherwise, you can do everything Java can do. The only problem is that many things (like accessing Java objects or calling Java functions) will require the use of JNI, and this code will look very ugly. Therefore, if you need to create / inherit the user interfaces of Java classes, then you can encode everything in C ++.

I suggest using JNI only for critical performance code. Mixing code - Java for the user interface, mathematical calculations in C / C ++ are really simple. Or, if you are coding a game using OpenGL ES, that's fine too.