# ExoPlayer

ExoPlayer is Media3's default Player implementation for playing local or streamed audio and video, with support for streaming protocols, renderers, buffering, customization, and extension.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Reel: Your Own Streaming Service or Course Platform

DevFeed: [Reel: Your Own Streaming Service or Course Platform](<https://devfeed.tech/articles/reel-your-own-streaming-service-or-course-platform-113296.md>)

Original publisher: [Read original article](<https://www.codenameone.com/blog/reel-streaming-and-courses-template/>)

Author: Shai Almog

Published: 2026-11-03T00:00:00Z

Content type: article

Language: en

Sources: [CodeName One](<https://devfeed.tech/sources/codename-one.md>)

Topics: [Streaming](<https://devfeed.tech/topics/streaming.md>), [ExoPlayer](<https://devfeed.tech/topics/exoplayer.md>)

Tags: [academy](<https://devfeed.tech/tags/academy.md>), [account](<https://devfeed.tech/tags/account.md>), [admin](<https://devfeed.tech/tags/admin.md>), [ads](<https://devfeed.tech/tags/ads.md>), [aes](<https://devfeed.tech/tags/aes.md>), [android](<https://devfeed.tech/tags/android.md>), [api](<https://devfeed.tech/tags/api.md>), [app](<https://devfeed.tech/tags/app.md>), [apple](<https://devfeed.tech/tags/apple.md>), [audio](<https://devfeed.tech/tags/audio.md>), [behavior](<https://devfeed.tech/tags/behavior.md>), [blocks](<https://devfeed.tech/tags/blocks.md>), [browser](<https://devfeed.tech/tags/browser.md>), [course](<https://devfeed.tech/tags/course.md>), [drm](<https://devfeed.tech/tags/drm.md>), [java](<https://devfeed.tech/tags/java.md>), [project](<https://devfeed.tech/tags/project.md>), [server](<https://devfeed.tech/tags/server.md>), [streaming](<https://devfeed.tech/tags/streaming.md>), [subscription](<https://devfeed.tech/tags/subscription.md>)

### AI overview

Reel is a Java app-and-server template for subscription streaming, creator platforms, or course academies. Runtime presets and feature toggles configure plans, uploads, courses, quizzes, and other functions; creators' videos are packaged and checked against moderator blocklists, and moderation approval is required before publication. A new Codename One streaming API selects among device-supported DRM schemes. Reel packages AES-128 HLS and ClearKey versions under one key, with session-linked license tokens and video-scoped, expiring media tokens; AES-128 and ClearKey deter casual copying but are not studio-grade protection. External Widevine or FairPlay license vendors can provide stronger protection without changing app code. Reel renders WebVTT subtitles itself for consistent display across devices and DRM schemes, but drops positioning and inline tags. Payments are simulated in development; Stripe and Apple and Google store purchases are supported.

### Source excerpt

Reel is a streaming service and its server in one Java project: a subscription service, a creator platform or a course academy, with a new DRM streaming API.

## Monetisation : Multi-period DASH x ExoPlayer

DevFeed: [Monetisation : Multi-period DASH x ExoPlayer](<https://devfeed.tech/articles/monetisation-multi-period-dash-x-exoplayer-77969.md>)

Original publisher: [Read original article](<https://blog.hotstar.com/monetisation-multi-period-dash-x-exoplayer-db8e8c00e521?source=rss----dbc3fcbc7f07---4>)

Author: Abhishek Bansal

Published: 2026-03-04T04:18:06Z

Content type: article

Language: en

Sources: [JioHotstar](<https://devfeed.tech/sources/jiohotstar.md>)

Topics: [ExoPlayer](<https://devfeed.tech/topics/exoplayer.md>), [Software Testing](<https://devfeed.tech/topics/software-testing.md>)

Tags: [ads](<https://devfeed.tech/tags/ads.md>), [alternatives](<https://devfeed.tech/tags/alternatives.md>), [android](<https://devfeed.tech/tags/android.md>), [approach](<https://devfeed.tech/tags/approach.md>), [asset](<https://devfeed.tech/tags/asset.md>), [audio](<https://devfeed.tech/tags/audio.md>), [box](<https://devfeed.tech/tags/box.md>), [card](<https://devfeed.tech/tags/card.md>), [client](<https://devfeed.tech/tags/client.md>), [complexity](<https://devfeed.tech/tags/complexity.md>), [component](<https://devfeed.tech/tags/component.md>), [consider](<https://devfeed.tech/tags/consider.md>), [content](<https://devfeed.tech/tags/content.md>), [cost](<https://devfeed.tech/tags/cost.md>), [dash](<https://devfeed.tech/tags/dash.md>), [details](<https://devfeed.tech/tags/details.md>), [driving](<https://devfeed.tech/tags/driving.md>), [dub](<https://devfeed.tech/tags/dub.md>), [exoplayer](<https://devfeed.tech/tags/exoplayer.md>), [period](<https://devfeed.tech/tags/period.md>), [streaming](<https://devfeed.tech/tags/streaming.md>)

### AI overview

ExoPlayer's AdsMediaSource rejected multi-period DASH streams, and simply removing its single-period assertion was insufficient: shared ad state could repeat prerolls across periods and misalign cue points. The team built a MultiPeriodAdTimeline that keeps one logical ad state, transforms cue-point times relative to each period, marks out-of-period groups skipped while preserving their indices, and uses bookmarking to prevent watched ads from replaying after cross-period seeks. This supports ads across period boundaries while allowing localized disclaimers and dub cards without re-encoding the main video. Older app versions continued receiving single-period DASH; multi-period delivery was gated to newer versions and rolled out with playback and ad metrics monitored. Separate players, playlist stitching, and concatenated clipped media sources were rejected because they add buffering, lose AdsMediaSource capabilities, and spread complexity.

### Source excerpt

Client Side Ad Insertion(CSAI) levels up using multi-period DASH in the Android ecosystem. This is our journey to upgrade ExoPlayer to leverage multi-period DASH.Introduction Multi-period DASH is a variant of DASH format that offers significant advantages, such as the ability to insert dynamic content like disclaimers, dub cards, and ad breaks without re-encoding the entire video. This flexibility is crucial for delivering personalized and localized content to millions of users across diverse regions. While the DASH standard natively supports multi-period manifests, the Android ExoPlayer ecosystem (specifically the AdsMediaSource component) was designed with a single-period assumption. This missing piece in the puzzle meant we couldn't support Client-Side Ad Insertion (CSAI) on these modern streams out of the box. This post details our engineering journey: identifying the constraints, evaluating architectural alternatives, and ultimately redesigning ExoPlayer's Ad handling to support multi-period content seamlessly. ContextThe Evolution of DASH Content JioHotstar relied on single-period DASH for entertainment content, where the entire stream including ads was encapsulated within a single period. This approach limited flexibility: inserting disclaimers, dub cards, and to some extent, dynamic ad breaks required re-encoding the entire video, which was both time-consuming and resource-intensive. Consider a common localization scenario: the same title is launched across multiple regions with different primary languages. Audio dubs may be recorded by different artists per market, so dub-card credits vary by region; likewise, legal and regulatory requirements differ, driving region-specific disclaimers. Under a single-period workflow, each of these variations would necessitate a distinct transcode of the full asset. If we target ~20 regions, that implies ~20 full transcodes, leading to long time-to-market, high cost, and significant operational complexity -- super unscalabl

## Controlling memory with Google's ExoPlayer

DevFeed: [Controlling memory with Google's ExoPlayer](<https://devfeed.tech/articles/controlling-memory-with-google-s-exoplayer-25145.md>)

Original publisher: [Read original article](<https://ianbird.dev/exoplayer-loadcontrol/>)

Author: Ian Bird

Published: 2021-12-06T14:24:05Z

Content type: tutorial

Language: en

Sources: [Ian Bird](<https://devfeed.tech/sources/ian-bird.md>)

Topics: [ExoPlayer](<https://devfeed.tech/topics/exoplayer.md>), [Playback](<https://devfeed.tech/topics/playback.md>), [Android](<https://devfeed.tech/topics/android.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [exoplayer](<https://devfeed.tech/tags/exoplayer.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [memory](<https://devfeed.tech/tags/memory.md>), [playback](<https://devfeed.tech/tags/playback.md>)

### AI overview

This tutorial explains how ExoPlayer manages its main playback buffer and how application developers can influence its memory usage. It covers decoder input and output buffers, media-file track interleaving, and the LoadControl and Allocator components.

### Source excerpt

Playback requires memory. Learn how to best control ExoPlayer to make efficient use for your application.

## Video playback in LazyColumn in Jetpack Compose

DevFeed: [Video playback in LazyColumn in Jetpack Compose](<https://devfeed.tech/articles/video-playback-in-lazycolumn-in-jetpack-compose-25900.md>)

Original publisher: [Read original article](<https://proandroiddev.com/video-playback-in-lazycolumn-in-jetpack-compose-df355097f26e?source=rss-56174fa84bcc------2>)

Author: Denys Rudenko

Published: 2021-10-05T23:51:23Z

Content type: tutorial

Language: en

Sources: [Denis Rudenko](<https://devfeed.tech/sources/stories-by-denis-rudenko-on-medium.md>)

Topics: [ExoPlayer](<https://devfeed.tech/topics/exoplayer.md>), [Jetpack Compose](<https://devfeed.tech/topics/jetpack-compose.md>), [media3](<https://devfeed.tech/topics/media3.md>), [Image](<https://devfeed.tech/topics/image.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-app-development](<https://devfeed.tech/tags/android-app-development.md>), [androiddev](<https://devfeed.tech/tags/androiddev.md>), [coil](<https://devfeed.tech/tags/coil.md>), [compose](<https://devfeed.tech/tags/compose.md>), [exoplayer](<https://devfeed.tech/tags/exoplayer.md>), [jetpack-compose](<https://devfeed.tech/tags/jetpack-compose.md>), [lifecycle](<https://devfeed.tech/tags/lifecycle.md>), [playback](<https://devfeed.tech/tags/playback.md>), [restore](<https://devfeed.tech/tags/restore.md>), [save](<https://devfeed.tech/tags/save.md>), [video](<https://devfeed.tech/tags/video.md>)

### AI overview

The excerpt describes a Jetpack Compose video list using ExoPlayer for playback and Coil for thumbnails. A VideosScreen tracks the playing item; stable LazyColumn keys help preserve item state, and each video's last playback position is saved so it can be restored. Tapping the play/pause control starts or pauses the selected video, while LaunchedEffect runs playback changes when the selected index changes. DisposableEffect observes app lifecycle events to pause playback in the background and release the player and observer when the screen leaves composition. A snapshotFlow over LazyListState detects whether the playing card is visible and pauses it when it scrolls off-screen. The auto-playback variant selects the first or last item at list boundaries and otherwise plays the item closest to the center. The supplied text does not include the complete code samples.

### Source excerpt

Article will cover both manual & auto-playback of videos in an efficient way, storing/restoring last played video position, pausing playback if video card is not visible to the user and handling application lifecycle. ExoPlayer will be used for video playback, and these videos as a test data set. Coil will be used for displaying the video thumbnails. Video shows manual play/pause & auto-playback versions side to side. https://medium.com/media/98ab3ea482f78b96bf44de2ce54c7168/hrefStep 1: VideosScreen Let's start implementing all of those features step by step. First we create a composable which will contain the exoPlayer instance, list of videos and playingItemIndex: https://medium.com/media/2440139ad1f185b8d1f1446f844530b9/href Very important part here is using keys for the lazyColumn. In short: we provide a key which enables item state to be consistent across data-set changes isPlaying -- we can always know if video is playing or not. If it's playing -- playingItemIndex will represent the position of the item in the list, if nothing is playing -- null. We need this field to know if we should show play/pause icon, and thumbnail image or playerView. VideoCard -- composable which exposes click event on play/pause icon. Click will be handled inside the viewModel. Notice that we're passing current playback position from exoPlayer as well as the index of clicked item. We'll use it to save & restore the playback position for each video. https://medium.com/media/518600644bbec8f225a0c4b933adccd1/href Whenever the play/pause icon is clicked, we're checking for three scenarios: currentlyPlayingIndex is null -- video is not playing at the moment, so we are assigning the videoIndex to currentlyPlayingIndex. currentlyPlayingIndex is the same as videoIndex clicked -- this means that the same video is already playing, and we want to pause the playback. That's why we assign null to currentlyPlayingIndex. To store the last played video position we're mutating list, and saving the position

## Drop-in Android Video -- Exoplayer2 with Picture in Picture

DevFeed: [Drop-in Android Video -- Exoplayer2 with Picture in Picture](<https://devfeed.tech/articles/drop-in-android-video-exoplayer2-with-picture-in-picture-26010.md>)

Original publisher: [Read original article](<https://medium.com/s23nyc-tech/drop-in-android-video-exoplayer2-with-picture-in-picture-e2d4f8c1eb30?source=rss-2ffcf6104135------2>)

Author: Stacy Devino

Published: 2018-09-13T15:58:58Z

Content type: tutorial

Language: en

Sources: [Stacy Devino](<https://devfeed.tech/sources/stories-by-stacy-devino-on-medium.md>)

Topics: [ExoPlayer](<https://devfeed.tech/topics/exoplayer.md>), [Android](<https://devfeed.tech/topics/android.md>), [picture-in-picture](<https://devfeed.tech/topics/picture-in-picture.md>), [User Interfaces](<https://devfeed.tech/topics/user-interfaces.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-app-development](<https://devfeed.tech/tags/android-app-development.md>), [exoplayer2](<https://devfeed.tech/tags/exoplayer2.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [nike](<https://devfeed.tech/tags/nike.md>), [picture-in-picture](<https://devfeed.tech/tags/picture-in-picture.md>), [video](<https://devfeed.tech/tags/video.md>)

### AI overview

The excerpt shows how to build an in-app Android player with ExoPlayer2: use SimpleExoPlayer with PlayerView, add the core, HLS, UI, and MediaSession extension libraries, select HLS or extractor media sources by URL type, and release the player in onStop(). For Picture-in-Picture (PiP), check Android version and device feature support, hide player controls, and enter PiP from onUserLeaveHint() and optionally onBackPressed(). The article reports that the Android Studio API available to its author could not check the user's PiP permission directly; it suggests checking whether the activity entered PiP after a short delay and falling back to back navigation if it did not. It also recommends finishAndRemoveTask() when the PiP activity stops, and a MediaSessionConnector for PiP playback controls. The excerpt warns that PiP can outlive the main app and proposes an onTaskRemoved() service signal to close the player activity. These are the article's version-specific workarounds; the excerpt does not establish their behavior on current Android versions.

### Source excerpt

Beautiful, interactive video content done easy. Video has been shown to increase engagement in apps and with content. How else could gif servicing apps be worth tens of millions and Youtube influencers be selling billions of dollars of product? The problem is that video in Android can be difficult. You are given the assumption that the video types you will support are pretty basic : embedded MPEG video, URLs to MP4/AVI files, and HLS Streaming. A naive approach would be to use the embedded video player sent with Intents, but that takes the user out of your app. You think, 🤔 " I'll just use the Android VideoView class with AppCompat ." Then you realize that it is nearly impossible to make the experience consistent across users because of codec support and whatever the phone manufacturer may have customized in the video player. Finally you settle on Exoplayer2 because it is the package everyone, including Google, uses. Upon further inspection, you quickly realize that it requires a lot of code to make it work and the example application on the Github is confusing, far too extensive for what you are doing. Another route you could take is ExoMedia by Brian Wernick, but it trades extensibility, theming, and control for simplicity. Fortunately, you only need the Exoplayer2 libraries to have a fantastic video player experience within your app. SimpleExoplayer "2" the Rescue First you need to make an app which can receive a URL and play it using Exoplayer. For this, you will need SimpleExoplayer and the Playerview from the UI package. Playerview has easy to manipulate styling/theming elements as well as available media controls. SimpleExoPlayer gives you a preconfigured player to work with without having to handle deeper logic yourself. Start by adding the Gradle dependencies to your build.gradle : implementation 'com.google.android.exoplayer:exoplayer-core:2.X.X' implementation 'com.google.android.exoplayer:exoplayer-hls:2.X.X' implementation 'com.google.android.exoplayer:

## April 2017 Meetup: ExoPlayer 2.0 & Lint - olin

DevFeed: [April 2017 Meetup: ExoPlayer 2.0 & Lint - olin](<https://devfeed.tech/articles/april-2017-meetup-exoplayer-2-0-lint-olin-38136.md>)

Original publisher: [Read original article](<https://touchlab.co/2017-4-april-2017-meetup-exoplayer-20-brushing-up-on-lint>)

Published: 2017-04-25T21:40:44Z

Content type: article

Language: en

Sources: [Touchlab](<https://devfeed.tech/sources/touchlab-enterprise-mobile-innovation-development.md>)

Topics: [ExoPlayer](<https://devfeed.tech/topics/exoplayer.md>), [Android](<https://devfeed.tech/topics/android.md>), [Library](<https://devfeed.tech/topics/library.md>), [issue tracking](<https://devfeed.tech/topics/issue-tracking.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [App](<https://devfeed.tech/topics/app.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [app](<https://devfeed.tech/tags/app.md>), [community](<https://devfeed.tech/tags/community.md>), [exoplayer](<https://devfeed.tech/tags/exoplayer.md>), [github](<https://devfeed.tech/tags/github.md>), [issue-tracker](<https://devfeed.tech/tags/issue-tracker.md>), [meetup](<https://devfeed.tech/tags/meetup.md>)

### AI overview

A recap of Touchlab's April 2017 meetup, featuring talks on ExoPlayer 2.0 and Android Lint. The ExoPlayer discussion emphasized understanding its architecture and initialization before customizing it, consulting the official samples carefully, and using the GitHub issue tracker as a learning resource.

### Source excerpt

For April, we welcomed Vimeo to our family of awesome meetup hosts! We thoroughly enjoyed their space, swanky arm chairs, and of course, sandwiches & pizza.