True, but I don't consider "games" (which typically use one activity and don't really use the pices of the framework) to be apps. Maybe people disagree, I'd call them games.
kris On Tue, Oct 16, 2012 at 6:56 PM, Latimerius <[email protected]> wrote: > On Wed, Oct 17, 2012 at 12:37 AM, Kristopher Micinski > <[email protected]> wrote: >> True, you can go through a JNI wrapper to jump back into Java, but I >> wonder then, if you're writing your app mostly in C++, how does that >> fit the goal of the original post.. > > If your app is tied to the Android platform and APIs, if you use lots > of Views, Activities, layouts and other platform classes, then the NDK > is not for you. > > However, a game's interaction with the platform will likely be a > single Activity, assets access and not much more. You'll be able to > do your graphics without touching Java, the same is likely for sound > and probably network, too (not quite sure about that). Almost > certainly no Dialogs, Adapters and so forth, perhaps some > PackageManager, Service or a broadcast receiver here and there, > definitely stuff you don't use in inner loops. :-) > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
