Stream Chat SDK Integration: Real-Time Chat Without Lag

Real-time chat without lag is a common headache for mobile teams. Misconfigured WebSocket, unstable reconnection, token leaks—these are typical issues we see during audits. The Stream Chat SDK solves them, but requires proper setup. With 5 years of experience and 20+ chat projects, 8 of which used Stream Chat, we guarantee stability even on weak connections. Let's walk through integration from scratch, skipping the "Hello World" from the docs.

Stream Chat differs from SendBird architecturally: its API is built on an event-driven model (WebSocket + event-driven state), and the SDK provides ready-made SwiftUI/Compose components with deep customization via subclassing and view factories. The binary size is smaller: iOS ~8 MB, Android AAR ~6 MB. We've often seen that SendBird offers more freedom, but Stream Chat is faster to integrate—up to 40% time savings on the initial setup.

Why Stream Chat saves up to 40% development time?

Ready-made UI components cover 80% of the behavior. The remaining 20% is customization via ViewFactory. This is faster than writing your own chat from scratch with UIKit/Compose. Full custom UI only makes sense when design systems are incompatible.

Initialization and token management

Stream uses JWT. The client never generates a token itself—only your backend via Stream Chat SDK. On the backend, the token is created using stream_chat.create_token(user_id) (Python/Node SDK). On the client:

// iOS
let client = ChatClient(config: ChatClientConfig(apiKeyString: "YOUR_KEY"))
let token = try Token(rawValue: "eyJ...")
client.connectUser(userInfo: .init(id: userId), token: token) { error in ... }

// Android
val client = ChatClient.Builder("YOUR_KEY", context).build()
client.connectUser(User(id = userId), token).enqueue { result -> ... }

Token refresh: Stream SDK calls TokenProvider when the token expires. Implement TokenProvider (iOS: closure-based, Android: TokenProvider interface)—there, make a request to your API and return a new token. Without this, the user will be disconnected after the token TTL.

How to create channels and subscribe to events?

Stream uses a type:id combination to identify channels. Types are messaging, livestream, team, commerce, gaming—they affect default permissions.

// iOS: get or create a 1-on-1 channel
let channelId = ChannelId(type: .messaging, id: "user1_user2")
let controller = client.channelController(
    createChannelWithId: channelId,
    members: [userId, targetId],
    isCurrentUserMember: true
)
controller.synchronize { error in ... }

synchronize() is the key call. It fetches history, subscribes to real-time events, and syncs the local state. Without it, the channel is created but events don't arrive. On Android, it's analogous via client.channel(channelType, channelId).create(memberIds).

How to set up push notifications?

Stream uses its own notification provider on top of APNs/FCM. Registration:

// iOS—after receiving APNs token
chatClient.currentUserController().addDevice(.apns(token: deviceToken))

// Android
FirebaseMessaging.getInstance().token.addOnSuccessListener { token ->
    client.addDevice(Device(token = token, pushProvider = PushProvider.FIREBASE)).enqueue()
}

Stream automatically sends notifications for new messages in channels the user is a member of. In the dashboard, configure notification templates. Deeplink—via handling CKNNotificationInfo (iOS) or RemoteMessage.data (Android).

UI customization: preserve functionality

Stream provides ChatChannelView, MessageListView, MessageComposerView from the StreamChatSwiftUI package. Customization is done via ViewFactory:

class CustomViewFactory: DefaultViewFactory {
    func makeMessageAvatarView(for userInfo: UserAvatarData) -> some View {
        // Your custom avatar
        CustomAvatarView(imageUrl: userInfo.imageURL)
    }
}
Utils.shared.viewFactory = CustomViewFactory()

This is cleaner than a fully custom UI—80% of the behavior (swipes, reactions, threads) comes for free, you only customize the appearance. Full custom UI only makes sense if the design is incompatible with Stream's component model. For Android, it's similar: MessageListView and MessageComposerView in XML or Compose, customization via AttachmentFactoryManager and MessageListViewModelFactory.

Offline cache and reconnection

iOS SDK uses CoreData under the hood, Android uses Room. It's enabled automatically when isLocalStorageEnabled = true in the configuration (true by default). When the network is restored, the SDK automatically syncs missed events via the WebSocket health check mechanism.

What's included in the implementation?

We document every step and leave you with working code. Below are the stages and timelines.

Timelines and next steps

With ready-made StreamChatSwiftUI/StreamChatUI components—3–4 days. Fully custom UI on Core SDK—6–8 days. Pricing is individual. Contact us for an audit of your current implementation or order a turnkey integration—we guarantee stability and post-delivery support.

How to Implement Social Features in Mobile Apps?

We design in-app chat not as “just WebSocket + messages” but as a system with offline access, history display under poor connection, typing indicators, read receipts, and push notifications when the app is closed. Our experience shows that all this must work on Android 8 with 512 MB RAM without ANR — otherwise users simply leave. With over 50 integrated social modules — from startup MVPs to enterprise platforms — we know where the architecture typically breaks. Contact us to achieve similar results for your product.

How do we approach chat development?

Choosing the protocol and storage is the first point where mistakes are made. WebSocket, XMPP, or a ready-made SDK — each option dictates time budget and reliability.

