Integrating VK Live into a mobile app seems straightforward until you hit the lack of an official SDK. It all boils down to the RTMP protocol, session keys, and real-time encoding. We've solved this for iOS and Android, and here's what we found.
What technical challenges arise with VK Live integration?
How to obtain an RTMP key without user interaction? — integrating broadcast streaming
The most common issue is getting the RTMP key via the VK API without manual input. The video.startStreaming method requires authorization via VK Connect with the video scope. If the token is expired or lacks the required scope, it returns error_code: 15 (access denied), and the broadcast won't start. We store the token in Keychain (iOS) or EncryptedSharedPreferences (Android) and refresh it before expiration rather than after an error. This increases first-time broadcast success to 95% and saves up to 30 seconds per session. Contact us for a consultation on setting up the OAuth2 flow — it will save days of development.
Why does H.264 encoding require precise tuning?
Encoding on mobile is the bottleneck. On iOS, we use VideoToolbox through AVAssetWriter + AVAssetWriterInput with parameters:
let videoCompressionProperties: [String: Any] = [ AVVideoAverageBitRateKey: 2_500_000, AVVideoMaxKeyFrameIntervalKey: 60 ] let videoSettings: [String: Any] = [ AVVideoCodecKey: AVVideoCodecType.h264, AVVideoWidthKey: 1280, AVVideoHeightKey: 720, AVVideoCompressionPropertiesKey: videoCompressionProperties ] Without explicit AVVideoMaxKeyFrameIntervalKey, the encoder places keyframes too sparsely — the VK RTMP server buffers longer, causing viewers to notice jerks on scene changes. On Android, we use MediaCodec with MediaFormat.MIMETYPE_VIDEO_AVC and BITRATE_MODE_CBR. VBR on unstable connections causes bitrate spikes that packet loss on the VK ingest turns into artifacts lasting 2-3 seconds. So we fix CBR and limit GOP to 60 frames.
How we implement RTMP streaming
Comparison of approaches: HaishinKit vs custom RTMP
| Parameter | HaishinKit (iOS) | Custom RTMP (Android) |
|---|---|---|
| Development time | 1–2 days | 3–5 days |
| Flexibility | Medium | High — full control over buffers |
| Dependencies | External library | Only standard APIs |
| Support | Active, updates | In-house |
| Performance | Good, 60 fps | Excellent with custom thread pool |
HaishinKit cuts implementation time by 2-3 times compared to a custom solution, but offers less flexibility for fine-tuning buffering.
On iOS, we use HaishinKit (Swift, actively maintained). On Android, we prefer native MediaCodec with a custom RTMP client over java.net.Socket, avoiding heavy dependencies. iOS scheme with HaishinKit:
let rtmpConnection = RTMPConnection() let rtmpStream = RTMPStream(connection: rtmpConnection) rtmpStream.videoSettings = VideoCodecSettings( videoSize: CGSize(width: 1280, height: 720), bitRate: 2_500_000, profileLevel: kVTProfileLevel_H264_High_AutoLevel as String ) rtmpStream.audioSettings = AudioCodecSettings(bitRate: 128_000) rtmpConnection.connect("rtmp://vp.vkforms.ru/live") rtmpStream.publish(streamKey) Quality monitoring — we subscribe to RTMPConnection.Event.rtmpStatus, tracking NetStream.Publish.BadName (invalid key) and NetStream.Failed (connection drop). On NetStream.Failed, we log to Firebase Crashlytics with parameters: bitrate at disconnection, connection type (Wi-Fi/Cellular), OS version.
Reconnection is implemented with exponential backoff: 2s → 4s → 8s → 16s → 30s (maximum). Infinite retries without a pause will block the account on the VK side due to flood.
Comparison of encoding settings for iOS and Android
| Parameter | iOS (VideoToolbox) | Android (MediaCodec) |
|---|---|---|
| Codec | H.264/H.265 | H.264/H.265 |
| Bitrate | 2.5–4 Mbps | 2.5–4 Mbps |
| GOP | 60 frames | 60 frames |
| Bitrate mode | CBR | CBR |
| Profile | High | High |
Authorization and obtaining the stream key
Via VK SDK (iOS: VKSDK, Android: vk-android-sdk) or direct OAuth2 flow:
- Open a WebView or SFSafariViewController at
https://oauth.vk.com/authorize?client_id=APP_ID&scope=video&response_type=token - Intercept the redirect to
https://oauth.vk.com/blank.html#access_token=... - Call
video.startStreamingwith the obtained token - Extract
rtmp_urlandkeyfrom the response
The key is session-bound — it works for one broadcast only. Saving it between sessions is not allowed.
Integration verification checklist
- [ ] Authorization token obtained with video scope
- [ ] RTMP key is valid for the current broadcast
- [ ] Encoding parameters set (CBR, GOP 60)
- [ ] Error handling with exponential backoff
- [ ] Logging to Crashlytics
- [ ] Compliance with App Store Review Guidelines and Google Play Developer Policy
What's included in the work
- Full RTMP streaming integration on iOS or Android (your choice)
- OAuth2 authorization via VK with token management
- H.264/H.265 encoding configuration: bitrate, GOP, profile
- Network error handling and auto-reconnection
- Monitoring via Firebase Crashlytics with custom logs
- Documentation for usage and support
- Help with App Store / Google Play publication (policy compliance check)
Timelines and cost
Integration on one platform (iOS or Android): 2–3 weeks including OAuth flow, video capture, and basic error handling. Adding adaptive bitrate and auto-reconnection takes another week. Cost is calculated individually after requirement analysis. Contact us to evaluate your project and choose the optimal stack. Request a consultation — we'll help with the details.
We provide a guarantee on stream stability when recommended settings are followed. Experience with over 15 projects — we are confident in the quality.