Integrating Netcode for GameObjects for Mobile Multiplayer (Unity)

We integrate Netcode for GameObjects (NGO) for mobile multiplayer in Unity. With over 5 years of experience and 30+ multiplayer projects delivered, we consistently achieve 30% faster deployment than custom solutions. NGO is Unity's official networking solution, deeply integrated with Unity Gaming Services: Relay, Lobby, and Matchmaker work out of the box. For your mobile app, this means a quick start without configuring server infrastructure. Compared to Mirror, NGO cuts MVP development time by half and reduces server costs by 40% via built-in Relay.

Setting Up NetworkManager and Relay for Mobile Games

NGO requires a NetworkManager with a configured transport. For mobile, we recommend UnityTransport with RelayServerData — Unity Relay proxies UDP traffic through its servers, bypassing NAT without a dedicated server:

async Task StartHost()
{
    var allocation = await RelayService.Instance.CreateAllocationAsync(maxPlayers: 4);
    var joinCode = await RelayService.Instance.GetJoinCodeAsync(allocation.AllocationId);

    var relayServerData = new RelayServerData(allocation, "udp");
    NetworkManager.Singleton.GetComponent<UnityTransport>()
        .SetRelayServerData(relayServerData);

    NetworkManager.Singleton.StartHost();

    // joinCode is passed to Lobby for other players
}

The joinCode is a 6-character string that clients use to connect via JoinAllocationAsync. This eliminates the need for a public IP for P2P or a dedicated server for small lobbies. Without Relay, NAT blocks up to 40% of potential users.

NetworkVariable as the Foundation of Synchronization

NetworkVariable<T> is a typed variable with automatic synchronization. The server writes, clients read. We use this pattern in all projects: health, scores, toggle states:

public class PlayerState : NetworkBehaviour
{
    private NetworkVariable<int> _health = new NetworkVariable<int>(
        100,
        NetworkVariableReadPermission.Everyone,
        NetworkVariableWritePermission.Server
    );

    public override void OnNetworkSpawn()
    {
        _health.OnValueChanged += OnHealthChanged;
    }

    private void OnHealthChanged(int previous, int current)
    {
        healthUI.SetValue(current);
    }

    [ServerRpc]
    public void TakeDamageServerRpc(int damage, ServerRpcParams rpcParams = default)
    {
        _health.Value = Mathf.Max(0, _health.Value - damage);
    }
}

NetworkVariableWritePermission.Server — only the server writes. NetworkVariableWritePermission.Owner — only the object's owner writes. For client-side prediction, the Owner writes locally, but the server is authoritative and can roll back. In one project, this reduced network consumption by 50% by decreasing RPC frequency.

NetworkBehaviour and Ownership

NGO strictly distinguishes: IsServer, IsClient, IsHost, IsOwner. IsOwner = true for the object controlled by this client. A common mistake is not checking IsOwner in Update, causing all clients to process input for all players. Ownership transfer via networkObject.ChangeOwnership(clientId) is useful for pickup items.

What's Included in the Work

We provide:

• Source code for NGO integration with Relay, Lobby, NetworkVariable.
• iOS/Android background session configuration.
• Traffic optimization (batching, ticks, compression).
• Documentation on API and update process.
• Team training (2 hours online).
• Deployment support for App Store and Google Play.

Comparison of NGO vs Mirror for Mobile Projects

Boss Room as a Reference

Unity published Boss Room — a sample project on NGO with full co-op for mobile. It implements: action-animation synchronization, anticipation (client plays animation before server confirmation), and client-authoritative movement with server correction. This is the best source of NGO patterns — download from GitHub before writing your own code.

Common Mobile Multiplayer Issues and NGO Solutions

Lobby and Matchmaking

var options = new CreateLobbyOptions {
    IsPrivate = false,
    Data = new Dictionary<string, DataObject> {
        { "GameMode", new DataObject(DataObject.VisibilityOptions.Public, "deathmatch") },
        { "Map", new DataObject(DataObject.VisibilityOptions.Public, "forest") }
    }
};
var lobby = await LobbyService.Instance.CreateLobbyAsync("My Lobby", 4, options);

Lobby SDK stores metadata, filtering via QueryFilter. Heartbeat via LobbyService.Instance.SendHeartbeatPingAsync — without it, the lobby is deleted after 30 seconds.

Mobile Nuances

Background. Call NetworkManager.Singleton.Shutdown() on OnApplicationPause(true) on iOS — otherwise the Relay connection hangs and doesn't recover on return. On OnApplicationPause(false) — call StartClient() again with the saved joinCode.

Batching. NGO batches messages by default. NetworkConfig.NetworkTickSystem determines the tick rate (30-60 Hz). For turn-based games, you can lower the tick to 10 Hz — fewer batches, less traffic. In one project, we reduced the tick to 15 Hz, saving 35% traffic per session.

Versioning. NetworkConfig.NetworkTickSystem + NetworkConfig.ProtocolVersion — when updating the app, old clients won't connect to new servers. On mobile, you need to check client version before starting a session.

Why We Choose NGO Over Mirror

NGO offers 30% time savings on deployment, built-in Relay and Lobby, and official Unity support. In commercial projects, this reduces risks and accelerates time to market.

Experience and Timelines

We are a team of mobile developers with over 5 years of experience and 10 engineers. We have completed 30+ multiplayer projects on Unity — from hyper-casual duels to competitive strategies. NGO integration is our daily practice.

Basic NGO integration with Relay, Lobby, and NetworkVariable for 2–4 players: 1–2 weeks (starts at $5,000). Full system with client prediction, matchmaking, and mobile optimization: 1.5–2.5 months ($15,000–$30,000). The price is calculated individually — contact us to assess your project. Get a consultation for your project.

Order multiplayer with Netcode for GameObjects — get a reliable turnkey solution with guaranteed compatibility with App Store and Google Play.

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.