flutter-video-player-production-engineering
Installation
SKILL.md
Flutter video_player Production Engineering
Treat video_player as a thin Flutter controller/widget layer over platform media engines. Codec support, buffering, decoder limits, streaming behavior, autoplay, and many errors belong to Media3/ExoPlayer, AVPlayer, or the browser—not to Dart alone.
Reference routing
Read only what the task needs:
| Need | Reference |
|---|---|
| Current APIs, source constructors, widget/controller lifecycle, source replacement | references/01-api-and-lifecycle.md |
| Support matrix, Android/iOS/macOS backends, codecs, view types, desktop boundaries | references/02-platforms-and-formats.md |
| Network delivery, headers, HLS/DASH, Web autoplay/CORS/range requests | references/03-network-and-web.md |
| Decoder/memory/rendering cost, feeds, preloading, pooling, fullscreen transitions | references/04-performance-and-feeds.md |
| Audio, captions, background playback, PiP, errors, accessibility | references/05-playback-features-and-ux.md |
| Testing, profiling, diagnostics, review checklists, authoritative URLs | references/06-testing-diagnostics-and-sources.md |
The bundled research was checked on 2026-08-11 against video_player 2.13.0, video_player_android 2.12.0, video_player_avfoundation 2.11.0, and video_player_web 2.4.0. Always inspect the project’s pubspec.lock, Flutter/Dart versions, resolved federated implementations, and installed source before relying on a signature or platform behavior.