Reach Android viewers without rebuilding your service
Widevine is a natural foundation for Android video applications and supported browser experiences. DRM-X connects this device ecosystem to the same content catalog, server authorization and operational workflow used by your other DRM integrations. Your team keeps control of login, purchases, subscriptions and the player interface.
Support must be qualified by device and browser, not inferred from an Android label alone. Widevine provisioning, the security level, secure decoding, codecs and display outputs influence which protected tracks a device can play. A software-security device and a hardware-secure device may legitimately receive different playback quality.
Keep account credentials on your backend
Start with encrypted media published in the correct DRM-X Environment. When a viewer presses Play, your backend verifies the user's right to that Content ID and requests bounded authorization. The app receives the manifest reference and license configuration; it never needs your Site Key or Access Key.
The player delivers a Widevine challenge to the authorized license route. DRM-X evaluates the signed policy and returns a license the device CDM can process. The CDN transports encrypted media separately. A license service does not replace content hosting, and encrypting a file alone does not decide which customer may watch it.
Add offline viewing with the player you already use
The DRM-X Android SDK supports both streaming and persistent offline VOD. Use the complete DRM-X player, or keep an existing Media3 player and use only the license helpers. A native Media3-only implementation can use the same backend contract without the DRM-X AAR.
Prepare both the device-bound persistent license and the encrypted media while connected. Select every audio and subtitle language needed later, preserve the selected stream keys and check license duration before disconnecting. Renewal and release need connectivity in this workflow. A custom on-board server is a separate option when advance license acquisition is impossible.
- Complete encrypted download and valid CDM license
- Policy-compliant video plus all required language tracks
- Restart, expiry, renewal and fully disconnected device tests
Turn content requirements into a tested policy
Choose security, output and duration rules that match the package and the rights holder's requirements. Premium content may require hardware-secure decoding and protected external output; a successful demo is not studio certification. Multi-key offline content needs a persistent license covering every key required by the downloaded tracks.
DRM-X provides a common service boundary for token issuance, licensing and application integration. Your production acceptance should still cover real devices, account switching, entitlement changes, storage pressure and error recovery. Start with one representative title and device class, then widen the supported matrix.
Common questions
Is the DRM-X player mandatory?
No. Use DrmXPlayer for a guided start, DRM-X helpers with your own Media3 UI, or native Media3 with your backend implementation.
Can a downloaded movie play without internet?
On a qualified device, yes: it needs complete local encrypted media and a valid persistent device-bound license. A streaming license is not automatically an offline entitlement.
Does Widevine L1 guarantee 4K?
No. Content policy, codecs, decoder capability, device approval and output protection also matter.
Platform background: Google Widevine overview. Product behavior and deployment scope are described above; platform capabilities do not imply every customer deployment is qualified.