Developing Mobile Games in Unity: From Prototype to Release

Draw calls, memory, and battery—three enemies of any mobile Unity project. Even at 60 FPS on a flagship, the game can lag on Xiaomi Redmi Note 8 with 3 GB RAM: frames drop to 15 FPS when enemies appear, and the battery heats up in 20 minutes. Typical causes are lack of object pooling, unoptimized textures, and neglecting IL2CPP.

We are a Unity development team with 7+ years of proven experience. We have shipped over 20 mobile games, from hypercasual arcades to open-world RPGs. Our specialty is performance on devices with 2 GB RAM. We guarantee stable 30 FPS on targeted low-end devices after optimization. Order mobile game development on Unity—get a consultation for your project.

How to Ensure Performance on Low-End Devices

Draw calls and batching. On mobile GPUs the draw call budget is tight: 100–200 depending on the device. Static geometry → Static Batching. Same materials → GPU Instancing. Dynamic objects → Dynamic Batching (works for mesh objects < 900 vertices). We verify using Frame Debugger in Unity Editor.

Textures and memory. ASTC is the compression format for iOS and Mali/Adreno GPUs on Android. No PNG in 2048×2048 for UI icons sized 64×64. Use atlases via Sprite Atlas or manual packing. Monitor memory with Memory Profiler (package com.unity.memoryprofiler). A typical iOS issue: Texture2D is not removed from memory after Destroy() without explicitly calling Resources.UnloadUnusedAssets().

Object Pooling. Instantiate/Destroy on the hot path is the enemy of performance. Use UnityEngine.Pool.ObjectPool<T> (built-in) for pooling. Bullets, enemies, particles—everything through a pool.

IL2CPP and AOT. Mobile builds always use IL2CPP, not Mono. IL2CPP is 2–3 times faster than Mono when executing code on mobile devices. Reflection breaks the strip level: if ReflectionProbe or a custom serializer uses reflection, add a link.xml with explicit preserve directives. Otherwise, you get MissingMethodException in release builds that didn’t appear in Debug.

Why Project Architecture Matters

For mid-core mobile games we use MVVM + Services without a full ECS. Unity documentation recommends DOTS for maximum performance, but it’s overkill for most mobile projects up to arcade genre: Burst Compiler, Jobs System, and NativeArray require experience and increase development time.

State management via Zenject or VContainer (lighter alternative). Each service (AudioService, ScoreService, InventoryService) is injected via constructor, not FindObjectOfType. Use ScriptableObjects for game data configuration—levels, enemy stats, progression curves. Change balance without rebuilding APK/IPA using Addressables + remote config (Firebase Remote Config or Unity Remote Config).

Integrations for Mobile Production

Ads. Google AdMob via com.google.ads.mobile—banners, interstitials, rewarded video. Unity Ads as an alternative. Mediation via IronSource or AppLovin MAX to maximize eCPM.

In-App Purchases. Unity IAP (package com.unity.purchasing)—unified API for App Store and Google Play. StoreKit on iOS, Google Play Billing on Android. Server-side receipt validation is mandatory—client validation can be bypassed by Jailbreak/Root.

Analytics. Firebase Analytics (com.google.firebase.analytics) is the standard. Key events: level_start, level_end, level_fail, ad_impression, iap_purchase. Unity Analytics as a built-in alternative.

Crashlytics. Firebase Crashlytics—real-time crash reports. Integrated via com.google.firebase.crashlytics. Custom keys for context: Crashlytics.SetCustomKey("level", currentLevel).

CI/CD and Publishing

Fastlane for automation: gym for iOS build, supply for upload to Google Play, deliver for App Store. Unity Build Automation as an alternative for teams without custom CI.

GitHub Actions + game-ci/unity-builder—free CI for Unity with caching of Library folder (saves 10–30 minutes per build).

App size. APK split by ABI—separate files for arm64-v8a, armeabi-v7a, x86_64. On iOS, App Thinning automatically via Xcode. Asset Bundle Compression—LZ4 for fast loading, LZMA for minimal size.

Deliverables and Post-Release Support

• Project architecture documentation and Game Design Document
• Core gameplay prototype and vertical slice with source code access
• Integration of ads, purchases, and analytics (including SDK documentation)
• Performance optimization for dozens of devices (profiling on real hardware, report provided)
• Publishing to App Store and Google Play (certificates, metadata, store listing assistance)
• Post-release support: bug fixing, content updates, crash monitoring via Crashlytics
• Training for your team on maintaining and updating the game

According to Unity documentation, "Proper memory management can increase FPS by 20–30%."

Development Stages

Prototype (core gameplay loop) → vertical slice (one full-content level) → alpha (all mechanics, no polish) → beta (device testing, optimization) → release.

Between alpha and beta—mandatory profiling on real hardware: old Android (Snapdragon 660, Mali G72) and iPhone SE 2nd gen. If these devices maintain stable 30 FPS, the product is ready for a wide audience.

Timelines and Cost

Cost is calculated after reviewing the GDD (Game Design Document) and platform technical requirements.

Get a consultation on optimization and monetization of your game—contact us to discuss details. Order mobile game development on Unity—we’ll help you take the project from idea to release.

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.