Crypto Exchange Mobile App Development

A typical problem for crypto exchanges is user churn due to order book lag on mobile devices. At 50 updates per second, standard lists freeze and cause frustration. We solve this with custom Canvas rendering and protocol optimization. Your trading platform will get a real-time order book, candlestick charts, order management, a built-in wallet, and security on par with top exchanges. Each component is a separate engineering solution optimized for mobile performance.

Mobile Exchange App: Architecture and Rendering

Native development (Swift/SwiftUI for iOS, Kotlin/Jetpack Compose for Android) provides direct GPU access and low-level APIs. Cross-platform solutions like Flutter or React Native add a layer that increases order book render latency by 30–50% under peak load. The native stack is 2–3 times faster for order book rendering. App Store Review Guidelines Section 5.1 directly regulates private key storage on the device, which is easier to comply with in native development.

What Technologies Enable Real-Time?

On iOS — URLSessionWebSocketTask (iOS 13+) or the Starscream library. Data flow via AsyncStream and @Published for SwiftUI. On Android — OkHttp WebSocket with Kotlin Coroutines and StateFlow. Example connection:

class ExchangeWebSocketClient(private val scope: CoroutineScope) {
    private val _orderBook = MutableStateFlow<OrderBookSnapshot?>(null)
    val orderBook = _orderBook.asStateFlow()

    fun subscribeOrderBook(symbol: String) {
        val request = """{"method":"SUBSCRIBE","params":["${symbol.lowercase()}@depth20@100ms"],"id":1}"""
        webSocket.send(request)
    }

    private fun handleMessage(text: String) {
        val update = json.decodeFromString<OrderBookUpdate>(text)
        _orderBook.update { current -> current?.applyDelta(update) ?: OrderBookSnapshot.from(update) }
    }
}

More on the WebSocket protocol.

How to Avoid FPS Drops When Updating the Order Book?

1. Establish a WebSocket connection with a binary protocol (MessagePack, FlatBuffers).
2. Subscribe to the depth20@100ms stream for the order book.
3. Process incoming messages on a background thread, applying deltas to the current order book.
4. For rendering, use performBatchUpdates (iOS) or DiffUtil (Android) at up to 20 updates/sec. At higher frequencies, draw the order book on Canvas/SurfaceView (Android) or CALayer (iOS) — this reduces main thread load by 3–5 times.

Key Components of a Crypto Exchange

We start with a backend audit and client-server interaction design. We use WebSocket for data streams and REST for static queries. A binary protocol for market data is critical at update frequencies of up to 50 times per second.

Candlestick Charts: From Simple to Advanced

For TradingView-style charts we use:

• TradingView Lightweight Charts in WKWebView — quick integration.
• MPAndroidChart / Charts (Daniel Gindi) — native but less feature-rich.
• Custom implementation on Canvas or Metal — full control, but 2–4 weeks of development.

The choice depends on customization and performance requirements.

Order Types and Their Implementation

The order form includes a Buy/Sell toggle, Price/Amount/Total fields with mutual recalculation, a percentage slider of balance, and a confirm button.

Case Study: Reducing Order Book Render Time

On one exchange project, the order book updated 50 times per second, causing the standard list to drop to 15 FPS. We implemented a Canvas-based renderer that processes deltas in native code and draws only visible rows. The result: render time dropped from 8ms to 1.2ms, FPS stabilized at 60, and user engagement increased by 20%.

Work Process and Stages

Analysis → design → implementation → testing → deployment. We guarantee compliance with App Store Review Guidelines Section 4.2/5.1 and Google Play policies. Unit tests cover models and business logic, UI tests cover key scenarios, load tests simulate 1000+ concurrent WebSocket connections.

What’s Included in the Work

• Documentation: API specification (OpenAPI), architectural diagram, flow descriptions.
• Access: to repository (GitHub/GitLab), CI/CD (GitHub Actions/App Center), TestFlight/Firebase Distribution.
• Training: workshop for your team on operation and code modification.
• Support: 6-month code warranty, consultation on further development.

Timeline and Budget Considerations

Total MVP: 8–10 weeks for one platform. Both platforms in parallel with a shared backend — 10–14 weeks. Cross-platform development can save up to 30% of budget, but for crypto exchanges we recommend native for performance.

We guarantee security: two-factor authentication (TOTP per RFC 6238), biometrics, push notifications for logins and withdrawals. Our team has 5+ years in mobile development and 20+ fintech projects.

Contact us to evaluate your project — we'll find the optimal solution. Request an MVP development and get an architect consultation.

Payments in Mobile Apps: In-App Purchase, StoreKit 2, Google Billing, Stripe, RevenueCat

In every monetization project, we balance App Store and Google Play policies, PCI DSS requirements, and purchase verification logic on the backend. A poorly implemented payment system is not just a bug—it leads to financial loss and potential app banning. Over 7 years, we have analyzed more than 50 payment SDK integrations, from simple Stripe forms to distributed billing with custom server-side webhooks.

In-App Purchase: Two Platforms, Two Different APIs

If your app sells digital content or subscriptions, Apple and Google require you to use their payment systems. This is non-negotiable: violating App Store rule 3.1.1 or Google Play Developer Policy results in app removal. Physical goods and offline services are a different story.

StoreKit 2 (iOS 15+)

StoreKit 2 is a complete overhaul of the original StoreKit with async/await API. Product.products(for:), product.purchase(), Transaction.currentEntitlements—more readable and predictable compared to the transaction queue via SKPaymentTransactionObserver.

