Recommendations for Submitting an Application to Apple's App Store

iOS App Publishing Requirements and Recommendations

Before publishing your application, we recommend that you to take the following steps:

• Deliver all content using HTTP Live Streaming (HLS)
• Make sure all content intended to be displayed on Apple devices is encoded properly with the correct flavors
• Make sure you have a 64Kbps audio stream for all content – Should be – stream with bitrate  lower than 64kbps
• Verify that you are implementing the correct URL format when calling playlists
• Download Apple verification tools and make sure you don’t receive any warnings or errors that may cause Apple to reject your application.
• View your content on all supported display types (Smartphones / Tablets / Apple TV) and try both Wi-Fi and cellular networks (where possible) and confirm good viewing quality. If not, make sure you have enough flavors to support fallbacks and large screen high quality bitrate. If you don’t have access to all types of devices, we may be able to do provide assistance. Please contact Kaltura for further assistance.
• Once your app is submitted, be patient as it may take up to few weeks for Apple to reply with an answer.

Display Types

Before deciding on sets of flavors suitable for your app, select the display types you want your app to support. When picking up flavors for your app, look at the column describing which display types the flavor is recommended for, and make sure you have your supported display types covered.

Cellular Network Support

If you would like to make your content available in a non Wi-Fi environment such as 3G networks, Apple requires you to enable a lower than 64Kbps, audio only, fallback flavor to support low connectivity scenarios.

Flavors & Display Types

The following table lists the recommended flavors per display type. Please use these flavors accordingly for the display types you intend to support:

URL Format

When retrieving asset of flavors available for an entry, it is strongly recommended to use the following format: 

http://cdnapi.kaltura.com/p/{partnerId}/sp/{partnerId}00/playManifest/entryId/{entryId}/format/applehttp/protocol/http/a.m3u8.

By using this format, Kaltura will automatically generate an m3u8 file containing all available flavors for a specific entry that are compliant with the requesting device’s playback capabilities.

If you are managing content with Kaltura that was not encoded for native application use, Kaltura has a process to automatically re-transcode your existing content library. Please contact support for further assistance.