• Ready-made chat SDK (SendBird, Stream Chat, Cometchat) provides UI components, server infrastructure, push notifications, and moderation. Fast, reliable, but vendor lock-in and recurring costs. For MVP — optimal. One client cut time-to-market by 2 months using Stream Chat.
• Firebase Realtime Database / Firestore — for simple chats without scalability requirements >100K concurrent users. Realtime Database is more convenient for ordered message lists, Firestore for structured data. Limitation: typing indicators and presence are implemented separately via onDisconnect().
• Custom backend with WebSocket — full control, maximum customization. Stack: Node.js + socket.io or Phoenix Channels (Elixir), PostgreSQL + Redis for pub/sub. On mobile: Starscream (iOS Swift), OkHttp WebSocket (Android), socket_io_client (Flutter). Requires 2–3x development time but gives zero vendor risk. In one project, we chose custom WebSocket and reduced licensing costs by 40% compared to SendBird. Custom WebSocket implementation delivers 3x lower latency than Firebase on high-concurrency workloads.

Why is it important to plan offline mode in advance?

Offline mode is the most labor-intensive part of any chat. Messages are stored in SQLite (iOS: GRDB, Android: Room) with a local ID, synchronized upon connection restoration. Conflicts during simultaneous sending are resolved via vector clocks or server-timestamp ordering. If you don’t build this into the architecture from the first sprint, you’ll have to rewrite half the code 2–3 weeks before release. On one project handling 10 million messages daily with 500,000 DAU, we reduced sync time by 60% and made average delivery delay under 150 ms. Cursor-based pagination reduces data duplication by 10x compared to offset pagination on feeds with over 10,000 items — when new items are inserted, the cursor doesn’t shift, and the user doesn’t see duplicate content.

VoIP: CallKit, ConnectionService, and WebRTC

VoIP in a mobile app splits into two scenarios: system UI (looks like a phone call) or in-app call. CallKit (iOS) integrates via CXProvider + CXCallController and allows showing incoming calls on the Lock Screen, working with Bluetooth, and interrupting other audio. The app launches via VoIP push (PKPushKit) even when killed — essential for receiving calls.

On Android, the analog is ConnectionService API. Integration is more complex, behavior varies between manufacturers (Xiaomi, Samsung with their battery optimization aggressively kill background processes). WebRTC — transport protocol for P2P media. Signaling server (SDP, ICE candidates) — usually over the same WebSocket channel. STUN/TURN are mandatory: without TURN ~15–20% of users behind symmetric NAT won’t see the call. coturn — open source solution, Twilio NTS and Metered TURN — managed.

What Are the Best Practices for Feed and Reactions?

Infinite feed — UICollectionView with UICollectionViewDiffableDataSource on iOS, LazyColumn with Paging 3 on Android. Pagination via cursor-based approach — it doesn’t shift when new items are inserted, unlike offset. Reactions (emojis on messages): each reaction is a record (message_id, user_id, emoji), aggregated on the server GROUP BY emoji. WebSocket event reaction_added updates the counter in real-time. Grouping with GROUP BY emoji is 5x faster than per-message count updates. Appearance animation — via withSpring (Reanimated) or Core Animation spring. In a social network project, we handled up to 80,000 concurrent connections on a single instance — the feed remained responsive.

Push notifications for social events: @mention, reply, new follower — via APNs and FCM. For rich notifications (media preview) on iOS — Notification Service Extension, which loads media before display. After implementing such notifications, user retention increased by 30%.

What deliverables do you receive?

We deliver not just code — here is the full list:

1. Data schema design (SQLite, Firestore, PostgreSQL) considering offline-first and scaling up to 1 million users.
2. Client-server protocol implementation (WebSocket, REST, GraphQL) with reconnection and heartbeat support.
3. Push notification integration (APNs, FCM) with certificate generation and key configuration.
4. TURN server setup or managed provider selection (e.g., Twilio NTS) for VoIP.
5. API documentation and migration schema (including rollback plan).
6. Access to repository, CI/CD (GitHub Actions + Fastlane), TestFlight / Google Play Console.
7. Team training (including code review for the first 2 sprints) and knowledge transfer.
8. On-call support for 2 weeks after release.

How to avoid typical mistakes in chat development?

• Lack of reconnection strategy. Client simply disconnects without a queue of unsent messages. Solution: heartbeat, exponential backoff, local storage of outgoing messages with pending flag.
• Using offset pagination in feed. When new posts are inserted, the user sees duplicates — scrolling breaks. Solution: cursor-based pagination.
• Ignoring battery optimization on Android. ConnectionService doesn’t survive until incoming call. Solution: foreground service with persistent notification or integration via Firebase Cloud Messaging for wake-up.
• Error in choosing chat protocol. Bare WebSocket without a protocol on top — reinventing the wheel. Platform-agnostic JSON or MessagePack with type flag.

The technology stack we typically apply on a mobile chat project includes: iOS (Swift 5.9+, SwiftUI, Combine, async/await, Starscream, GRDB), Android (Kotlin, Jetpack Compose, OkHttp WebSocket, Room, Hilt DI), cross-platform (Flutter 3.x/React Native), backend (Node.js + socket.io or Phoenix Channels + PostgreSQL + Redis), push (APNs/FCM), and VoIP (WebRTC + coturn).

⏱ Estimated timelines

Cost is calculated individually after analyzing your technical specification and existing architecture. Contact us for a project estimate — we will offer two options: fast implementation via ready-made SDKs or a fully customized solution. Get a consultation and accurate estimate within 2 business days. Order chat development today — we guarantee correct operation on Android 8+ and iOS 14+. Reach out to discuss your project's specific needs — we'll propose the optimal architecture.