Real-Time Collaborative Editing in Mobile Apps: A Developer's Guide

Why Collaborative Editing is Hard in Mobile Environments

Note: When two engineers simultaneously edit the same document, mobile environments introduce three scenarios: unstable networks with packet loss (up to 30% on weak signal), background synchronization after offline mode, and native keyboard with composition events – input latency of 300+ ms. We encountered this in a corporate editor for 500+ users, where we had to balance ACID guarantees with UI responsiveness. Our team implements such solutions turnkey using proven algorithms. With 5+ years of experience and 10+ projects, we guarantee stable synchronization even with network delays up to 2 seconds.

Choosing a Synchronization Algorithm: OT vs CRDT

OT is proven in Google Docs and Apache Wave – server coordinates operations, eliminating conflicts. CRDT (Y.js – de facto standard) does not require a server: merge works locally. For a mobile corporate editor we choose OT; for offline-first editing, CRDT is 2x faster in sync time. See Wikipedia: Operational Transformation and Yjs Documentation for details.

How Y.js Solves Collision Issues in React Native

yjs is pure JavaScript, works in React Native without modifications. Typical setup:

import * as Y from 'yjs';
import { WebsocketProvider } from 'y-websocket';

const ydoc = new Y.Doc();
const provider = new WebsocketProvider('wss://your-server.com/sync', 'doc-room-id', ydoc);
const ytext = ydoc.getText('document');

YText is a CRDT type with formatting support (bold, italic, headers). Integration with web editors via WebView gives a quick MVP. For native UX, a custom TextInput with manual synchronization via Y.js operations. On iOS: UITextViewDelegate, on Android: TextWatcher. For performance, use line height 18sp and debounce 200ms.

How to Implement Y.js in React Native

To implement Y.js in a React Native collaborative editor, follow these steps:

1. Install dependencies: npm install yjs y-websocket.
2. Create a Y.Doc and connect to a WebSocket provider with a room ID.
3. Obtain a Y.Text type for the document content.
4. Bind the Y.Text to a native TextInput using a custom bridge for iOS/Android.
5. Implement cursor awareness using the Awareness protocol.
6. Persist document state to SQLite on changes using Y.encodeStateAsUpdate.
7. Reconnect and sync on app resume.

Cursors and Awareness

Y.js Awareness Protocol distributes ephemeral data (cursors, presence) among participants. Not stored in the document:

provider.awareness.setLocalState({
  user: { name: 'Ivan', color: '#3B82F6' },
  cursor: { anchor: 45, focus: 45 }
});

provider.awareness.on('change', () => {
  const states = Array.from(provider.awareness.getStates().values());
  // update other users' cursor positions
});

Displaying other cursors in native TextInput is non-trivial. Need to convert character position to pixel coordinates using UITextView.caretRect(for:) on iOS and Layout.getDesiredWidth() on Android. For this, we use Y.js Awareness and custom calculations – pixel accuracy at 60fps.

How Are Formatting Conflicts Resolved?

Y.js YText formatting works via Delta operations with attributes. Concurrent formatting (one user makes bold, another italic on overlap) – both attributes apply. For semantically incompatible operations (H1 vs H2), Y.js selects based on clientId, but UI should warn or allow manual resolve. In one project, we added a modal dialog – users resolve conflict in 2 seconds.

Persistence and History

Y.js document serializes to Uint8Array via Y.encodeStateAsUpdate(). On mobile, store in SQLite using react-native-sqlite-storage. On open: load saved state, apply via Y.applyUpdate(), then connect to WebSocket for diff. Server uses y-leveldb or y-redis for persistence. Optimization: snapshots every 100 operations – load time <500ms.

Comparison: Native vs WebView

For mobile app synchronization, native TextInput with Y.js offers 3x better performance compared to WebView, essential for smooth cursor rendering.

What Is Included in the Work

• Analysis: Scenario evaluation and algorithm selection (OT/CRDT).
• Architecture: Design of synchronization using WebSocket sync.
• Implementation: Text editor with native rendering and Y.js or OT server.
• Cursors: Development of cursor awareness and display.
• Testing: Real device testing with poor network emulation (30% packet loss).
• Deliverables:
  • Documentation: user guides, API references, and architecture diagrams.
  • Access: source code repository and server credentials.
  • Training: team workshops on maintenance and scaling.
  • Support: 1 month post-deployment including bug fixes.

Typical MVP costs range from $20,000 to $40,000, with potential savings of up to 30% compared to full custom development. Project costs start at $20,000 for an MVP, and we offer a 10% discount for early commitments.

Get a consultation – we will assess your project. Write to us – we will show code examples.

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.