Building an awesome game for Android
summary
Requires API level 26+ now and a 64-bit build next year, so update engines and plugins; Android P adds Vulkan 1.1, neural net APIs, notch simulation and JobScheduler, and NDK r18 uses libc++ and LLD for much faster links. Chrome OS runs most Android games (about 90%), but ship x86 too; Gameloft reports 6x DAU, 9x monetization on Chromebooks. Use Airtest + Firebase Test Lab for scripted, image- or Poco-driven tests, GAPID to trace draw calls, Android Studio systrace to find slow frames, and Vitals to catch real-world crashes.
AI-written summary · about
chapters (14)
- 0:00BUILDING AN AWESOME GAME FOR ANDROID
- 1:56Deprecation policy
- 3:27Notification
- 4:45Other Android P features
- 5:31Android games on Chrome OS
- 6:48The first step is already done
- 8:06Key differences
- 11:57Android Studio 3.3 preview
- 12:36System Trace in Android Studio
- 14:27Custom events
- 16:02Game testing is hard
- 18:14Underlying framework: Airtest & Poco
- 21:14Stability & bugs
- 22:01Battery
related talks
37mAdapting Android games beyond the phone
12mOptimize your Android games and apps to run on Chrome OS
16mOptimizing games for
36mBuilding Android apps for the Chrome OS ecosystem
32mMoving with the Android ecosystem towards a 64-bit r-Evolution
33mGames on ARC++
27mBig Android: Reaching the Masses! Adding X86 Support To Your Game
17mPlan and optimize your game for success on
