Creating Mobile Games with Godot: From Concept to App Store

Creating Mobile Games with Godot: From Concept to App Store

You're launching a 2D platformer on mobile, but Unity 2022 LTS starts hitting your budget with new fees. Or you're looking for an open-source engine without royalties. Godot 4.x is an engine with a BSD license that allows commercial releases with no deductions. After Unity's pricing changes, the Godot community has grown, and mobile support has matured. We have been developing games on Godot for over 5 years and have delivered more than 50 mobile projects for iOS and Android. We work end-to-end: from concept to store publication. We guarantee bug-free code, timely delivery, and full documentation.

Why Godot Is Chosen for Mobile Games

2D rendering in Godot 4 is among the best in engines: CanvasItem, TileMap with TileSet, Polygon2D, batching via CanvasItemMaterial. Iteration is faster than in Unity: hot-reload scenes without recompilation, built-in editor on all platforms without a license.

GDScript — a Python-like language compiled to bytecode. Easy to learn. For performance-critical systems — C# (Mono, with Godot 4.2 — .NET 6) or GDNative/GDExtension in C++.

How We Organize Game Architecture

Godot works on the concept of scenes and nodes. Each scene is a node tree. Instantiating a scene is analogous to a prefab in Unity. Signals (built-in event bus) replace event/delegate systems.

For mobile games, a typical structure: Main (AutoLoad singleton for global state) + GameManager + LevelManager. Autoloads (like DontDestroyOnDestroy singletons) — for AudioManager, SaveManager, AdManager.

State management. Godot does not impose an architecture. For small projects — Autoload singletons. For large projects — State Machine via AnimationTree or custom StateMachine node with signal transitions.

Mobile Specifics

Export to Android requires Android SDK, JDK, and a configured debug.keystore in Editor Settings. Export templates are downloaded once via Export → Manage Export Templates. ETC2 + ASTC textures — enable both formats in Export Preset for maximum compatibility.

Export to iOS — only with macOS + Xcode. Godot generates an .xcodeproj that is signed via standard Xcode workflow. Without a Mac machine in the team, you can use cloud CI (GitHub Actions with macos-latest runner) for iOS builds.

2D performance. VisibleOnScreenNotifier2D to disable logic for off-screen objects. TileMap with y_sort_enabled for isometric views. Object Pooling — via ObjectPool singleton or MultiMeshInstance2D for many identical objects (bullets, particles, coins).

3D on mobile. Godot 4 uses Vulkan (Forward+) and Vulkan Mobile — a lighter renderer specifically for mobile. In Project Settings → Rendering → Renderer choose Mobile for targeting smartphones. This automatically lowers GPU requirements.

Native Plugins for Mobile

Godot does not have an official Firebase SDK. Integrations are done via Android plugins (.aar file + GDScript API) or iOS plugins (.xcframework). Active open-source plugins: godot-firebase (unofficial but working), godot-admob for monetization.

In-App Purchases. GodotGooglePlayBilling for Android, InAppStore plugin for iOS. Alternative — RevenueCat SDK with a Godot binding.

The lack of official plugins from Google and Apple is the main downside of Godot for production projects requiring specific SDKs. It is solvable but requires extra time. We have experience integrating such plugins in dozens of projects.

Comparison of Godot and Unity for Mobile

Development Stages: From Concept to Store

What Is Included in Our Work

• Game Design Document (GDD) creation
• Prototype development (vertical slice)
• Full cycle: art (if needed), programming, animation, sound
• Integration of ads (AdMob/Unity Ads) and purchases (In-App Purchases)
• Publication to App Store and Google Play
• Technical support for 1 month after release
• Full source code documentation and architecture guides
• Access to project management board and version control (Git)
• Training session for your team on maintaining the game

Timelines

Casual 2D game (Godot is the optimal choice): 2–4 months with a team of 2–3 people. Hyper-casual prototype: 3–6 weeks. The cost is calculated after analyzing the concept and target platforms.

Contact us to assess your project — we'll discuss your idea and propose timelines.

Step-by-Step: How to Export a Game to iOS

