Unity Multiplayer with Mirror: Sync, Reconnect & Headless Server

A mobile Unity game often lags when adding multiplayer. Network synchronization on the phone is a separate challenge: accidental backgrounding drops the connection, and 200 ms delays kill gameplay. We solve this using the open-source network code Mirror Networking — a framework that gives full control over the Unity network and infrastructure. Unlike Photon, Mirror is not tied to the cloud: plug in kcp2k, Telepathy, or WebSockets, host the server on your own hardware. For mobile projects this means latency 10–50 ms instead of 100+, up to 70% savings on hosting, and traffic optimization that reduces data transfer costs up to 50%. Specifically, hosting a Mirror server for 50 players costs about $50-100 per month, saving 70% compared to Photon's $200-300 for the same load. For 1000 concurrent players, Mirror costs about $500 per month compared to Photon's $1500, saving $1000 monthly. Our experience: 5+ years developing mobile multiplayer games on Unity, over 30 successful releases. We guarantee stable synchronization even with 50+ concurrent players.

How Mirror Solves the Connection Loss Problem on Mobile

Mobile networks are unstable. On background, iOS closes the socket after 10 seconds, Android varies. Mirror itself does not reconnect, so we implement a custom reconnect:

public class MobileNetworkManager : NetworkManager
{
    private bool wasPaused;

    void OnApplicationPause(bool pauseStatus)
    {
        if (pauseStatus)
        {
            wasPaused = true;
        }
        else if (wasPaused)
        {
            wasPaused = false;
            if (!NetworkClient.isConnected)
            {
                StartCoroutine(TryReconnect());
            }
        }
    }

    IEnumerator TryReconnect()
    {
        int attempts = 0;
        while (attempts < 5 && !NetworkClient.isConnected)
        {
            NetworkClient.Reconnect();
            yield return new WaitForSeconds(2f * attempts);
            attempts++;
        }
    }
}

According to Mirror Networking documentation, the NetworkClient.Reconnect() method is used to restore connection.

The code above is the base. Additionally we configure push notifications (APNs/FCM) to bring the player back into the active session and use NetworkManager.singleton for global access. Important: do not create multiple NetworkManager in the scene — Mirror will give a warning, but behavior becomes unpredictable.

State Synchronization: SyncVar, SyncList and Calls

[SyncVar] automatically transfers changes from server to all clients. Use hook for UI update:

public class PlayerHealth : NetworkBehaviour
{
    [SyncVar(hook = nameof(OnHealthChanged))]
    public int health = 100;

    void OnHealthChanged(int oldVal, int newVal)
    {
        healthBar.fillAmount = newVal / 100f;
    }

    [Command]
    public void CmdTakeDamage(int amount)
    {
        // Executes only on server
        health = Mathf.Max(0, health - amount);
    }
}

For collections (inventory, buff queue) use SyncList<T> with OnChange callback. The trio [Command] (client→server), [ClientRpc] (server→all clients), [TargetRpc] (server→single client) is the foundation of any multiplayer. Master them before starting integration.

Why Transport Choice Is Critical for Mobile Multiplayer

For mobile native app choose kcp2k or Ignorance. kcp2k built into Mirror since version 50+, configuration: NoDelay = true, Interval = 10ms, FastResend = 2. For mobile action, kcp2k is 5-10 times faster than TCP. Mirror's interest management system further reduces data by 20-30% per player. Using Spatial Hashing Interest Management can reduce updates by 70% in large levels. TCP (Telepathy) use for turn-based games where reliability matters more than latency. On mobile devices kcp2k provides 5-10 times lower latency compared to TCP.

Comparison of authority models:

Headless Server and Infrastructure

Mirror server is the same Unity build with flag -batchmode -nographics. For action games — one headless server per room, for strategies with few players — multiple rooms per instance. Orchestration trust to Unity Game Server Hosting (Multiplay) or Kubernetes with autoscaling. Small projects start on VPS (DigitalOcean/Hetzner) with systemd scripts. For UDP transport (kcp2k) ensure load balancer supports UDP passthrough.

