How to Achieve Instant Short‑Video Playback on Android: Multi‑Player & Pre‑Download Strategies

Introduction

Short videos are a key content format for user engagement, and their playback experience directly influences user retention. This article discusses Android short‑video instant‑play optimization.

Problem Statement

Before optimization, the immersive short‑video page showed noticeable gaps in fluidity compared to mainstream apps, with two main issues:

Cover‑screen flash during playback start.

Slow streaming speed.

Target metrics include meeting hard requirements for playback success rate, first‑frame latency, and second‑play rate, as well as ensuring smooth user perception.

Test Environment

Phone: Pixel 4

OS: Android 10

Player: Taobao player

Problem Analysis

1. Home screen flash – A cover image is shown to avoid a blank screen, then hidden during playback. Even after optimization, the perceived start time is about 200 ms (excluding swipe). During swipe, the cover remains for ~600 ms, causing a noticeable flash and poor experience.

Solution: Display the video’s first frame during swipe instead of the cover, eliminating the flash.

2. Slow streaming – Server‑side issues (large files, poor network) can be mitigated with H.265 and CDN acceleration. Client‑side playback involves download → load + decode → render, which takes about 1 s. Pre‑downloading download‑load‑decode steps can reduce this latency.

Optimization Scheme Selection

Three schemes were evaluated:

Dual player + pre‑download – low memory, simple, but limited optimization.

Custom three‑player management + pre‑download – better experience, higher memory and complexity.

Three players based on RecyclerView cache + pre‑download – best experience, memory‑intensive.

Considering cost‑performance, the third scheme was chosen.

Scheme Three Principle

Before Page Turn

Current player starts playing video 1.

Pre and next players load video data 0 and 2.

Videos 3‑7 are added to the pre‑download queue.

After Page Turn

RecyclerView recycles holder and destroys its player.

onBind creates a new next player.

Current player starts playing video 2.

Pre player seeks to 0 and pauses; next player loads video 3.

Pre‑download queue adds videos 4‑8, avoiding duplicate downloads.

Specific Multi‑Player Refactor Steps

Set cache size:

mRecyclerView.setItemViewCacheSize(1); // set cache count

Override onBindViewHolder to create players, pre‑load and decode video, pausing at the first frame.

Listen to onPageRelease to pause and seek the exiting player to 0.

Listen to onPageSelected to start playback of the entering player.

Override onViewRecycled to destroy the player of the holder leaving the screen.

Note: Because decoding completes in onBindViewHolder, moving the view by just 1 px triggers surface rendering, instantly showing the first frame.

Benefits of the Three‑Player Approach

During vertical swipe, the entering screen shows the video’s first frame without visual stutter.

Pre‑creation and pre‑decoding of players eliminate preparation time before playback.

Eliminates cover‑screen flash, as the first frame is displayed directly.

Pre‑Download Optimization

Pre‑downloading the first‑frame segment (≈1 MB) for the next five videos reduces black‑screen time during fast swipes. Strategies include:

Download size: 1 MB per video, containing the first frame.

Pre‑download count: ahead of five videos (pageSize = 10).

Concurrency: synchronous queue to avoid bandwidth spikes.

Fast‑swipe handling: clear download queue during rapid page changes.

Download timing: push first five videos on loadMore, skip the next video on onPageSelected to avoid duplicate downloads.

Fast‑swipe is defined as multiple onPageRelease calls without an intervening onPageSelected, indicating the user skipped at least one page.

Cache Optimization

The existing Taobao player lacks file caching. Integrating the open‑source library com.danikula:videocache provides a local proxy (e.g., http://127.0.0.1:8888) that forwards video streams while saving them locally.

Future Outlook

Further work includes extending instant‑play to home‑page list videos, implementing resume‑play and memory optimizations, and managing a single player per page for reuse.