// the take
An Android + HarmonyOS Next audio/video playback SDK wrapping FFmpeg, dav1d, OpenSSL and SoundTouch behind a Java/ArkTS API, aimed at teams that need a drop-in player with protocol coverage (http/rtsp/rtmp/byte[]), AV1 decode, encrypted video, and oddball features like transparent video or seamless surface switching — think car infotainment, set-top boxes, or KTV-style multi-screen apps rather than a typical mobile video app.
The feature list genuinely covers things ExoPlayer makes you build yourself: transparent/alpha video playback, simultaneous multi-surface rendering, seamless surface swapping without a black flash, per-instance variable speed/pitch, and live PCM tap-off for metering. It's one of the few player SDKs that targets HarmonyOS Next natively alongside Android, with parallel ArkTS and Java APIs and a shared native core. The API itself is a thin, sane listener pattern (setSource/prepare/start plus onPrepared/onComplete/onTimeInfo callbacks) that doesn't fight you for basic playback. Six years of commit history and an active HarmonyOS port suggest this isn't an abandoned side project.
The actual player — libwlplayer.so, libwlffmpeg.so, libwlmediautil.so — ships as prebuilt binary blobs in jniLibs; there's no native source in the repo, so you can't audit, patch, or rebuild the decode/render path yourself, and any native bug or security issue is entirely dependent on one maintainer's release schedule. It's not actually free: the Android build burns a visible watermark into every video frame unless you pay the author per package name to remove it, which is a licensing gotcha easy to miss until you're ready to ship. Test coverage is the default Android Studio stub files (ExampleInstrumentedTest, ExampleUnitTest) — nothing exercises real playback, seeking, or format-switching paths. The only performance claim versus ExoPlayer is a single screenshot comparison on one device with one test clip, not something you can reproduce or trust for your own workload. Support runs through a personal email and a QQ group rather than GitHub issues, so there's no public record of known bugs or response times.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →