You can use Radiant Media Player to build media-oriented web-based mobile applications on Android and iOS. The player is equipped with various optimisations, notably file:// protocol support, to work in the following environments:
Using Radiant Media Player in a WebView or in a Cordova-based application is only available for PLATFORM edition customers.
Radiant Media Player can be used to build web-based mobile applications for the following mobile OS:
It is possible that Radiant Media Player used in web-based mobile applications would work on previous versions of Android or iOS but they are not officially supported.
All player features available for the mobile web are generally available with Radiant Media Player for web-based mobile applications. Below is a non-exhaustive list of features you can expect to be available or not when using Radiant Media Player in a web-based mobile application:
| Feature | Android | iOS |
|---|---|---|
| HLS (Clear or AES-128/SAMPLE-AES or Widevine DRM) | ||
| DASH (Clear or Widevine DRM) | ||
| Progressive download | ||
| HTML5 video ads (1) | ||
| VOD & Live streaming | ||
| DVR streaming | (2) | |
| 360 video | (3) | |
| Autoplay (with audio) support (4) | ||
| Mobile-first & responsive UI | ||
| Player API | ||
| Google Cast (5) | ||
| Offline mode (6) |
A WebView is a view generated by native code on Android or iOS that displays web content. When embedded in a WebView the player assumes the file:// protocol is used and opts
for various optimisation to better fit this environment. In such cases the player adds the rmp-webview class to its container (HTML element with the
rmp-container class). You can also query the player API
isWebView method which should return a boolean clearly stating if the player is currently used in a WebView or not.
Refer to our Working with Apache Cordova guide.
Refer to our Working with Adobe PhoneGap guide.
A standalone web application is designed to look and behave in a way similar to a native application - for example, it is scaled to fit the entire screen of a device. You can tailor your web application for Safari on iOS or Chrome for Android even further, by making it appear like a native application when the user adds it to the "Home screen".
When embedded in a standalone web application the player adds the rmp-standalone class to its container (HTML element with the
rmp-container class). You can also query the player API isStandalone method which should return a boolean clearly stating if the player is currently used in a standalone web-app or not.
Apple has documentation on how to configure standalone web applications. Notably this is achieved by adding the following meta tag to your HTML page:
<meta name="apple-mobile-web-app-capable" content="yes">
For Chrome on Android Google has a guide for Installable Web Apps with the Web App Manifest. This approach follows the W3C Web App Manifest specification which is also available in Firefox and Opera.