Integrate Chromecast Streaming in Your Mobile App

When a user taps the Cast button, content should instantly appear on the big screen. But implementing that button is far from trivial: integrating the Google Cast SDK, managing session state, handling connection loss, and controlling pause and seek. Devices must be on the same network, and the app must pass App Store Review Guidelines (Section 4.2). We handle this for you. Our team has 5+ years in mobile development and 15+ projects with Chromecast streaming. We use proven patterns and guarantee stable performance on Android and iOS. Our ready components reduce time-to-market by 30%, and using the Default Media Receiver can cut initial budget costs by up to 40%.

How to Implement Chromecast Streaming in 2–3 Days?

The fastest path is using the Default Media Receiver: the phone (Sender) sends a content URL, and the Receiver streams it directly—no custom web app needed. Playback control goes through the Google Cast SDK. Basic integration takes 2–3 days. For custom requirements (UI, DRM, analytics), we develop a custom Receiver, adding another 2–3 days. Development costs are up to 50% lower compared to doing it yourself.

Integrating the Google Cast SDK

Android. Add com.google.android.gms:play-services-cast-framework:latest to your build.gradle—the standard package for Chromecast on Android. Initialize in Application:

class App : Application() {
    override fun onCreate() {
        super.onCreate()
        val options = CastOptions.Builder()
            .setReceiverApplicationId(CastMediaControlIntent.DEFAULT_MEDIA_RECEIVER_APPLICATION_ID)
            .build()
        CastContext.getSharedInstance(this, executor).addOnSuccessListener { castContext ->
            // Cast context ready
        }
    }
}

DEFAULT_MEDIA_RECEIVER_APPLICATION_ID is the standard Default Media Receiver, which plays HLS, DASH, MP4, MP3. For a custom Receiver, register your app in the Google Cast Developer Console and use your own App ID. For more on CastContext setup, see the Google Cast documentation.

iOS. Add pod 'google-cast-sdk' or GoogleCast via SPM—the main SDK for Chromecast on iOS. The API is similar to Android.

Cast Button in the UI

The Google Cast SDK provides ready-made buttons: UICastButton (iOS) and MediaRouteButton (Android). They show device lists and change appearance when connected:

// In toolbar menu
override fun onCreateOptionsMenu(menu: Menu): Boolean {
    menuInflater.inflate(R.menu.menu_player, menu)
    CastButtonFactory.setUpMediaRouteButton(this, menu, R.id.media_route_menu_item)
    return true
}

For Jetpack Compose, use AndroidView with MediaRouteButton.

Starting Playback on the Receiver

val castSession = CastContext.getSharedInstance(context).sessionManager.currentCastSession
val remoteClient = castSession?.remoteMediaClient ?: return

val mediaMetadata = MediaMetadata(MediaMetadata.MEDIA_TYPE_MOVIE).apply {
    putString(MediaMetadata.KEY_TITLE, "Movie Title")
    putString(MediaMetadata.KEY_SUBTITLE, "Description")
    addImage(WebImage(Uri.parse(thumbnailUrl)))
}

val mediaInfo = MediaInfo.Builder(streamUrl)
    .setStreamType(MediaInfo.STREAM_TYPE_BUFFERED)
    .setContentType("application/x-mpegURL") // HLS, or video/mp4 for MP4
    .setMetadata(mediaMetadata)
    .build()

val loadOptions = MediaLoadRequestData.Builder()
    .setMediaInfo(mediaInfo)
    .setAutoplay(true)
    .setCurrentTime(startPositionMs.toLong())
    .build()

remoteClient.load(loadOptions)

Playback Control

RemoteMediaClient is the central object for Chromecast playback: play(), pause(), seek(position), setStreamVolume(volume). Track state via a callback:

remoteClient.registerCallback(object : RemoteMediaClient.Callback() {
    override fun onStatusUpdated() {
        val status = remoteClient.mediaStatus ?: return
        val position = status.streamPosition
        val isPlaying = status.playerState == MediaStatus.PLAYER_STATE_PLAYING
        updateUI(isPlaying, position)
    }
})

Mini Controller and Expanded Controller

Built-in components: MiniControllerFragment—a bottom control bar, and ExpandedControllerActivity—a full-screen player. They work declaratively with minimal code and automatically reflect the Chromecast connection state.