Our Approach: A Real Case

For a mobile action game with up to 50 concurrent players, we integrated Mirror with kcp2k transport. We implemented a custom reconnect mechanism using exponential backoff and push notifications to restore sessions after backgrounding. The headless server ran on a VPS with Docker. After load testing, we achieved stable 10-50 ms latency even under full load, with no packet loss. Traffic optimization reduced bandwidth usage by 40% compared to the previous TCP-based solution.

Process of Work on Integration

1. Analytics — game design audit, model selection (authoritative / P2P), latency prototype.
2. Design — network architecture, synchronization scheme, reconnect & anti-cheat scenarios.
3. Implementation — NetworkManager setup, transport, SyncVar, commands, object spawning.
4. Testing — load tests (50+ clients), packet loss simulation, background behavior.
5. Deployment — headless server setup, CI/CD for updates, monitoring.

What's Included in the Work

• Network architecture (model choice, transport, load balancing).
• Mirror setup: NetworkManager, prefabs, spawning, commands.
• Implementation of reconnect and background handling.
• Build and deployment of headless server with systemd/Docker.
• Load testing under 50+ concurrent connections.
• API documentation and deployment instructions.
• Post-release support (1 month).

Typical Errors When Integrating Mirror into a Mobile Game

• NetworkIdentity not found. Prefab not registered in NetworkManager.spawnPrefabs. Spawn via NetworkServer.Spawn will crash at runtime.
• Authority confusion. isServer, isClient, isLocalPlayer, hasAuthority — four different booleans. Code in Update() without checking isLocalPlayer executes on all clients.
• Disconnect on mobile. When backgrounding, iOS closes socket after ~10 seconds. Mirror does not restore connection automatically — custom logic required.

Timelines

Basic Mirror integration with position/health sync and commands: 1–2 weeks. Full system with headless server, matchmaking, reconnect, and mobile optimization: 1–2 months. Cost is calculated individually. Contact us for a project analysis — we'll assess for free. Get a consultation on network architecture and timelines. Order Mirror integration for your game — we'll audit and propose a solution within 1 day.

How to Start Integrating API into a Mobile App?

The request goes out, the response doesn't come, timeout — 30 seconds. The user stares at the spinner. No network — mobile card in the subway. Or the network is there, but the server returns 200 with an HTML error page instead of JSON — and the app crashes on JSONDecoder.decode(). We see such cases on every second project. So integrating API into a mobile app is not just calling an endpoint, but designing a reliable network layer: error handling, caching, offline mode, certificate pinning. Order an audit of your current network layer — we will evaluate the project in 1 day. Our team guarantees a thorough analysis and provides a detailed roadmap.

Standard libraries like URLSession and OkHttp provide basic HTTP clients, but for production you need retries with exponential backoff, status code validation, typed deserialization, and network state monitoring. Without this, the app loses data and users. We have been doing mobile development for 5 years and implemented more than 30 projects with API integration on iOS, Android, and Flutter — from startups to enterprise solutions.

How to Choose a Protocol for API Integration?

REST remains the standard for most projects. But when a profile screen needs 5 fields out of 40, GraphQL eliminates over-fetching and reduces traffic by 30–60%. gRPC is justified for thousands of requests per minute (trading, IoT) — binary serialization is 3–5 times faster than JSON. WebSocket is the only choice for real-time without polling (messages, notifications).

Practical example: For a fintech app, we replaced REST (40 fields) with GraphQL — response size dropped from 12 KB to 2.5 KB, screen render time decreased by 70%. Traffic savings were significant. Our certified iOS and Android developers have deep experience with all these protocols — you can rely on proven solutions.

How to Ensure Reliable Connection and Offline-First?

Users lose network in the subway, elevator, tunnel. A mobile app must work without internet — at least in read-only mode. We implement the offline-first pattern:

