The automatically generated sections are Settings and Search as well as the Home section mentioned above. These sections cannot be changed.
A Category is a single row of videos and/or collections in the application. In the MRSS feed, it is represented by the <media:category> tag associated with videos. Please note the following In order to optimize user experience, we only show a Category (row) if it contains at least 3 videos. If less than 3 videos are associated with a single category, then the Category (row) will not appear in the final app, and the corresponding videos will only be visible in other categories that meet the criteria (if any) or in the general autogenerated categories like "Latest Videos" (see below). If there is only one category in the feed, its name is not displayed in the application UI.
This functionality is enabled for single-MRSS apps (apps created from one MRSS feed) but disabled for multi-MRSS (apps created from more than one MRSS feed).
Publication date is based on the PubDate tag from the feed.
These categories initially aggregate videos on a monthly basis. If such category contains only few videos then videos from the next month are added to fill it up.
The first entry (e.g first month) is removed to avoid similarity with the Latest Videos category.
A Collection is a single element in the application’s category row. It may look like a single video, but it represents the collection of multiple videos and categories located inside. In the MRSS feed, it is represented by the <vmrss:categoryData> tag.
Collections can be nested. Nesting of collection is defined in the path attribute of <vmrss:categoryData> tag, with each level of nesting separated with a slash. For example, ‘Winter/Events’ path for ‘Events’ collection defines ‘Events’ collection as a child of ‘Winter’ collection. There are no limits to the nesting of collections. In theory, an infinite number of levels can be used, but it is best to limit your levels of nesting to two or three. More levels can make navigation too complicated for the users. Collections should not be used if the selection of the content is not big. For example, if, in total, there are only 20 video clips or less available in the feed it is better to have them available in the section without breaking down to collections.
An Item is a single video. It is represented by the <item> tag in the MRSS feed. Items can belong to collections, categories and sections. Single items can belong to multiple categories and collections (for details see the MRSS Item structure below).
<media:content> with correct url & type.
You might also use <media:group> to group multiple media elements (like video in different formats)
Content might also contain duration and bitrate attributes.
Duration should be set by number of seconds.
For widest device support and best user experience, we recommend making sure that your minimum bitrate doesn't exceed 4000 kbit/s. Higher bitrate can be supported using adaptive bitrate streaming formats (e.g. HLS)
the value of the url attribute must be unique across the whole MRSS feed. In other words you should make sure there is only one <media:content> element for each unique URL. Failing to do so might lead to unexpected results
- <media:thumbnail> with correct url pointing to an image.
Snap supports both landscape and portrait video thumbnail orientation. Please note that the first image in a row determines the orientation of the video thumbnails in the whole row. The same image orientation (portrait or landscape) should be used throughout the whole application. Mixing various image orientations will cause problems with cropping images in automatically generated categories.
Snap will detect portrait orientation of thumbnail based on its width and height attributes provided in the MRSS feed. Those are optional parameters. If missing, Snap will assume landscape orientation.
If the portrait thumbnail will be used without width and height information then Snap will assume landscape orientation and will crop the thumbnail accordingly.
256 × 144 px format is recommended for landscape and 166 x 256 px for portrait thumbnails. If other sizes are used then Snap will crop and resize it to the desired size.
If there is more than one thumbnail then the best one will be selected based on width attribute (if present).
At at least one <media:category> is needed but an item can belong to many categories. It should contain a path to the actual category defined in the <vmrss:metadata> tag (if one is present) or just a simple name of the category must be present, but more are allowed if an item (video) belong to more then one category. The value of the <media:category> can be either free text or a "path" that matches the one provided via the path attribute of the <vmrss:metadata> tag. In case the item belongs to a nested category , a fully nested category path should be provided(e.g. to "black" under "video/cats/black") make sure to provide the full path.
The following children of the <item> tag are optional:
<item> <pubDate>Mon, 21 Mar 2016 11:00:01 GMT</pubDate> <media:title> Sam Smoothy Follows His Fathers Footsteps In The Andes | Lost… </media:title> <media:description> Many years ago, Sam Smoothy’s father climbed in the Andes mountains… </media:description> <media:category>Skiing</media:category> <media:category>Winter/Events</media:category> <vmrss:orderInCategory path="Winter/Events" value="12"/> <media:content url="video.mp4" type="video/mp4" bitrate="2200" duration="772"/> <media:thumbnail url="thumb.jpg" width="256" height="144"/> </item>
Since our server are distributed, in general we require feeds to be accessible. It is important that your MRSS feeds are available worldwide without any restrictions to e.g. location, IP addresses, User Agents or other. If any restriction is set then TV Snap servers may not be able to access and present your content.
In case it is a must have to limit access to your feeds by white-listing IP addresses then please use the below list. Please note that we recommend to not apply any restriction if not really needed though.
The following IP addresses must be allowed to access MRSS feeds:
Feed re-indexing rate
Feeds are index indexed by our ad system on submission. After that we periodically check of changes in the feed and update our index. The refresh rate is around 6 hours for now. This means that any change to your content availability (adding or removing videos or change of metadata) might take up to 6 hours to show up in the actual application.
The MRSS feeds structure (e.g. categories, collections, items structure, and nesting) and content can be changed after submission. We recommend updating the video content in feeds periodically and often (especially adding new content) as an incentive for end users to run the app regularly. Snap 3 updates the content every 6 hours from the feed. Although, the content structure should not change that often. (e.g. categories, collections, items structure, and nesting).
It is best to test the changes before publishing. In order to test submitted content, use the ‘Preview’ function in the Submission portal.
Some graphics graphical assets used by an application are provided through Submission portal, whereas other ones are provided in the MRSS feed. The image below shows the graphic assets tab in the Submission portal.
Wherever graphic assets are provided in the MRSS feed, an absolute url to your image file must be used as a tag value or attribute. The image below shows the placement of selected graphic assets in the application UI.
The Logo of your application is presented in the top-left top corner of the app. The Logo is provided through the submission portal and is not a part of the Snap MRSS formatfeed.
Background The background of an application is defined in the submission panel and it is not included in the MRSS feed.