WebSocket API Development for Mobile Apps

Picture this: a user opens a chat on the subway, sends a message—and it gets lost because the phone switched from LTE to Wi-Fi. Or an iOS app in the background receives a push, but when the user returns, the data doesn't update. This is classic: without a well-designed WebSocket API, every network change turns into event loss. We've been building real-time solutions for mobile platforms since 2019, completed 25+ projects on iOS and Android—and we know how to design an API that withstands disconnections without loss.

Our data shows: a properly implemented WebSocket API with replay reduces message loss by 95% even under frequent network switches. WebSocket is 10 times more efficient than classic polling in terms of traffic and 5 times faster in delivery time. Below are architectural solutions battle-tested in production.

Protocol over WebSocket

Raw WebSocket is a transport, not a protocol. You need to define a message format on top. Minimal schema:

{
  "type": "message.new",
  "id": "uuid-v4",
  "payload": { ... },
  "timestamp": 1711234567890
}

type—client-side routing. id—idempotency: client ignores duplicates on reconnect. timestamp—state synchronization.

Popular protocols over WebSocket: STOMP (works well with Spring Boot, rich client ecosystem), Socket.IO (polling fallback, rooms out of the box, but ties to JS ecosystem), custom protocol (maximum control, but more work at all levels). Comparison:

Custom protocol using Protobuf or MessagePack saves up to 40% traffic compared to JSON frames of STOMP—critical for mobile apps with limited data plans.

How to Restore State After Disconnection?

Simple reconnection is not enough. The server must replay missed events.

Server side: each event has a monotonically increasing sequence or cursor. On reconnect, the client sends the last received cursor:

{ "type": "subscribe", "channel": "chat.123", "lastSeq": 4521 }

The server responds with events where seq > 4521. Storage window is typically 24–72 hours. If the client was offline longer, send a full state snapshot.

Without this mechanism, every connection break means missed messages—especially critical on Android with Doze Mode. Our experience shows: properly implemented replay reduces data loss by 95% even under frequent disconnections.

Authentication and Authorization

WebSocket connection is authenticated at handshake via query parameter or first message:

wss://api.example.com/ws?token=eyJ...

Query parameter is simpler, but the token ends up in logs. Preferred: establish connection, send auth frame with token, wait for auth_ok from server before any subscriptions.

Token expiration during a session is a real scenario. The server should send a token_expiring warning 60 seconds before expiration; the client fetches a new token and sends a new auth frame without breaking the connection.

Scaling the Backend

A single server instance cannot hold all client connections. Under horizontal scaling, a message arriving at server A must reach clients on servers B and C. Standard solution: pub/sub via Redis (PUBLISH/SUBSCRIBE). Each server subscribes to channels and forwards messages to its WebSocket clients.

Infrastructure alternatives: Ably (hosted WebSocket infrastructure), Pusher Channels, AWS API Gateway WebSocket—they reduce operational load at the cost of price and less control. If you choose a hosted solution, expect vendor lock-in and additional costs under high load. Comparison:

Client Implementation

On Android—OkHttp WebSocket with pingInterval for heartbeat. On iOS—URLSessionWebSocketTask. Implementation details are covered in the article on WebSocket chat. Important: during API design, agree on maximum message size (WebSocket frame limit), error format, and graceful connection closing (1000 Normal Closure vs 1011 Internal Error).

Why Choose a Custom Protocol Over a Ready-Made One?

A custom protocol saves up to 40% traffic compared to STOMP JSON frames, and you are not tied to third-party libraries. However, it requires 2–3 times more development time. If you have simple logic (one event type, low load)—Socket.IO or STOMP is enough. If the app is traffic- and latency-critical—we write a custom protocol on Protobuf or MessagePack.

What's Included in the Work

We design the protocol over WebSocket, implement server-side with replay mechanics, authentication, and heartbeat, and integrate a client SDK for the required platforms. All event types are documented.

Timeline: 6–12 business days, including server part and testing on unstable networks. Contact us for a free assessment of your project—we'll evaluate complexity and timeline at no charge. Order turnkey WebSocket API development with a 3-month warranty on all connections.

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.