The changes is to reduce the quantity of the templates and to focus on the core patterns. Samples can be found on the web to produce native only applications though at this time as Nsight Tegra continues to evolve and improve its template customizations.
Some templates have also been simply combined being: “Android Application”, “Android Application with Native Code”, and “Android Hello World Demo”.
Importing Google SDK and NDK projects have been dropped since Google’s own SDK continue to evolve and “Android Project (External Build System)” (EBS) can be a more complete solution to invoke other build systems where the attempt to convert may not always be successful. In this case, by using EBS still allows you to edit files, invoke builds, and debug, even when created from other build systems.
Let me add a little more backstory to the fully native application. You can still build one yourself but we have found over time that users have found it difficult to make 100% purely nature applications and instead the most efficient and convenient pattern is what GameWorks suggests. This is going to be the best starting point for game rather than a fully from-scratch template. Instead of being 100% native instead they derive from the Java class NativeActivity. The Android runtime still had Java in your process anyways and was using NativeActivity to bridge to your native library. This way, you now have easy access to anything Java if you desire; whether that be anything in the android runtime that doesn’t have an NDK equivalent or Google Play Services.
Check that out at:
or more specifically
And see how samples in that github location use NvAppBase.