Godot 4.7: Creating Games Entirely on Android Is Now Real

Godot 4.7 improves the workflow for building games on an Android device. The Android editor handles scene and script editing, while the Godot Android Build Environment (GABE) provides Gradle export support. This guide covers the changes and a small project you can use to try them.

Source pass: this article is based on the official Godot 4.7 release notes. It focuses on the Android development workflow and avoids API-level code examples. For production setup details, cross-check the current Godot docs and migration guide.

The Catchy Version

You can use the Android editor and GABE to work toward an Android build on the device itself. Before starting a larger project, test the full route from editing a scene to installing the exported game.

This can be useful if you are learning without a desktop or prototyping touch controls directly on an Android device. Screen size, input, and file management will affect how comfortable the workflow is.

What GABE Adds

GABE stands for Godot Android Build Environment. It is a companion app for the Godot Android editor, and the key practical point is Gradle export support. In plain English: it helps turn Android editor work into Android builds from the Android-side workflow.

Try the build tools early. Being able to run a scene in the Android editor is only part of the process; the exported game also needs to install and run independently.

Why This Matters

• Lower barrier to entry: a capable Android device can become more than a test device.
• Better mobile-first testing: you can think about touch, screen shape, and performance earlier.
• Stronger learning story: beginners can experiment with Godot without needing the full desktop setup immediately.
• Real export path: GABE gives the Android editor workflow a clearer build and publishing route.

A desktop offers more room for large scenes, asset tools, and debugging. Android development is easier to evaluate with a small project that uses touch input and limited source assets.

Android Editor Quality-of-Life

The Android editor’s embedded game window can be moved and resized in Godot 4.7. Use it to check how the game’s layout responds to different screen shapes while you work on the device.

The expanded Script Editor supports orientation changes. Rotating the device lets you choose a more comfortable layout when the on-screen keyboard takes up editing space.

Export and Publishing Polish

Native Android splash screen settings are available in the export options. You can adjust them there instead of making the manual native resource edits previously required for that setup.

Godot 4.7 also makes Perfetto the default tracing tool for Android editor and template builds. For template builds, that means developers can use Android's built-in performance tracing tools to analyze games and apps. For the Android editor itself, it gives maintainers better data for improving the mobile editor experience over time.

Mobile Game Features Around It

Godot 4.7 also adds picture-in-picture support on Android. If that suits your app, check how its visible content and controls behave when the window becomes small.

For input, Godot 4.7 adds a built-in VirtualJoystick node with Fixed, Dynamic, and Following modes. That pairs nicely with a mobile-first workflow because touch controls are not an afterthought; they become part of the early prototype.

What to Try First

Do not start by moving a giant existing game onto a phone. Start with a small mobile-first project that can prove the workflow. A one-screen arcade game, idle prototype, tap timing game, tiny platformer, or simple puzzle project is enough.

• Pick portrait or landscape before designing the first screen.
• Use touch controls early instead of adding them at the end.
• Resize the embedded game window to test several aspect ratios.
• Set up a simple export path and splash screen before the project grows.
• Run a quick performance trace once gameplay exists.
• Only then decide whether the workflow fits a larger project.

Who This Is Best For

This is most compelling for learners, students, mobile-first indie developers, game jam experiments, lightweight 2D games, tool prototypes, and creators who want to test on the same class of device they are targeting.

For a large 3D project, compare the Android workflow with your desktop setup before moving files. Check editing space, profiling, external asset tools, and keyboard input with a representative scene.

Finish the small test project by installing its export and checking touch input, orientation, and performance. Use those results to decide how much of your next project you want to build on Android.