GameActivity Part of Android Game Development Kit.
GameActivity is a Jetpack library designed
to assist Android games in processing app cycle commands, input events, and text
input in the application's C/C++ code.
GameActivity is a direct descendant of
NativeActivity and shares a similar
As illustrated in the above diagram,
GameActivity performs the following
- Interacting with Android framework through the Java-side component.
- Passing app cycle commands, input events, and input text to the native side.
- Modelling C/C++ source code into three logical components:
- GameActivity’s JNI functions, which directly support GameActivity’s Java
functionality and enqueue the events to
native_app_glue, which runs mostly in its own native thread (different from the application’s main thread), and executes tasks with its looper.
- The application's game code, which polls and processes the events queued
native_app_glueand executes game code within the
- GameActivity’s JNI functions, which directly support GameActivity’s Java functionality and enqueue the events to
GameActivity, you can focus on your core game development and avoid
spending excessive time dealing with the JNI code.
If you are already familiar with
NativeActivity, the major differences
NativeActivity are as follows:
GameActivityrenders into a
SurfaceView, making it much easier for games to interact with other UI components.
- For touch and key input events,
GameActivityhas a completely new implementation with the
android_input_bufferinterface, separate from the
GameActivityis a derived class of
AppCompatActivity, which lets you seamlessly use other Jetpack components.
Fragment, and others are all available.
GameActivityadds text input functionality by integrating the GameTextInput library.
- Apps derived from
GameActivityare expected to build all three parts of C/C++ code into one library. On the other hand,
NativeActivity's JNI functions are a part of the framework (always loaded by OS). Hence, only the
native_app_glueand application’s C/C++ code are expected to be built into one library.
NativeActivityis a part of Android framework and follows its release cycle (typically yearly).
GameActivityis a part of the Jetpack library, which has a much more frequent release cycle (typically biweekly); new features and bug fixes can arrive much more quickly.
GameActivity library is available in the following channels:
- As a part of the Android Jetpack library (recommended)
- As a zip package, downloadable from the AGDK download page
- As AOSP source code
The C/C++ code is provided as source code in all release channels, using the Prefab format.
Contents of Jetpack library and AGDK zip package
With the Jetpack library and AGDK zip package channels, GameActivity is released with an AAR. This AAR contains the following major components:
- A JAR file for Java code
- C/C++ source code (under the
The integration instructions linked to from this page assume that you can use
Prefab in your build system; otherwise, you can copy the source code packed
prefab/modules/game-activity/include folder into your build system
and perform the necessary integration steps. A similar file structure exists for
the releases under
androidx for the Android Jetpack library; by default,
gradle unpacks AARs in its cache directory (~/.gradle/caches/...). You can find
the C/C++ source code by searching for
and picking up the location under your intended release version.
For instructions on integrating using the Jetpack library, see Get started with GameActivity.
For the AGDK library zip package, follow these steps to get the C/C++ code:
- Unzip the downloaded package.
- In the unzipped package, unzip GameActivity-release.aar.
- Find and copy out all C/C++ source code under
prefab/modules/game-activity/include, includes the following:
GameActivityrelated C/C++ code
GameTextInputrelated C/C++ code
Content of AOSP source code
AOSP always contains the most recent source code. Follow the build instructions to create your own releases or directly integrate the source into your build environment. The C/C++ source code is saved in a file structure similar to the ones for the Jetpack library and AGDK zip package.
Follow those guides to integrate
GameActivity into your applications:
To learn more about
GameActivity, see the following:
- Use the GameTextInput in GameActivity.
- NativeActivity migration guide.
- GameActivity reference documentation.
- GameActivity implementation.
To report bugs or request new features to GameActivity, use the GameActivity issue tracker.