1. Install Xcode on a Mac (or use a cloud CI with macOS runner).
2. In Godot, set up export preset for iOS with correct Bundle Identifier and signing info.
3. Export the project as Xcode project.
4. Open the .xcodeproj in Xcode, configure signing certificate and provisioning profile.
5. Build and archive the app, then upload to App Store Connect.

Godot Engine Documentation: https://docs.godotengine.org/en/stable/

Our experience and certified developers ensure your project is delivered on time and without hidden costs.

How to choose cross-platform development: Flutter, React Native, or KMM?

We often work with startups that need two apps—iOS and Android—with a budget for one team. Or corporations that want to release an internal tool in three months on both platforms. Cross-platform development solves a specific economic problem: one codebase instead of two. The question is not 'cross-platform or native'—it's 'which tool for which task.'

Each framework dictates its own stack and imposes limitations. An incorrect choice leads to rewriting the project in six months—we've seen it many times with clients who came to us after a failed first attempt. Therefore, before starting, we conduct an audit of technical requirements and team expertise. With 8+ years of cross-platform experience and 50+ delivered apps, we know the pitfalls firsthand.

The three main players now: Flutter, React Native, and Kotlin Multiplatform Mobile. They solve different problems and are poorly compared head-on. Below, we'll break down how to choose the best option for your project.

How do we choose the technology? 4 steps

1. Requirements analysis — list of native APIs, need for offline work, branded UI or standard.
2. Team assessment — expertise in Dart, JavaScript/Kotlin, availability of an iOS developer.
3. Proof-of-concept — implement a critical scenario on the chosen stack in 2–3 days.
4. Final decision — based on performance benchmarks and maintenance cost.

Case from our practice: a fintech startup needed an MVP on both platforms in 10 weeks. Their team had deep React experience, so we selected React Native. The app passed App Store and Google Play review on the first submission, and they launched on schedule. That choice saved 4 weeks compared to training for Flutter.

Comparison of Flutter and React Native: under the hood

Rendering model

Flutter renders UI independently via the Impeller engine (replaced Skia starting with version 3.10). The platform only provides a canvas—Flutter draws every pixel itself. This means:

• Pixel-perfect on all platforms. The same widget looks identical on iOS and Android—good for branded apps, bad if you need a 'native' look on each platform.
• No dependency on OS version. Material 3 in Flutter works the same on Android 8 and Android 14. System Android components are not involved.
• Platform channels for native code. Access to camera, Bluetooth, NFC—via MethodChannel or EventChannel. flutter_camera, flutter_blue_plus are wrappers over platform channels.

React Native uses native platform components. <View> on iOS is UIView. <Text> is UILabel. This means:

• Native look and feel without extra effort.
• New Architecture (Fabric + TurboModules) with JSI removed the JSON bridge between JS and native code. Synchronous calls work without serialization. This is critical for animations and gestures.
• React Native Reanimated 3 runs worklets on the UI thread—animations at 60/120 fps without blocking the JS thread.

Performance in practice

For most business apps, the performance difference between Flutter and React Native New Architecture is imperceptible. The difference appears in edge cases.

Flutter is slower when interacting with platform APIs via platform channels—each call is asynchronous, with data serialization overhead. google_maps_flutter renders the map via PlatformView—a native UIView/View embedded in the Flutter tree. Before Impeller, this caused performance issues (Hybrid Composition vs Virtual Display). With Impeller, Flutter renders UI 2–3x faster on low-end devices compared to Skia, and PlatformView performance improved by 40%.

React Native is slower in scenarios with heavy JS logic on the main thread. Parsing large JSON, complex computations—these block the JS thread and appear as UI freezes. Solution: Hermes (JS engine optimized for RN) + offloading computations to a native module or react-native-workers. With Hermes, cold start time is reduced by 30–40% compared to JavaScriptCore—that's 2x improvement on older devices.

Ecosystem and maturity

Dart is a barrier to entry for teams with a JS/TS background. It's possible to learn basic Dart in a week, but shifting your mindset to Flutter widgets and widget tree takes longer.

TypeScript in React Native is the de facto standard. A team with React experience becomes productive faster.

When to choose Flutter?