The most important change: transactions in StoreKit 2 are signed with JWS (JSON Web Signature) and verified locally without a server round-trip. Transaction.verificationResult returns .verified(Transaction) or .unverified(Transaction, VerificationError). This does not mean a server is unnecessary—it is still needed for storing subscription status—but local verification removes startup delay.

StoreKit.AppTransaction verifies the actual app download from the App Store. Required for paid downloads or non-renewing purchases.

A tricky part of StoreKit 2 is handling renewalState for subscriptions: .subscribed, .expired, .inBillingRetryPeriod, .inGracePeriod, .revoked. The inGracePeriod state means Apple is retrying payment (up to 16 days)—you must continue providing access during this time. Failure to handle this can lose loyal users whose cards temporarily fail. Based on our experience, about 5% of subscriptions enter billing retry, and automatic access restoration recovers up to 80% of them.

Google Play Billing Library (v6+)

Google Billing is more complex than StoreKit in terms of scenario handling. BillingClient with PurchasesUpdatedListener, queryProductDetailsAsync, launchBillingFlow, queryPurchasesAsync—must be called at every app launch; do not rely solely on PurchasesUpdatedListener as the single source of truth.

Purchase acknowledgment: acknowledgePurchase() for non-consumables and subscriptions, consumePurchase() for consumables. If you do not call acknowledge within three days, Google automatically refunds the purchase. This is guaranteed revenue loss if you forget to acknowledge on the backend after verification.

ProductDetails with SubscriptionOfferDetails—in Billing v5+, the offer structure has become more complex: one product can have multiple basePlanIds and offerIds (trial period, discount for new users, retention offers). BillingFlowParams.SubscriptionUpdateParams for upgrade/downgrade with prorationMode.

Why Is Server-Side Verification Mandatory?

Never trust only client-side code when unlocking paid content. Client-side verification can be bypassed by modifying the app.

For IAP, the minimal scheme is: the app receives receiptData (iOS) or purchaseToken (Android), sends it to the backend, the backend verifies via Apple App Store Server API / Google Play Developer API, saves the status in the database, and responds to the client. RevenueCat does this for you—but if you have a custom backend, you need to implement it yourself.

Webhooks are more important than they seem. Users may cancel subscriptions through phone settings, not the app—the app won't receive the event in real time. Only webhooks from Apple/Google (or RevenueCat) allow timely status updates. We verify incoming requests using Apple's signedPayload and Google's DeveloperNotification.

How Does RevenueCat Simplify Integration?

Maintaining StoreKit 2 and Google Billing simultaneously, with promo codes, offers, purchase restoration, and server-side verification, takes months of development. RevenueCat handles most of this layer.

RevenueCat is not just a payment SDK. It offers:

• A unified API for iOS and Android (and Stripe for web)
• Server-side verification and subscription status storage
• Webhooks for events (purchase, renewal, cancellation, billing issue)
• Analytics for cohorts, MRR, churn
• A/B testing of offers via Experiments

Purchases.configure(withAPIKey:) at startup, Purchases.shared.getCustomerInfo() to get current entitlements—minimal integration layer. Purchases.shared.purchase(package:) instead of directly calling StoreKit/Billing.

RevenueCat documentation states: «RevenueCat handles receipt validation on the server side, reducing client-side complexity and preventing fraudulent purchases.»

Limitations of RevenueCat: it is paid (free up to $2.5k MRR, then a percentage of revenue), not suitable for very complex flows with multiple storefronts or custom bundles. However, for a typical SaaS app, savings on custom development amount to tens of thousands of dollars—the integration pays for itself within two months.

Stripe in Mobile Apps

Stripe is used for physical goods, services, and B2B payments where IAP is not required by platform policy.

Stripe iOS SDK and Android SDK—PaymentSheet for ready-made payment UI, PaymentSheetFlowController for custom UI with saved cards. Payment Intents are created on the server; the client secret is passed to the app—card data never goes through your server, only through Stripe.

Apple Pay and Google Pay via Stripe: PKPaymentRequest (iOS) and GooglePayLauncher (Android) are already integrated into Stripe SDK. Apple Pay conversion rates are 1.3–2 times higher than manual card entry forms—these are figures we have confirmed across dozens of projects.

Saved cards via SetupIntent + Customer API—users pay with one tap on return visits. Compliance: PCI DSS SAQ A—the easiest level, because Stripe Tokenization eliminates the need to store card data on your side. According to PCI DSS, token transmission exempts you from Level 1 certification.

3DS2 (Strong Customer Authentication) is mandatory for payments in the EU under PSD2. Stripe handles it automatically via PaymentIntent.confirmPayment, but you need to correctly handle the .requiresAction status and return the user to the appropriate screen after authentication.

What Is Included in the Work (Deliverables)

Process and Timeline

We start by clarifying the business model: subscriptions, one-time purchases, consumables, freemium. The architecture depends on this. Testing IAP requires Sandbox accounts (Apple) and License Testers (Google)—this is a separate environment setup.

Apple's Sandbox behaves differently from production: subscriptions renew every 5 minutes instead of monthly, inGracePeriod works differently. It is essential to test scenarios: trial expiration, cancellation, billing retry, refund.

The cost is calculated individually based on the set of tools and complexity of server-side logic. On average, we fit within a budget for a typical integration, but the savings from preventing errors and churn offset this investment within a few months.

Get a consultation for your project—contact us. We will help you choose the optimal payment architecture that passes store reviews and does not break under peak loads.