Application UI Description

This topic describes the App UI Description file, required when submitting an application to the Samsung Apps TV Seller Office.

Application UI Description Template
(345 kB)

When submitting your application, you must include the Application UI Description created using the provided template file. The UI description documents your application UI and helps the QA certification team test the application efficiently. You must update and resubmit the application UI description file whenever you submit an application update.


Application UI Description Structure

On the title slide, enter the application and content provider name. The revision history documents the changes made to the application UI description. Include the file version, date, list of changes, and author. You must also define the application version related to the file version.

The application UI description consists of the following parts:

  • UI structure: Illustrates the overall structure and navigation flow between application pages.

  • Use cases: Provides detailed instructions for using the main application features.

  • Menus and functions: Labels and describes the screen components for all application screens, using screenshots.

  • Remote control keys: Describes the remote control key functions.

  • Language options: Specifies whether the application language can be changed and how to do it.


UI Structure

Use a flow graph, tree structure, or depth navigation diagram to illustrate the navigation between all screens in the application.

The UI structure diagram shows the overall structure of the application. It does not show or describe the content on individual screens.

Figure 1. Flow graph

Figure 2. Tree structure

Figure 3. Depth navigation


Use Cases

Describe the application functionality in detail, by dividing it into clear use cases. A use case is a specific and defined task the user can or must do, such as searching for content or playing a video. The use cases must cover the main functions or scenarios of the application. In addition to application-specific features, you must also describe any general user login, menu browsing, and in-app purchase features.

The following guidelines apply to use case descriptions:

  • Label each use case with a title.
  • For each use case, describe the steps the user must perform to do the task. You can use text, figures, and screenshots in the descriptions.
  • Since the launch process is the same for all applications, do not describe how to launch the application.
  • Refer to application screens with the names you have defined for them in the UI structure diagram.
Use Case Description Method Example
Using figures
Using text
Using screenshots

Table 1. Ways to describe use cases

Missing information is a major cause for application rejection. If your application includes any of the following features, you must provide additional information within the applicable use cases.

Application Feature Required Information
(missing information causes application rejection)
User login
  • Test account with a valid user ID and password
Device activation
  • Test account that permits an unlimited number of activated devices
  • Instructions for activating the device at an external website, if needed
In-app purchases
  • Valid credit card information for testing
  • Test account with funds available for making purchases
  • Valid coupon or promotional codes, if supported
Gaming
  • Cheat codes or master account for accessing all game levels
  • List of correct responses to any trivia questions
Smart View mobile integration
  • Mobile application package attached to the TV application submission
  • Instructions for connecting the mobile application to the TV
Geolocation or IP-restricted access
  • List of countries from which content can be accessed and permission to access the content through a VPN
  • Testing IP addresses added to allowed list

Table 2. Information required to avoid application rejection

Use labeled screenshots to describe the UI elements and their functions on each application screen.

The following guidelines apply to menu and function descriptions:

  • Provide a screenshot of each screen defined in the UI structure diagram.
  • Label all clickable and non-clickable UI elements with names or numbers. If there are many elements, use number labels.
  • Accompany each screenshot with a table describing the UI elements. For clickable elements, describe what happens when the element is clicked.
  • Provide English translations for titles, headings, and button labels, if needed.

Figure 4. Number labels

Figure 5. Text labels


Remote Control Keys

List the key mappings for any remote control keys that have been mapped to custom functions in your application:

  • Special function keys, such as the color, "Info", and "Tool" keys
  • Standard remote control keys whose function has been modified or disabled (for example, if the "Volume Up" key is implemented to zoom in on an image)

Language Options

If the application supports multiple languages, describe how the user can switch the application language, such as by changing the TV language or country settings, or selecting the language within the application settings.

If the application does not support multiple languages, state that the application has no language options.