Liveblocks for Mobile Apps: Real-Time Collaboration

Two users simultaneously edit a task list: one on an iPhone, the other on an Android. Data diverges quickly, conflicts pile up, and the final state is unpredictable. REST API doesn't provide real-time, and building a custom WebSocket server with CRDT takes months of development and debugging. Data loss due to conflicts can reach 15% of all changes.

We integrate Liveblocks—a managed infrastructure for collaborative editing. It provides a ready-made WebSocket server, CRDT storage (based on Liveblocks Storage), presence, comments, and notifications via a cloud API. In the browser, integration takes a day; in a React Native mobile app, from a week. This accelerates time to market by 3–6 times compared to building from scratch. Infrastructure cost savings can be significant.

What Liveblocks gives out of the box?

• Storage — CRDT storage based on its own implementation with LiveObject, LiveList, LiveMap. Changes replicate between clients in <100 ms within the same region.
• Presence — ephemeral user state: cursor position, selection, status. Not persisted, only online.
• Yjs integration — via @liveblocks/yjs you can use Yjs documents with web editors (Tiptap, Slate).

According to Wikipedia, CRDT guarantees consistency in distributed systems.

How to connect Liveblocks in React Native?

1. Install packages: npm install @liveblocks/client @liveblocks/react
2. Create a client with createClient and configure authentication.
3. Define Presence and Storage types for your app.
4. Export hooks via createRoomContext.
5. Wrap the editor screen in RoomProvider.

import { createClient } from '@liveblocks/client';
import { createRoomContext } from '@liveblocks/react';

const client = createClient({
  authEndpoint: '/api/liveblocks-auth',
  // or publicApiKey for prototypes
});

type Presence = {
  cursor: { x: number; y: number } | null;
  selectedItemId: string | null;
};

type Storage = {
  items: LiveList<{ id: string; text: string; done: boolean }>;
};

export const { RoomProvider, useMyPresence, useStorage, useMutation } =
  createRoomContext<Presence, Storage>(client);

RoomProvider wraps the editor screen. Inside, useStorage gives an immutable snapshot, useMutation — transactional mutations.

Issue in RN: @liveblocks/client uses fetch and WebSocket, which are available, but EventSource (SSE for notifications) is missing without a polyfill. Install react-native-event-source and a global polyfill:

import EventSource from 'react-native-event-source';
global.EventSource = EventSource;

Get a consultation on client setup and polyfills—this saves you up to 40% of integration time.

What is Presence in a mobile context?

In a browser, presence means mouse coordinates. In a mobile app, other use cases:

• Collaborative task list editing: presence = { focusedItemId: string | null } — highlight the item being edited.
• Collaborative whiteboard: presence = { x, y, tool: 'pen'|'eraser' } — show the stylus.
• Document editor: presence = { selection: { anchor, focus } | null } — text selection.

Use useOthersConnectionIds and useOther for reactive presence data. For optimization, useOthersMapped selects only necessary fields.

Why choose Liveblocks for a mobile app?

The comparison shows: Liveblocks wins on integration speed but falls short on offline mode and data control. For most MVPs and medium projects, this is sufficient.

Offline mode: what is not included out of the box

Liveblocks does not provide offline persistence. When the network is absent, changes are lost. We solve this with a mutation buffer in AsyncStorage:

const [pendingMutations, setPendingMutations] = useAtom(pendingMutationsAtom);

NetInfo.addEventListener(state => {
  if (!state.isConnected) {
    const snapshot = storage.toObject();
    AsyncStorage.setItem('offline_snapshot', JSON.stringify(snapshot));
  } else {
    pendingMutations.forEach(mutation => mutation());
    setPendingMutations([]);
  }
});

This is not true CRDT offline—merge is not guaranteed with concurrent offline changes. For a full solution, combine with Yjs via @liveblocks/yjs and a custom local provider. More complex but correct.

AppState and reconnect

iOS kills WebSocket when in background. The SDK auto-reconnects, but room.getStatus() goes through 'reconnecting'. If the UI doesn't react, the user sees stale state. Handle it explicitly:

const status = useStatus();
if (status === 'reconnecting') {
  return <ReconnectingBanner />;
}

What's included in the work

• Setting up Liveblocks client and authentication provider.
• Integrating Storage and Presence for your use case.
• Implementing an offline buffer (optional).
• Yjs integration for compatibility with web editors.
• Testing reconnect and appState handling.
• Documentation and team training.
• 2 weeks of support after deployment.

Order a demo project with basic integration—we'll show how Liveblocks works in your context. Contact us for a project estimate within 1–2 business days.

How we estimate the project

Indicative timelines:

• Basic integration (Storage + Presence, no offline): 2–4 weeks.
• With offline buffer: 3–6 weeks.
• With Yjs and full offline: 6–10 weeks.

Cost is calculated individually after analyzing your MVP. Get a consultation—we'll estimate the project within 1–2 business days.

Our experience: more than 5 years in mobile development, 15+ projects with real-time synchronization. We have worked with Liveblocks since its public release.

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.