Turnkey Midcore Mobile Game Development from Scratch

We develop midcore games that handle real-time load on devices with Snapdragon 680 and 2GB RAM. When a client expects a meta-layer with progression, guilds, and seasonal passes, casual solutions don't work. Our job is to design an architecture that scales with monetization without rewriting code. Contact us for a project evaluation.

What problems does turnkey midcore game development solve?

The most common point of failure is a progression system designed as an Excel spreadsheet rather than code. Balance is stored in ScriptableObject or local JSON, the game launches, and three months later it turns out that adding a new unit type requires rewriting four systems. We've seen projects where UnitConfig contained 47 boolean flags and all logic was built through if (isElite && hasBuff && !isFrozen). That doesn't work with 200 unit types.

The second pain point is the network layer in PvP and co-op. Using simple HTTP REST for real-time combat leads to the client and server diverging by 3-4 steps at 150ms latency. Client prediction without server validation leads to cheats. Server validation without rollback leads to jitter. We need either Photon Fusion with its state synchronization, or a custom implementation on Mirror with deterministic physics (Deterministic Lockstep), where both clients reproduce the same commands in the same order.

The third problem is memory. Unity Addressables with improperly configured groups causes the entire previous scene to remain in memory when loading a new chapter. On an iPhone 12 that's tolerable. On Android low-end with 2GB RAM — OOM and crash. You need explicit lifecycle management via Addressables.ReleaseInstance and proper bundle splitting: UI atlases separately, characters separately, environment separately. The financial risk from such crashes is losing users during onboarding.

Ensuring Stable Performance on Android Low-End Devices

For midcore projects we use Entity Component System (ECS) through Unity DOTS or Arch for game simulation, and a separate MonoBehaviour layer for UI and visual representation. Game logic (stats, buffs, AI, projectile physics) runs in ECS — this provides determinism and performance on job threads. Everything Canvas, Animator, VFX stays in Mono. ECS outperforms MonoBehaviour by a factor of 10 on large numbers of objects: tests show 2ms vs 20ms for 1000 units.

The meta-layer (inventory, progression, social) is built as a separate domain with clear boundaries. Typical structure:

GameCore/
  ECS/          -- combat simulation (DOTS)
  Systems/      -- GameplayLoop, SpawnSystem, CombatSystem
  Data/         -- ScriptableObject configs + remote config via Firebase
Meta/
  Inventory/
  Progression/  -- XP, levels, unlocks
  Social/       -- guilds, leaderboards (Google Play Games SDK / GameKit)
Network/
  Photon/       -- real-time PvP
  REST/         -- meta operations (purchases, saves)

Remote Config via Firebase is mandatory for balance. All numeric parameters: damage, upgrade cost, drop probabilities — should be in Remote Config, not in the build. This allows patching balance without store updates. Our experience shows this approach reduces critical bugs by 40%.

Monetization: Unity IAP for in-app purchases + ironSource or AppLovin MAX for ads with mediation. Important: on iOS you need to handle SKPaymentTransactionObserver correctly — pending transactions on interrupted internet should be restored at next launch, otherwise Apple may reject the app per guideline 3.1.1. We guarantee passing review.

Why ECS is Better for Midcore Games?

ECS provides determinism and performance. In one project — a midcore strategy with 50v50 battles — on budget Android devices the CPU overheated after 8 minutes of continuous battle. Profiler showed: 6ms per frame was spent on SkinnedMeshRenderer.Update for 100 units simultaneously. The solution — GPU Instancing for static meshes + replacing Skinned Mesh with GPU skinning via Compute Shader for distant units (distance > 15 units). Close units — normal skinned mesh. Distant units — billboard or simplified animation via vertex shader. As a result, CPU render time dropped from 6ms to 1.8ms, temperature stabilized. This optimization saved us weeks of redesign work.

From our practice: for another project we used Addressables with bundle splitting, which reduced cold start to 3 seconds and avoided OOM on 2GB devices. Read more in the official Unity Addressables documentation.

How to Start Midcore Game Development with Us?

1. Idea and Concept Audit — analyze the market, define target audience, form requirements.
2. Core Prototype — implement basic gameplay in 4-6 weeks.
3. Alpha Version Development — connect meta-systems, network layer, prepare build for testing.
4. Beta Testing and Polish — fill with content, balance, integrate monetization.
5. Soft Launch and Iterations — analyze metrics, refine project for global release.

What's Included

Timelines and Process

A midcore game from scratch takes 6–14 months depending on meta-systems and content volume.

Cost estimation is done after analyzing the GDD and technical requirements. It's especially important to understand the scope of multiplayer: real-time PvP vs asynchronous — the difference in labor is significant. Order turnkey midcore game development, and we will prepare a precise quote.

Get a consultation to discuss your project and avoid these mistakes from the start.

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.