Why Use a Custom Receiver?

The Default Receiver covers 80% of use cases. But if you need a unique interface, Subrip subtitles, analytics, or DRM (Widevine), a custom Receiver is essential. We build a web application in HTML5/JavaScript. A custom Receiver increases development time by 70% but gives full control—4 times more customization options than the Default.

Key Integration Steps

Cast Session and Reconnection

When Wi-Fi is lost, CastSession enters TEMPORARILY_DISCONNECTED, then DISCONNECTED after 3 minutes. SessionManagerListener.onSessionSuspended / onSessionResumed handle reconnection; we resume playback from the saved position. On app return, the Cast SDK automatically restores the session via CastContext.sessionManager.currentCastSession.

Chromecast on React Native and Flutter

React Native: react-native-google-cast—an unofficial wrapper. It is stable for basic scenarios; advanced features require native code. Flutter: no official package; flutter_google_cast is unstable. For production, we recommend native implementation via MethodChannel. Native solutions are 2 times more reliable than cross-platform wrappers. TV casting from a WebView is also possible, but control is limited.

What Is Included

• Google Cast SDK integration on Android (Kotlin) and iOS (Swift)
• Cast button and custom UI (MiniController, ExpandedController)
• Playback control (play/pause/seek/volume)
• Session handling, reconnection, position saving
• Testing on real devices (Chromecast, Android TV, Google Nest)
• Documentation and source code access
• Post-deployment support (1 month)

Timelines and Cost

Timelines range from 2 to 6 days. Cost is determined individually after an audit of your project. Contact us for a consultation and preliminary estimate. Order your Chromecast streaming solution—we guarantee stable performance on all devices. Get a consultation and ensure your TV casting works flawlessly.

How to Choose a Camera Approach on Mobile Platforms?

Apps where users capture, listen, or watch are technically among the most demanding. We deal with this every day. Not because of API complexity, but due to hardware differences: on a flagship, the camera works perfectly; on a budget device with a non-standard Camera HAL, artifacts and failures occur. On iOS, stabilization differs between generations. Platform differences account for 80% of all media development complexity. Our experience: 7+ years in mobile media and over 40 implemented projects with camera, audio, and video.

What are the Differences Between CameraX, Camera2, and AVFoundation?

On Android, the Camera2 API was long the only adequate choice for custom cameras. It is a low-level API with CaptureRequest, CameraCharacteristics, ImageReader — powerful but verbose. Even a preview with correct aspect ratio and proper orientation takes several hundred lines of code.

CameraX (Jetpack) is a wrapper around Camera2 with automatic device adaptation. Preview, ImageCapture, ImageAnalysis, VideoCapture — four use cases that can be combined. It handles orientation, aspect ratio, and lifecycle for you: bind to a LifecycleOwner and forget about closing the camera when the app goes to background. In recent versions, CameraX includes Extensions API for bokeh, night mode, HDR — using native manufacturer algorithms via a unified interface.

When is Camera2 needed directly?: RAW capture via ImageFormat.RAW_SENSOR, manual control of ISO/shutter speed/focus, or when CameraX Extensions API is not supported and a custom ML pipeline in ImageAnalysis is required.

On iOS, AVFoundation is the only path for a custom camera. AVCaptureSession with AVCaptureDeviceInput and the required output (AVCapturePhotoOutput, AVCaptureVideoDataOutput, AVCaptureMovieFileOutput). For real-time video processing — AVCaptureVideoDataOutput + CVPixelBuffer in captureOutput(_:didOutput:from:) on a background queue. This is where CoreML models receive frames for inference.

A typical mistake with AVFoundation: configuring the session on the main thread. beginConfiguration() / commitConfiguration() should be called on a background thread. Otherwise, the preview freezes, and the user sees a frozen UI. This mistake appears in 70% of the projects we have audited.

Why is AudioFocus Critical for Android Apps?

Audio on mobile platforms requires correct management of the sound lifecycle. AudioFocus is a coordination mechanism between apps. AudioManager.requestAudioFocus() with OnAudioFocusChangeListener. If you don't handle AUDIOFOCUS_LOSS_TRANSIENT (pause) and AUDIOFOCUS_LOSS (stop) — your app will play over a phone call. That guarantees a bad review on Google Play. Android Developer Guide: AudioFocus