• Need a unified branded UI on all platforms (iOS, Android, Web, Desktop).
• Team is ready for Dart.
• Lots of custom animation and custom UI—Flutter is more predictable.
• The app is not tied to specific native APIs.

When to choose React Native?

• Team has React/TypeScript expertise.
• Need native look and feel.
• Heavy use of native components (Maps, Camera with native capabilities).
• Sharing code with React web via monorepo.

Kotlin Multiplatform Mobile: a different story

KMM solves not a UI problem, but the problem of business logic duplication. The concept: write business logic, networking, caching, validation once in Kotlin. iOS receives a .framework via Kotlin/Native, Android uses the library directly. UI on each platform is native.

// Shared Kotlin code — works on iOS and Android
class UserRepository(
    private val httpClient: HttpClient, // Ktor
    private val database: AppDatabase   // SQLDelight
) {
    suspend fun getUser(id: String): User {
        return database.userQueries.selectById(id).executeAsOneOrNull()
            ?: httpClient.get("$BASE_URL/users/$id").body<User>().also {
                database.userQueries.insert(it)
            }
    }
}

Ktor — HTTP client for KMM (works on iOS via Darwin engine, on Android via OkHttp). SQLDelight generates a typesafe Kotlin API for SQLite, works on both platforms.

Real limitations of KMM

Coroutines on iOS: suspend functions from shared code are called through automatically generated wrappers. SKIE (Swift/Kotlin Interface Enhancer) from Touchlab significantly improves the Swift interface: async/await instead of callbacks, AsyncStream for Flow. Without SKIE, working with coroutines from Swift is inconvenient.

Compose Multiplatform: JetBrains is developing Compose for iOS — UI in Compose works on iOS via Metal. This blurs the line with Flutter: one Compose code for both platforms. Status today: Beta, with early adopters in production (Touchlab, JetBrains own products), but stability is lower than Flutter.

Complexity of iOS integration: XCFramework from KMM module is added to an Xcode project. SPM integration exists and works. But iOS developers must understand the Kotlin API and memory management rules via Kotlin/Native (ARC + Kotlin GC work together, which is not always obvious).

When KMM is justified

The company already has mature iOS and Android teams that duplicate business logic. Switching everything to Flutter or React Native is too radical. KMM allows starting small: extract networking and models into shared code, keep UI native. Gradual migration without rewriting everything.

Typical mistakes in technology selection

Choosing Flutter "because it's a single codebase" for an app heavily reliant on native APIs (custom camera, BLE, background processing). Implementing these via platform channels adds complexity that eats up the development speed advantage.

React Native without understanding the JS thread. Heavy operations on the JS thread cause visible freezes. This is solvable, but requires understanding the architecture—otherwise the app will perform worse than native.

KMM without an iOS developer on the team. Shared Kotlin code requires an iOS engineer who integrates the framework into Xcode, writes SwiftUI on top of KMM APIs, and debugs Kotlin/Native crashes.

What is the development process and timeline?

A cross-platform project goes through the same stages as a native one: requirements audit → stack selection → design → development → testing on real devices of both platforms → publication in App Store and Google Play → support.

Testing on real devices is not optional. An emulator does not reproduce memory issues on budget Android phones and does not show differences in gesture behavior on iOS. We test 40+ scenarios on at least 5 real devices covering both OS versions.

Budget savings compared to two native teams can be up to 40–50%. The cost is calculated individually after analyzing the stack and requirements.

What's included in our work

• Technical audit and stack selection for your project.
• Architecture design (clean architecture, MVVM, BLoC/Redux).
• UI development according to design mockups for both platforms.
• Integration of native modules (camera, geolocation, push notifications).
• CI/CD setup (GitHub Actions, Codemagic).
• Testing on real devices (iOS/Android) — at least 40 scenarios.
• Preparation and publication in App Store and Google Play following guidelines (App Store Review, Google Play Policy).
• Technical support for 3 months after launch.
• Handover of source code, documentation, and access — all turnkey.

We'll evaluate your project in one day—get a consultation on stack selection. Order turnkey development and receive a cross-platform app within the agreed timeline, backed by our experience and guaranteed milestones.