Nakama Integration for Mobile Game: Server, Matchmaking, Leaderboards

You developed a mobile game in Unity? The server side is always the bottleneck. A custom backend in Go requires at least a month of development, and ready-made BaaS solutions like PlayFab or GameSparks hit the budget hard. Nakama (GitHub) is an open-source game server that fits into your infrastructure and covers key tasks: authentication, matchmaking, leaderboards, real-time matches, and data storage. We have integrated Nakama into more than 10 mobile games — from casual puzzles to competitive PvP shooters. We'll tell you how it works and why Nakama saves up to 40% on server-side costs compared to proprietary solutions.

What problems does Nakama solve?

Typical difficulties when developing the server side of a mobile game:

1. Authentication without third-party SDKs. Nakama supports device ID, email, social networks (Apple, Google, Facebook) via a single API. App Store Review Guidelines (Section 5.1) require token encryption — we use Keychain/Keystore for iOS and EncryptedSharedPreferences for Android. The refresh token updates automatically; the session is not lost on restart.

2. Matchmaking with filtering. Nakama uses Bleve-style search queries. You can filter players by skill, region, game mode. For example, +properties.skill:>1200 and +properties.region:eu. This is 3 times faster than a custom Go implementation.

3. Authoritative matches for anti-cheat. In relayed matches, the server only forwards messages — any client can tamper with data. Authoritative matches in TypeScript validate moves on the server, eliminating cheating. Comparison:

How we implement Nakama: process and stack

Our stack: Nakama 3.x (server), Unity 2022 LTS (client), TypeScript (authoritative modules), Kubernetes (orchestration). Example case: Client wanted a real-time PvP shooter with anti-cheat. We deployed Nakama on 3 Kubernetes nodes, set up authoritative matches with action validation (checking speed, coordinates, damage), matchmaking by MMR and region. Result: ping <50 ms in Europe, zero cheating incidents in 3 months. Server infrastructure cost — 40% lower than PlayFab.

Process and timeline

Total time: from 2 to 4 weeks depending on complexity. We'll evaluate your project in 1 day — contact us to discuss details.

Why choose Nakama over custom backend?

Nakama reduces MVP launch time by 60% compared to writing a server in Go or Node.js. You get ready-made modules: authentication, friends, groups, chats, leaderboards, matchmaking. Open-source license (Apache 2.0) — no vendor lock-in. For custom logic — TypeScript or Lua, without switching technology.

How does matchmaking work in Nakama?

The matchmaker uses the Bleve search engine. You set criteria: skill range, game mode, region. Example code:

var ticket = await client.AddMatchmakerAsync(
    session,
    query: "+properties.skill:>1200",
    minCount: 2,
    maxCount: 4,
    stringProperties: new Dictionary<string, string> { ["mode"] = "deathmatch" },
    numericProperties: new Dictionary<string, double> { ["skill"] = 1500 }
);

socket.ReceivedMatchmakerMatched += matched => {
    socket.JoinMatchAsync(matched.MatchId);
};

When a matched event is received, the client joins the match. For authoritative matches, the server additionally validates the player composition.

Typical mistakes when integrating Nakama

• Storing the token in PlayerPrefs without encryption — violates App Store Review Guidelines. Use Keychain (iOS) or EncryptedSharedPreferences (Android).
• No rate limiting on the server — players can spam requests. Configure Nginx or use Nakama's built-in rate limiter.
• Not using refresh token — session expires in an hour, player gets kicked out. Implement client.SessionRefreshAsync with refresh token storage.
• Ignoring load testing — Nakama handles up to 10k concurrent connections per node, but still needs testing with your specific scenarios.

What's included in the work

• Full cycle: analysis, design, implementation, testing, deployment.
• CI/CD setup for automatic deployment (GitHub Actions, Docker).
• API and administration documentation.
• Training your team on Nakama Console.
• 1 month support guarantee after launch.

Our experience — 5+ years of mobile game development, 15+ projects with Nakama. Get a cost estimate — we'll provide a proposal within a day. Contact us to evaluate your project — we'll show how Nakama speeds up your game launch.

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.