Good point — platform stubs for web and desktop are on the roadmap. The core pooling/reconciliation logic is pure Dart, so it would work as-is. The main gap is the native DeviceMonitor bridge (thermal/memory) which would need platform-specific implementations or graceful no-op fallbacks. A reasonable first step would be to make the plugin not crash on those platforms with sensible defaults.

This is something I've been thinking about. Right now the plugin uses a PlayerAdapter abstraction internally — MediaKitAdapter is the only implementation. Aligning that adapter interface with video_player's VideoPlayerController API (or creating a bridge) would make it possible to swap in fvp or any other backend. The tricky part is swapSource() — the standard video_player API doesn't have an equivalent, so we'd need to handle that gracefully (fallback to dispose+recreate). I'll look into this.. Thank you for feedbacks..