1. On screen open, first show data from the local cache (Core Data / Room).
2. Simultaneously perform a network request, update UI after response.
3. If network is unavailable — show cached data and a 'no connection' label.
4. When network is restored, automatically synchronize changes.

For HTTP response caching we use URLCache (iOS) and OkHttp Cache (Android) with Cache-Control support. For structured data — SwiftData / Room. NWPathMonitor / ConnectivityManager.NetworkCallback monitor network state and trigger updates.

REST and Client Library Selection

Alamofire (iOS) — de facto standard for Swift projects. On top of URLSession it adds request chaining, response validation, automatic retry, certificate pinning via ServerTrustManager. AF.request() with .validate() returns an error for any status code outside 200–299. Without .validate(), Alamofire considers 404 and 500 as successful responses. With Swift Concurrency — async version via serializingDecodable.

Retrofit (Android) — annotation-based HTTP client on top of OkHttp. An interface with annotations compiles into implementation. @GET, @POST, @Path, @Query, @Body — declarative API description. OkHttp under the hood: connection pooling, transparent gzip, HTTP/2 multiplex. HttpLoggingInterceptor — logging in debug builds. Authenticator — automatic token refresh on 401.

Ktor (KMM/Flutter) — multiplatform HTTP client. On iOS it works via Darwin engine (URLSession), on Android — via OkHttp. Single code for both platforms with KMM architecture.

GraphQL: When REST Falls Short

REST returns a fixed structure. A profile screen needs name, avatar, email — the server sends 40 fields. Over-fetching. GraphQL solves this: the client requests exactly the needed fields. This is critical for mobile where traffic and parsing time are real constraints. Apollo iOS and Apollo Kotlin generate typed classes from schema: schema.graphql + query files → strict types at compile time. Subscriptions via WebSocket — real-time without polling. Limitation: GraphQL is harder to cache at the HTTP level. Apollo uses a normalized in-memory cache InMemoryNormalizedCache — requests with overlapping data update the cache without duplication.

WebSocket: Real-Time Without Extra Traffic

Polling (setInterval every 5 seconds) — battery and traffic waste. WebSocket is a persistent bidirectional connection. iOS: URLSessionWebSocketTask (native, iOS 13+). Android: OkHttp WebSocket. Mandatory reconnect handling: on onFailure — exponential backoff (1s → 2s → 4s → 8s → max 60s). Socket.IO is an overlay with automatic reconnect, but for new projects native WebSocket is preferable (fewer dependencies).

gRPC: For High-Load Services

gRPC with protobuf — binary serialization: smaller size, faster parsing. grpc-swift for iOS, grpc-kotlin for Android. The protobuf schema compiles to typed classes. Streaming (server-side, client-side, bidirectional) is a native feature. Application threshold: high request frequency (trading, IoT) or critical latency. For regular CRUD, REST is simpler to debug and monitor.

Certificate Pinning and Security

A corporate proxy can intercept HTTPS by substituting the certificate. Certificate pinning prevents this: the app accepts only a specific certificate or public key. Alamofire: ServerTrustManager with PinnedCertificatesTrustEvaluator. OkHttp: CertificatePinner with SHA-256 hash. Apple's App Transport Security documentation recommends pinning certificates for sensitive data. Operational complexity: on certificate rotation, older app versions stop working. Solution — pinning to the CA public key or support multiple pins with a grace period.

What Is Included in the Work

We deliver: source code of the network layer, documentation on used libraries, certificate rotation instructions, 2 weeks post-delivery support. Our experience guarantees that the solution will be stable and maintainable.

Timeline and Cost

Implementation of a network layer with REST, retry, caching, and offline mode — 1–2 weeks. Adding GraphQL or WebSocket — another 1–2 weeks. gRPC — 2–3 weeks, including code generation. The cost is calculated individually after analyzing the API and offline behavior requirements. We will evaluate the project in 1 day — contact us for a consultation. Get a reliable API integration with guaranteed quality.