On iOS, AudioSession categories define behavior: playback — for players (continues playing when screen is locked), record — for recording, muting other sources, playAndRecord — for voice messages. Wrong category — the app mutes the user's background music on start.

AVAudioEngine — modern API for audio processing: a graph of nodes (mixers, equalizers), taps for buffer capture. For real-time speech — SFSpeechRecognizer + inputNode.installTap.

On Android for recording with noise suppression — NoiseSuppressor.isAvailable() + create(audioRecord.audioSessionId). Works not on all devices, need a fallback.

Video: Playback and Streaming

ExoPlayer (Media3) — standard for Android. Supports HLS, DASH, SmoothStreaming, progressive playback. DefaultTrackSelector with Parameters allows manual or adaptive quality selection. DRM via DefaultDrmSessionManager with Widevine L1/L3.

Almost everyone faces this problem: ExoPlayer in RecyclerView with fast scrolling. Need a PlayerPool — a pool of reusable players. Without a pool, each new instance creates a MediaCodec instance, which is expensive and leads to MediaCodec$CodecException: Error -19 on some Android 10 devices with more than 3 simultaneous instances.

AVPlayer / AVPlayerViewController on iOS — for playback. For custom UI — AVPlayerLayer + custom controls. HLS works natively via AVPlayer(url:) with m3u8. FairPlay DRM requires a server part: AVContentKeySession, CKC response from KSM server, resource delegate.

For Flutter — video_player as a base layer, chewie for UI. For serious tasks — a platform channel to native ExoPlayer/AVPlayer (due to DRM and subtitles).

WebRTC on mobile — via native frameworks or flutter_webrtc. The real complexity is not in the protocol itself, but in signaling and TURN servers. Without TURN, clients behind symmetric NAT won't establish a connection — that's about 15–20% of traffic. Coturn is the standard open-source server.

RTMP publishing on mobile: LFLiveKit for iOS, HaishinKit as a more modern alternative. On Android — rtmp-rtsp-stream-client-java or via FFmpeg with JNI. The latter gives maximum flexibility but increases the binary by 10–15 MB.

Media Processing: Compression and Transcoding

ProRes video can take up to 6 GB/minute. Compression is needed before upload. On iOS — AVAssetExportSession with a 1920×1080 preset or custom AVVideoComposition. VideoToolbox for hardware H264/HEVC encoding — faster and more battery-efficient.

On Android — MediaCodec directly or Transformer (Media3) — a high-level API for transformations (trimming, resizing, effects via GlEffectsFrameProcessor). For images — BitmapFactory.Options.inSampleSize for downsampling, Glide / Coil for caching. Coil on Coroutines fits well with Compose. Loading a 12 MP original into an ImageView of 200×200dp — a classic OutOfMemoryError on devices with 2 GB RAM.

How to Implement Streaming on Mobile Devices: Step-by-Step Plan

1. Define requirements: target latency, number of concurrent users, need for P2P.
2. Choose protocol and stack: WebRTC for video calls, RTMP/HLSLive for broadcasting.
3. Set up signaling (SIP, WebSocket, MQTT) and TURN server.
4. Implement publishing/viewing via native API or cross-platform plugin.
5. Test on real devices with different cameras and network conditions.
6. Optimize bitrate and resolution based on bandwidth.

What is Included in the Work

Development Process for Media Functionality

Complexity is non-linear: basic video playback — 1–2 days, custom camera with frame processing and streaming — 3–5 weeks. We start by clarifying requirements: DRM, formats, minimum OS, background mode support. Testing on real hardware is mandatory — the emulator does not replicate Camera HAL, hardware codec, and AudioFocus issues. Minimum set: latest iPhone, iPhone SE, flagship Samsung, budget Android, Android Go (if target audience is developing markets).

Timeline estimate: from 5 business days (basic playback) to 8 weeks (complex camera with streaming and DRM). Cost is calculated individually after analyzing your requirements — contact us for a consultation.

Our service: "Mobile Media Integration" — this is our expertise. Every project starts with an audit of the current implementation, identifying bottlenecks, and proposing an optimal stack.

Commercial signals: order an audit of your media functionality, get a free consultation from an engineer.