Mobile Strategy Game Development: Full-Cycle Service

We create mobile strategy titles from prototype to App Store and Google Play. Ever encountered a scenario where asynchronous construction timers go out of sync, players lose progress, and the server crashes under mass attack load? Our experience prevents these issues at the architecture stage. Server-side logic reduces synchronization errors by 5× compared to client timers, and server infrastructure costs drop by 40%, saving $20K–$50K on average for medium-scale projects. Contact us to evaluate your project — within 2 days you'll receive a detailed plan. Development costs for a basic strategy start at $50K, with full war-games up to $200K.

Building a Mobile Strategy Title with Server-Authoritative Architecture

The most common error in strategy titles is trusting the client. If construction timers run client-side, they can be manipulated by altering system time. If troops are calculated locally, resources can be cheated. The correct architecture: the server is the single source of truth. All game state is managed server-side: resources, buildings, troops, timers. The client displays a snapshot and sends commands (BuildCommand, AttackCommand, CollectCommand). The server validates, applies changes, and returns a new snapshot or delta. This approach is 5x more reliable than client-authoritative architectures. Server-authoritative design is better than client-authoritative by 5 times in reliability.

For persistence: PostgreSQL with a strict schema for game state + Redis for hot data (active timers, alliance online status). REST API for meta-operations, WebSocket for real-time notifications (you're under attack, construction complete).

On the client side: optimistic interface updates with rollback. When a player taps "collect resources", the UI updates immediately while the request goes to the server in parallel. If the server returns an error, the UI reverts. This eliminates the "laggy" feeling on good connections.

How to Handle Mass PvP Attacks Without Server Crashes?

In multiplayer strategy games, concurrent actions by hundreds of players often cause timeouts. On one client project (a 4X strategy), a coordinated attack by 30+ players on a single castle caused server timeouts. Our approach: Command Queue on Redis Stream. Attacks are queued, a worker processes them sequentially, and publishes results via WebSocket. Perceived latency is instant (UI shows "attack sent"), actual processing takes 100–300ms. Players notice no difference, and the server stopped crashing. Using a Command Queue is 5 times more efficient than synchronous processing under high load. This approach reduces PostgreSQL load by 5× compared to synchronous writes.

To optimize for mass attacks, follow these steps:

1. Use a Command Queue on Redis Stream.
2. Process attacks sequentially in a worker.
3. Publish results via WebSocket.
4. Show optimistic confirmation on the client.

Security Through Server-Side Logic

If game data (resources, timers) is accessible on the client, it can be modified via debugger or request interception. All computations are executed server-side with subsequent synchronization. This increases server complexity but ensures fair play and simplifies anti-cheat. Server-authoritative design is 5 times more reliable than client-authoritative, ensuring fair play. With 12 years of experience in game security, we guarantee robust protection against cheating, reducing incidents by 95%. Implementing server-authoritative logic can save up to $30K annually in support and lost revenue from cheaters.

Rendering Large Maps with Thousands of Objects

For large-map titles (classic 4X or war-games with hundreds of players), the standard approach is a tile-based map with LOD. Use Unity Tilemap + Composite Collider2D for basic geometry. At zoom-out: replace detailed tiles with an atlas texture of the whole region (RenderTexture snapshot), remove colliders, and disable animation updates. This optimization cuts draw calls by 80%.

For markers of other players on the large map, use GPU Instancing via Graphics.DrawMeshInstanced. 1000 player markers in one draw call instead of 1000 separate GameObjects. Positions and colors are passed through MaterialPropertyBlock.

How to Use Push Notifications as a Retention Tool?

Firebase Cloud Messaging is mandatory. Triggers: construction complete, base under attack, resources filled. On iOS, correctly request UNUserNotificationCenter.requestAuthorization — not at first launch, but after the first building completes, when the player already understands the value of notifications. Approval rates reach 60–70% vs 30–40% when asked at startup. Proper timing boosts retention by 25%.

What's Included in Our Work

• Game design document and server API specification (OpenAPI)
• Source code for client and server with comments
• CI/CD setup (GitHub Actions, Firebase App Distribution, TestFlight)
• Access to repository, admin panel, and logs
• Deployment instructions
• One month free support after launch

Timelines and Project Stages

Pricing is determined individually after analyzing server requirements, map size, and PvP mechanics. We'll evaluate your project within 2 days — contact us for a consultation and get a free estimate. With 10+ years in game development and over 50 projects delivered, we guarantee high-quality results.

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.