Mobile Arcade Development: Performance & Monetization

Mobile Arcade Development: Performance & Monetization

Arcades live on the first 30 seconds. If the player doesn't get the "one more time" feeling in that window, they leave and never return. We solve this technically: instant respawn, asynchronous asset loading without splash screens, responsive input with sub-frame latency compensation. Every millisecond of delay reduces retention by 5–10%. We design gameplay so that after the first touch, the player has no time to think—only react. We use the Input System Package to eliminate delays on Android and iOS. At the start, we analyze typical game scenarios and identify bottlenecks—from GC Allocs and memory fragmentation to GPU overload. Only then do we begin prototyping. Special attention goes to the first two levels—they teach mechanics and build habit. Our experience: 5 years in mobile game dev, 50+ released projects with over 2 million total installs and over $2 million in ad revenue generated for clients.

Ensuring 60fps on Budget Devices

Arcade gameplay requires stable 60fps. A drop to 45fps for two frames feels like a bug, not a norm. In Unity, this means:

• Object Pooling for everything dynamic (projectiles, coins, enemies, effects)—the pool pre-creates 20–50 objects and reuses them, avoiding GC Allocs and memory fragmentation. Object Pooling cuts frame time by half compared to dynamic creation.
• Static Batching for immobile level elements. If the level is procedural, we merge statics during scene load.
• Single Canvas for in-game HUD with Canvas.renderMode = RenderMode.ScreenSpaceOverlay. Recreating the Canvas on every UI change kills performance via dirty rebuild.
• We leverage the Unity Profiler with Deep Profiling to identify hot spots and optimize CPU-bound code paths using the Jobs System and Burst Compiler.

For touch input—Input System Package with EnhancedTouch.Enable() and Touch.activeTouches instead of the old Input.touches. This removes the overhead of one extra JNI marshaling on Android. In one project, we saw drops on a Samsung Galaxy A50: CPU usage spiked 12% due to Input.touches. After switching to Input System, the problem disappeared, and frame time dropped from 18ms to 14ms. As mentioned in Unity's official documentation, Input System is the recommended way to handle input. For iOS, we also employ IL2CPP to reduce overhead and improve performance.

Typical Problems and Solutions

Integrating Ads Without Losing Users

Ads are the main revenue source in arcades, but showing them at the wrong time kills retention. Rewarded ads work 3–4 times better than interstitials if shown at the moment of loss. Interstitials—only between levels, with a minimum 30-second timer. We use AppLovin MAX for mediation—it automatically selects the network with the highest eCPM. A/B testing of show timing is mandatory: on one project, moving rewarded ads from level start to death screen increased CTR from 12% to 38%.

Why Leaderboards Alone Are Not Enough for Retention

Leaderboards are baseline, but virality comes from deep-linking to a specific score. When a player shares a record on social media, the link should open the game directly on the "beat my score" screen. Firebase Dynamic Links generates a short link with OG preview (score, avatar). On iOS—Universal Links, on Android—App Links. Without this, your leaderboard is just a list of numbers, not an acquisition tool.

Arcade Development Work Process

1. Analytics and Prototype—2–3 weeks ($5,000–$10,000), create a minimal arcade with one mechanic. Test on 10 users, check Day1 retention.
2. Design—level design, sound, leaderboard tables. Integrate Google Play Games Services and Game Center.
3. Implementation—full mechanic cycle, optimal rendering, Input System setup, Object Pooling.
4. Monetization—Rewarded ads via AppLovin MAX and In-app purchases (StoreKit 2 / Billing 6). Rewarded ads shown only after death—CTR 35–50% vs. 10–15% in menus.
5. Testing—on 20+ real devices, check fps, battery drain, crashes. Use Unity Profiler with Deep Profiling on low-end Android devices.
6. Deployment and support—publish to App Store and Google Play, monitor crash reports.

What's Included

We deliver:

• Unity source code with comments (C#)
• Configured build pipelines (iOS/Android)
• Documentation on ad and leaderboard configuration
• Access to Google Play Console and App Store Connect
• Client team training (1–3 hours)
• 30-day warranty for critical bug fixes
• Optional hourly support at $120/hour for post-warranty work

public GameObject Get()
{
    if (pool.Count == 0)
        return Instantiate(prefab);
    var obj = pool.Dequeue();
    obj.SetActive(true);
    return obj;
}

public void Return(GameObject obj)
{
    obj.SetActive(false);
    pool.Enqueue(obj);
}

</details>

### Arcade Development Timeline and Cost

Prototype—2–3 weeks ($5,000–$10,000); full arcade with 5–7 mechanics, leaderboards, monetization—2–4 months ($20,000–$50,000). Cost is calculated individually after scope estimation—contact us for an exact commercial offer. We also offer a 10% discount for early-stage startups, saving up to $2,000. Get a consultation on your project today.

We guarantee stable 60fps on mid-range devices and compliance with App Store Review Guidelines (Section 4.2/5.1). Order a turnkey arcade development—we'll evaluate your project within 2 days.

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.