You can use Radiant Media Player to build media-oriented web-based mobile applications for 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 Cordova-based application is only available for PLATFORM edition customers as FILE protocol support is required. Using Radiant Media Player within a standalone application or a WebView through the HTTP protocol is available for all player editions.
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:
|HTML5 video ads (1)|
|Widevine DRM (HLS or DASH)|
|VOD & Live streaming|
|Autoplay (with audio) support (3)|
|Mobile-first & responsive UI|
|Offline playback (5)|
Since Radiant Media Player 4.6.0 we support offline playback of media content (HLS, DASH or progressive download) within an Android or iOS web-based application. In order to be displayed, offline content must be locally stored within the application
(like in an assets/ or media/ folder). The player must point to this locally stored resource in order to start playback (through the usual
bitrates setting). The mechanism where online media content could be dynamically saved on
the device is not covered by Radiant Media Player.
adTagUrlsetting must point to this local resource. VAST metrics will not be ping since the device is offline.
Offline playback requires a PLATFORM Edition license key. Offline player starts are saved locally and push to our logging servers when an Internet connection becomes available.
As stated in the Cast SDK forum Google Cast casting from a Chromium WebView is not supported. Hence we do not support Google Cast casting from Radiant Media Player in an Android web-based mobile application. This does not mean it is not possible though. Google Cast support may be provided through a Cordova plugin. Various solutions are available on GitHub and while we do not recommend any specific solution, this one seems to be popular. When using such a plugin you would need to build your own cast and remote controlling logic outside the player.
Google Cast support through Radiant Media Player is available in standalone web applications or in Chrome for Android.
Refer to our Working with Apache Cordova guide.
Refer to our Working with Ionic Framework 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.