Manual: The Activity application entry point (original) (raw)
Android application entry points
Activity requirements and compatibility
Activity was originally the only application entry point that Unity supported and because of this it’s very stable in the majority of scenarios.
This application entry point is appropriate to use in the following scenarios:
- Your project uses plug-insA set of code created outside of Unity that creates functionality in Unity. There are two kinds of plug-ins you can use in Unity: Managed plug-ins (managed .NET assemblies created with tools like Visual Studio) and Native plug-ins (platform-specific native code libraries). More info
See in Glossary that must run on a Java thread. For more information, refer to Plug-in compatibility. - You are upgrading an old project that already uses the Activity application entry point.
If the above scenarios don’t apply to your project, the GameActivity application entry point is a more appropriate application entry point. Among other benefits, Unity’s implementation of GameActivity gives you more control over the interaction between Android and your application. For more information, refer to GameActivity application entry point.
| Topic | Description |
|---|---|
| Activity requirements and compatibility | Understand the system requirements and feature compatibility of the Activity application entry point. |
| Extend the default Unity activity | Override basic interactions between the Android operating system and the Unity Android application. |
Additional resources
Android application entry points
Activity requirements and compatibility