Mobile Card Game Development: From Prototype to Release

Imagine: a player plays a card with a poison effect, but on the opponent's screen, the target's health doesn't change. A sync bug — one of the most common reasons for negative reviews. In one of our projects with 50,000 DAU, such a bug led to a 15% user loss within a week. We've encountered this multiple times and developed a reliable solution: the Command pattern and strict server-side validation.

We build mobile card games from scratch: from mechanic design to store publication. Experience: 5+ years and 10+ projects. In this article, we break down key technical aspects: match state synchronization, balancing 500+ cards, smooth animations on low-end devices.

Technical Challenges

Card games are a genre highly dependent on data balance and match state reliability. In a fighting game, an animation bug might go unnoticed; in a card game, an incorrectly calculated card effect ruins the experience immediately.

• Real-time state synchronization: each turn must be a transaction. The game state must not remain "half-applied" on crash or connection loss.
• Balancing 500+ cards: 500+ unique cards with different effects require a metrics system and automated testing. We ran 10,000 automated simulations to detect imbalance early.
• Visualization and performance: card animations must not lag on budget devices (average FPS of 60, minimum 30).
• PvP mode: support for synchronous and asynchronous matchmaking.

Why Match State Synchronization Is the Key Problem?

Each turn is a transaction. Player plays a card → chain of effects → new board state. We implement it via the Command pattern. PlayCardCommand, AttackCommand, DrawCardCommand — each command has Execute and Undo. The entire turn is a stack of commands that either applies fully or rolls back. This also gives replay functionality for free: save the command stack + initial seed → get a reproducible match. Average turn takes 2.3 seconds including network latency.

For real-time, we use Photon Realtime. Photon Realtime ensures reliable message delivery for multiplayer games.

What to Choose: Real-Time or Asynchronous PvP?

The choice affects architecture and user experience.

Synchronous PvP (both players online): use Photon Realtime with custom Room State. Turns are transmitted as events (RaiseEvent), server acts as relay. For validation — a separate server service that checks move legality before broadcasting to opponent.

Asynchronous PvP (Push & Pull): turn is saved to server, opponent receives FCM push notification. Works even with poor connection, more tolerant to mobile-first audience. For deck and balance — Firebase Firestore with security rules.

How to Achieve Smooth Animations on Low-End Devices?

Cards in Unity — Canvas with RectTransform for UI-based render or separate SpriteRenderer meshes for the game board. UI approach is more convenient for animation and drag-and-drop via IBeginDragHandler, IDragHandler, IEndDragHandler. DOTween for card playing effects: flyout from hand, glow, shake on attack. We use Object Pool for cards to avoid runtime allocations. Average frame time 16 ms (60 FPS).

Dynamic card art generation from template: RenderTexture + Camera in offscreen — render the 3D card model with needed parameters into texture, use as sprite. This allows having 500+ unique cards without 500 separate textures.

Typical Mistakes in Card Game Development

• Ignoring testing on low-end devices: animations may lag if not optimized.
• Lack of logging system for sync debugging: without logging, it's hard to reproduce bugs.
• Poor reconnection handling: player must return to match with restored state.
• Too frequent server requests: increase load and latency.
• Not using Object Pool: leads to frequent GC and FPS drops.

What Stages Does Development Include?

1. Analytics and design: mechanic prototyping, card balance based on simulations (10,000 rounds), matchmaking design.
2. Implementation: writing game logic in C# in Unity, Photon/Firebase integration, card system and animations creation.
3. Testing: automated match simulations, testing on real devices (iOS/Android), server stress tests (handles 1,000 concurrent matches).
4. Publication: build preparation, App Store and Google Play review, in-app purchases setup with StoreKit 2 and Billing 6.
5. Support: 30-day warranty after release, updates for new OS versions.

Timelines and Cost

Single-player card game with AI opponent — 3–5 months. With PvP and deck-building mode — 5–9 months. Cost is calculated individually after requirements analysis.

What's Included in Our Work

• Full documentation package: technical specification, architecture diagram, game logic description.
• Access to the repository with code and CI/CD pipeline.
• Training your team to work with the project (2–3 sessions).
• First month of warranty support after release.

Contact us to discuss your project — we will prepare a commercial proposal with a detailed development plan. Order a consultation to estimate timelines and budget. Get a detailed development plan.

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.