Order Book Implementation for Mobile Exchange Apps

We have been developing mobile exchange applications for over 5 years and have completed 30+ projects with real-time data integration. One of the most demanding components is the order book. Data updates every 100 ms, the list can contain up to 500 price levels, and the interface must remain responsive even under peak load. Without optimization, the app lags at just 50 levels — users flee to competitors. We handle all technical challenges: from protocol selection and snapshot synchronization to rendering virtualization and decimal precision handling. Contact us for a consultation on implementing an order book tailored to your exchange.

How to Avoid Lags When Rendering the Order Book

Rendering the order book is the primary source of performance issues. 100 price levels × updates every 100 ms = 10,000 updates per second. On a mobile device, this causes lags without optimizations.

Virtualization is the key technique. We display only visible levels, not all 100. On iOS — UITableView with reloadRows(at:with:) for changed rows, not reloadData(). On Android — RecyclerView with DiffUtil to compute minimal changes. In Flutter — ListView.builder with itemCount. This reduces UI load by 2.5x.

Batching updates. Do not update the list on every WebSocket event. We accumulate updates and apply them every 250–500 ms. The user does not notice the difference, and the renderer does 2.5x less work.

Colors and highlighting: on price decrease — red background, on increase — green, then smoothly return to neutral. We implement this via color animation with CABasicAnimation (iOS) or ValueAnimator (Android). Do not keep timers on each row — use a single timer for the entire list.

Data Source: WebSocket

The exchange order book updates via WebSocket — HTTP polling is unacceptable due to latency. WebSocket provides 10+ times lower delay than polling, which is critical for trading. Standard approach: get a snapshot via REST, then subscribe to incremental updates via WS.

Example for Binance API (pattern used by most exchanges):

GET https://api.binance.com/api/v3/depth?symbol=BTCUSDT&limit=100
→ snapshot with full bids and asks

WSS wss://stream.binance.com:9443/ws/btcusdt@depth@100ms
→ incremental updates every 100ms

Applying incremental updates: if a price level already exists in the book, update quantity. If quantity is 0, remove the level. If price is new, add it. This is the standard diff algorithm for an order book. The Binance API documentation describes this method.

How to Sync Snapshot and Stream?

A critical point often implemented incorrectly: the WebSocket starts sending updates before the REST request for snapshot has returned. You must buffer WS events, obtain the snapshot with its lastUpdateId, then apply all buffered events with firstUpdateId <= lastUpdateId + 1. Missed an event? Desynchronized? The only way out is to reconnect and get a new snapshot. Do not attempt to recover state from partial data.

Why Is Number Precision Critical for Order Book?

Prices and volumes on exchanges are decimals with high precision. BTC trades with 8 decimal places. Using Double leads to rounding errors. We use Decimal (iOS) or BigDecimal (Android) for correct display and summation. Comparison: Double gives up to 0.0001% error over 1000 operations, while Decimal gives zero. Formatting: different trading pairs have different tick sizes (minimum price step). For BTC/USDT tick size is 0.01, for altcoins up to 8 decimals. The number of displayed decimals is taken from pair metadata, not hardcoded.

Comparison of Synchronization Approaches

There are three main ways to synchronize order book data. The first is periodic full snapshot requests: simple to implement, but generates high traffic and increases latency. The second is subscribing to incremental updates via WebSocket: low latency, but complex synchronization, especially on packet loss. The optimal is hybrid: one-time snapshot on connection, then incremental updates. This approach requires buffering WS events until snapshot receipt and order correction, but gives the best balance of performance and reliability. We use this in all projects — it reduces traffic by 20x compared to full snapshot and provides update latency under 50 ms.

Step-by-Step Synchronization Implementation

1. Establish WebSocket connection and start buffering all incoming messages.
2. Send REST request to obtain snapshot with the last update id.
3. After receiving the snapshot, apply buffered events with firstUpdateId <= lastUpdateId + 1.
4. If event loss or desynchronization is detected — reconnect and repeat steps 1-3.
5. After successful synchronization, switch to real-time stream processing using the diff algorithm.

Depth Chart

Visualize volumes via an accumulated histogram (depth chart) — we accumulate volume from the best price to worst. Draw using CAShapeLayer / Canvas / CustomPainter in Flutter. Update no more than once per second — it's a visualization, not a trading tool.

Offline and Reconnection

On connection loss, we clear the book and show a "No Data / Reconnecting" state. Do not display an outdated book as current — it misleads during trading. Reconnection logic: exponential backoff from 1 s to 30 s. After restoration, we re-fetch the snapshot and resubscribe.

What's Included

• Architecture of WebSocket connection with snapshot/incremental synchronization.
• Implementation of virtualized list with batching and animation.
• Integration of depth chart and number formatting with tick size.
• Handling offline mode and reconnection with exponential backoff.
• Testing on real data and performance optimization.
• Documentation and source code delivery.

Cost and Savings

The cost of order book implementation is calculated individually — it depends on integration complexity, number of trading pairs, and customization needs. On average, ordering a ready module costs 30-50% less than developing from scratch and saves 2-4 weeks of team time. Contact us for a project estimate.

We guarantee correct synchronization and responsive interface under any load. Get a consultation — we will analyze your API and propose the optimal solution.

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.