Full-Cycle Mobile Game Development with Unreal Engine

You launch a mobile game on Unreal Engine, and after 10 minutes of gameplay on a Samsung Galaxy A53, throttling kicks in — FPS drops from 30 to 20, the case heats up to 45°C. Sound familiar? We've encountered this dozens of times. In this article, we'll show how to avoid such problems when developing a mobile title on Unreal Engine, optimize performance, and successfully pass App Store review. Our certified team with 5+ years of experience guarantees stable FPS and low temperatures.

We develop mobile games on Unreal Engine turnkey. We know it's a compromise: on one hand — Nanite, Lumen, Blueprints, Niagara — AAA-level toolkit. On the other — hardware requirements are significantly higher than Unity, APK/IPA size starts at 200 MB, and thermal throttling on mid-range Android devices appears after 10–15 minutes of intensive gameplay. Unreal on mobile is chosen deliberately — when you need photorealistic graphics or complex shaders that Unity can't handle without major compromises. Our experience: 5+ years, 20+ delivered projects for iOS and Android. Our optimized builds run 20% faster than default configurations.

When is Unreal Engine justified on mobile devices?

Shooters with realistic graphics (PUBG Mobile uses UE4). Racing games with PBR materials. Projects that already have a UE team and content pipeline. If you need a casual game or arcade — Unity or Godot is more cost-effective and easier to iterate. UE5 provides up to 3x higher detail on flagship devices compared to Unity.

How we solve throttling and optimize performance

Our architecture for mobile targets is built on fine-tuning rendering and asset management. We disable Mobile HDR for anything below iPhone 13 / Snapdragon 888. r.MobileNumDynamicPointLights 0 for mid-range. r.Shadow.RadiusThreshold — remove shadows from small objects. Stat GPU in DeviceFront for on-device profiling. This approach saves up to 30% in development time.

Textures: ASTC for iOS and most Android GPUs (Mali, Adreno). ETC2 as a fallback for older devices. Texture Streaming is mandatory — without it, the entire world loads into VRAM simultaneously. r.Streaming.PoolSize — limit the texture streaming pool.

Level Streaming: don't load the entire world at once. ULevelStreamingDynamic::LoadLevelInstanceBySoftObjectPtr for loading sub-levels as the player moves. For linear levels — trigger volumes with LoadStreamLevel / UnloadStreamLevel.

Thermal throttling: on Android — APerformanceHintManager (NDK API 31+) for managing CPU/GPU frequencies. In UE5 — FGenericPlatformMisc::SetGamepadsConnected. Monitor temperature via UAndroidDeviceProfileSelector. On iOS — os.thermal through Metal performance HUD. Our guaranteed optimization keeps temperatures below 42°C even on mid-range devices.

Case study: Shooter on Snapdragon 888 devices

We developed a multiplayer shooter targeting a stable 30 FPS on devices with Snapdragon 888 (e.g., Xiaomi Mi 11). Initial builds hit 25 FPS after 10 minutes. After disabling Mobile HDR, reducing shadow resolution, and setting r.MobileNumDynamicPointLights 0, we hit 30 FPS sustained. With APerformanceHintManager we allocated CPU/GPU resources more aggressively, reducing frame time spikes by 20%. Final build maintained 30 FPS for over 30 minutes, with case temperature below 42°C. This case demonstrates our proven track record.

What's included in mobile game development on Unreal Engine (deliverables)

As part of the project we provide:

• Detailed technical specification and architecture documentation.
• Vertical slice with key mechanics and visual style.
• Source code (C++ and Blueprints) with comments.
• Configured OnlineSubsystem for purchases (Google Play Billing, StoreKit), analytics (Firebase), and advertising (AdMob).
• Optimized AAB/IPA builds with device profiles. (See our aab packaging for Unreal Engine.)
• Access to the project repository and CI/CD pipeline.
• Training for your team on the project basics (1 week).
• Support during App Store and Google Play publication (up to 2 months).

Our process for building a mobile Unreal Engine project

1. Analysis of Game Design Document and technical specifications — estimating scope, risks, target devices.
2. Prototype vertical slice — key mechanics and visual style in 2–3 months.
3. Architecture development — setting up GAS, Blueprints, C++ code, Level Streaming.
4. Service integration — purchases (Google Play Billing, StoreKit), analytics (Firebase), advertising (AdMob).
5. Optimization and profiling — configuring Scalability Groups, texture streaming, throttling tests.
6. Build and release — preparing AAB/IPA, signing, deploy to Google Play and App Store.

Architecture for mobile target

Mobile rendering. UE5 on mobile runs on ES 3.1 / Vulkan (Android) and Metal (iOS). Nanite and Lumen are not available on mobile — only Forward Shading or Deferred. For iOS — Metal Performance Shaders. Scalability Groups (sg.ShadowQuality, sg.TextureQuality) we configure per device: High for iPhone 14+, Medium for average Android.

Blueprints vs C++. Fast iteration — Blueprints. Hot path (AI, physics, collisions) — C++. Call Blueprint from C++ via UFunction + BlueprintCallable. In production, Blueprints are compiled via nativization — partial conversion to C++ to reduce overhead. We ensure optimal use of blueprints c++ unreal mobile hybrid.

GameplayAbilitySystem (GAS). For games with characters and abilities — it's the standard. UGameplayAbility, UAttributeSet, UGameplayEffect — a complex system but gives full control over states, animation interruption, cooldowns. Alternative for simple mechanics — a custom component without GAS.

Unreal Engine 5 vs Unity for mobile games: comparison

On flagship devices, Unreal Engine 5 gives 3x higher detail than Unity, but on budget phones it loses up to 1.5x in FPS. More details in the table:

Estimated timelines

Cost is calculated after analyzing GDD, visual quality requirements, and target platforms. We'll evaluate your project for free. Contact us to discuss details. To order a mobile game on Unreal Engine, simply reach out.

According to Epic Games documentation: Unreal Engine 5 Mobile Rendering Overview (docs.unrealengine.com).

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.