You can use our HTML5 video player to build video-oriented native mobile apps for Android and iOS. The player can be used in the following environments:
Our player has been tested and optimised to work in the above environments to provide a video experience that can match apps built with native SDK - minus the cost and headaches of having to manage native SDK.
Using Radiant Media Player to build native Android or iOS app is only available for PLATFORM edition customers.
Radiant Media Player can be used to build mobile applications for the following mobile OS:
All player features available for the mobile web are generally available with Radiant Media Player for mobile apps. Below is a non-exhaustive list of features you can expect to be available when using Radiant Media Player in a mobile app:
Feature | Android 5.1+ | iOS 12+ | iPadOS 13+ |
---|---|---|---|
HLS | |||
MPEG-DASH | (6) | ||
VAST video advertisement | (1) | (1) | (1) |
On-demand, Live & DVR streaming | (2) | ||
Low-latency live streaming | |||
360 video | |||
Autoplay with sound | |||
Widevine DRM | (4) | ||
FairPlay DRM | (7) | (7) | |
Google Cast | (5) | (5) | (5) |
AirPlay | |||
Offline playback/download/storage | (6) | ||
Offline DRM | (8) |
We do support using video ads in an iOS, iPadOS or Android mobile app built with Ionic, Flutter, Apache
Cordova or WebView. It should be noted that since the HTML5 Google IMA SDK is not officially supported in iOS
or Android WebView, the preferred solution is to use our VAST manager rmp-vast.
See this
section for more
information on limitations when using
the Google IMA HTML5 SDK in a mobile app. The VAST manager can be selected with player setting
adParser
set to 'rmp-vast'
.
It is perfectly possible to play Widevine DRM encrypted content in an Android apps built with Ionic, Flutter, Apache Cordova or WebView. Here are the requirements:
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.
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.
The following settings should only be used in the context of a mobile app:
appName: String
This setting allows to set a unique app name with Radiant
Media Player. This app name will then be used as an unique identifier in our back-end
reporting section. It can be read with API method
getAppName
. Default: ''.
Refer to our documentation for PLATFORM Edition allowlisting and denylisting.
©2015-2024 Radiant Media Player. All Rights Reserved.