application registration guide - samsung...

Application Registration Guide

SAMSUNG Electronics

2

Application Registration Guide

Index

1. From Application Registration to Sale .................................................................................. 3

1) Application Registration ............................................................................................... 3

2) Certification Process .................................................................................................... 3

3) Certification Evaluation ................................................................................................ 3

2. Application Registration Screen .......................................................................................... 4

3. Selecting Application Type & Default Language ..................................................................... 6

4. Enter Application Information ............................................................................................. 7

1) App Information Menu ................................................................................................. 7

2) Binary Menu ............................................................................................................. 12

3) Country & Price Menu ................................................................................................ 16

4) In App Purchase Menu ............................................................................................... 19

5) Certification Menu ...................................................................................................... 21

5. Attachment .................................................................................................................... 22

1) Binary Extraction Information ....................................................................................... 22

① Binary Basic Information ......................................................................................... 22

② Android Device Recommendation Information ................................................................ 22

③ Tizen Device Recommendation Information .................................................................. 24

④ Galaxy Specials Information ..................................................................................... 24

⑤ Additional Information and Gear Linked (Host) Deeplink .................................................. 25

2) Precautions for Binary Registration ............................................................................... 26

3

1. From Application Registration to Sale

1) Application Registration

- Click 'Add a New Application' to register a new application.

- Once added, the application will move on to the Certification Process stage.

2) Certification Process

- The Certification Process status is shown as 'Pre-Certification' in the [Applications > My Applications] menu.

- If through the process the application is rejected, the seller can check the reason by clicking the 'R' icon to

the right of 'Pre-Review Rejected' in [My Applications]. The seller will receive an email about this.

- The process will be completed within a day. Once the application passes this process, it will move on to the

Certification Evaluation stage.

* For information about the application status shown in [My Applications], refer to the 'Seller Office User Guide.'

3) Certification Evaluation

- Once the application passes the certification evaluation, its status will be shown as 'For Sale' in [My

Applications], and it will be available for sale in the store within 24 hours.

- If it does not pass the evaluation, its status will be shown as 'Rejected' or 'Suspended' in [My Applications].

The seller can check the reason by clicking the 'R' icon to the right. The seller will receive an email about this.

* For information about certification evaluation items, refer to the 'Certification Guide.'

4

2. Application Registration Screen

① Select the required menu and start entering information.

② Check the tips below the fields (2-2) .

Change (2) Show Tips to On to expand all tips. To check the tips one by one, click (2-1) .

③ If you want to add your application with only the required fields filled in, click the [Simple] mode toggle button.

5

To enter additional information or other details about devices and countries, click the [Advanced] mode toggle

button.

④ If the information entered has an error, an alert message will appear in red at the bottom.

⑤ When entering information, click the [Save] button frequently.

If you do not enter anything for 20 minutes, you will be automatically logged out. Click the [Save] button

frequently to avoid losing any information entered. However, if the information entered has an error, an alert

message will appear in red and the information will not be saved.

⑥ Check the color of the [Submit] button to see whether or not the information can be submitted.

If the required fields have not been saved, meaning that the application cannot be submitted, the [Submit]

button will be in gray. If you click the button while it is gray, the required fields that still need to be filled in will

be marked.

If all the required fields are saved, meaning that the application can be submitted, the [Submit] button will be

red. If you click the button while it is red, your application will be submitted. Please note that if there is a

discrepancy between the information entered in each LNB menu, an alert will pop up. In some cases, you

might not be able to submit the application. If an alert message pops up, modify the information accordingly.

6

3. Selecting Application Type & Default Language

- Please select the type of the application you want to add.

- Select the default language in which you will provide application information in the store, and click [Next].

7

4. Enter Application Information

1) App Information Menu

Each item of the App Information menu is described below. In Simple mode, only the fields marked as required (*)

will be displayed. The other fields will be displayed in Advanced mode only.

A. Language: The language in which you will provide application information in the store

- Click [Add Language] to add local languages in which you want to provide application information. If you do

not add any local languages, the information will be provided in the default language.

- Click [Select Language] to select one of the additional languages. Fields where you can enter information in

the local language will appear.

B. Application Name (*): Application name displayed in the store

- You can enter up to 100 bytes.

- You cannot use the names of existing applications that are already registered or on sale for the devices you

are registering your application for.

- You cannot use the names of other sellers' applications that are already registered or on sale.

C. Linked (Master) Application Name (Gear *): Name of an application linked to Linked (Follower) Applications


- You can only enter this if you selected Linked (Follower) in [2) Binary Menu > A. Gear App Type].

D. 1-line App Description: A short app description displayed in the application list of the Chinese store

8


- You can enter this if you selected Simplified Chinese in [Select Language].

E. Description (*): Description of your application


- If you sell your application in 2 or more countries, you must select English as the default language and enter

the description in English.

- If you selected Linked (Follower) in [2) Binary Menu > A. Gear App Type], you must enter text that says the

users must install the linked application on their devices as well.

F. New Features: Changes in the updated application


G. Tag: Application search tags

- You can enter upto 15 tags to help people search for and find your application, using upto 1500 bytes for all

tags combined.

H. Icon and Screenshot (*): The application icon and screenshot displayed in the store

9

- Icon image requirements

∙ PNG file

∙ 512 x 512 pixels

∙ Maximum of 1024 kb

- Edge Screen's icon image requirements (Edge Single Mode, Edge Feeds Mode *)

∙ If your application is an Edge Single Mode application or an Edge Feeds Mode application, register Edge

Screen icons only. You can check a binary's Edge Mode status in [2) Binary Menu > C. Detailed Binary

Information].

∙ PNG file

∙ 160 x 2560 pixels


- Edge Screen – Single + icon image requirements (Edge Single + Mode *)

∙ If your application is an Edge Single + Mode application, register Edge Screen – Single + icons only. You

can check a binary's Edge Mode status in [2) Binary Menu > C. Detailed Binary Information].

∙ PNG file

∙ 550 x 2560 pixels


∙

- Screenshot image requirements

∙ PNG or JPG file

∙ Minimum of 320 pixels and maximum of 3840 pixels. The maximum size must not exceed twice the

minimum size.

∙ You can register 4 to 8 images.

I. Category (*): The store category where the application will be displayed

10

- The number of categories to choose may vary depending on the seller type (Partner, China, MENA,

Developer) and application type.

- If you select a category that is not suitable for the application, it may be changed automatically.

J. Age Restriction (*), Kids Age Restriction (Kids *): The age rating suitable for the application

- Select an age rating. For the selected age rating's conversion standards per country, refer to the 'Age Rating

Guide.'

K. Rating Certificate for Available Countries: Register age ratings settings and support files for each country

- Register image files of your age restriction document issued by related associations. The speech balloon

icon located to the right of each age rating shows details about the age rating.

∙ PNG, JPG or GIF file

- If you selected Game in [I. Category], please refer to the following.

∙ For age ratings related to game content, such as ESRB, PEGI, GRB, and MJ/DEJUS, please check the

'Age Rating Guide' first.

∙ If you select 18+ in [J. Age Restriction], 18 will be automatically selected for MJ/DEJUS age restriction.

∙ To sell a game application in Korea for which 18+ is selected in [J. Age Restriction], you must register

GRB age restriction settings and support image files.

L. Supported Languages (*): Languages supported by the application

M. YouTube URL: The application's promotional video which will be displayed in the store

11

- Please enter the 11-digit video ID of the YouTube URL.

N. Items to be Displayed in 'Seller info' in the Store: Items to be displayed in Seller info

12

① Copyright Holder: Name of the person or company who owns the application's copyright. You can enter

up to 1000 bytes.

② Privacy Policy URL: The application's Privacy Policy. If you selected Kids in [I. Category], make sure to

enter your Privacy Policy URL.

③ Customer Support URL (*): Main website address

④ Customer Support Email (*): The email address that users can send application-related queries to

⑤ Open Source URL: Open source software license used for the application

O. Notification Email: Email address to which you want to receive application status change emails from the

Seller Office

- You can enter up to 20 email addresses.

2) Binary Menu

The following describes the Binary menu. In Simple mode, only the fields marked as required (*) will be displayed.

The other fields will be displayed in Advanced mode only.

A. Gear App Type (Gear *): The type of Gear application being registered

- Please be careful when choosing a Gear app type because you cannot change it once the application is for

sale.

- If you select Integrated or Linked (Follower), you can only update applications that are already for sale.

B. Add Binary (*): Binary file registration and option settings

13

- You can register up to 10 binary files. All the binaries in a single application must have the same extension.

- Select the resolution of the devices for which you will sell your application. For a Gear application, resolutions

for Gear devices will be displayed.

- If your application uses the Google Mobile Service, please select 'Yes.' If you select 'Yes,' China will be

automatically excluded from the list of countries.

- All binaries registered in an application must support the same properties (Gear App Type and Edge Mode).

You can check the properties in the results of automatic binary extraction. For details, refer to [5. Attachment

> 1) Binary Extraction Information].

∙ Gear App Type e.g. After registering a Standalone binary, you cannot register additional Linked

(Wearable) binaries.

∙ Edge Mode e.g. After registering an Edge Single Mode binary, you cannot register additional Edge

Feeds Mode binaries.

- Apart from underscores ( _ ), special characters and spaces cannot be used in a binary file's name. Also, you

cannot use the same file name as those of uploaded binaries.

- For detailed precautions for binary registration, refer to [5. Attachment > 2) Precautions for Binary

Registration] and [5. Attachment > 1) Binary Extraction Information > ① Binary Basic Information].

C. Detailed Binary Information: Binary information to refer to when registering applications

14

① The icon that shows the binary's status will be displayed by the name of the registered binary file.

∙ Registering: A new application is being registered or the binary is being replaced.

∙ Passed: The binary passed the certification evaluation.

∙ Rejected: The binary was rejected during certification evaluation.

∙ On Sale: The application is for sale, in the form of binaries.

② Click the arrow to the right of the binary file's name to see its details.

③ Device: The number of devices selected for the binary.

④ Edit: You can replace the uploaded binary file or change its resolution and GMS info.

⑤ Version Code & Version Name: Application version displayed in the store or managed by the seller. It is

extracted from the binary and displayed accordingly. For details, refer to [5. Attachment > 1) Binary Extraction

Information > ① Binary Basic Information].

⑥ Device Recommendation Information: Devices will be recommended based on this information and resolution.

Information for each field will be extracted from the binary and displayed accordingly. For details, refer to [5.

Attachment > 1) Binary Extraction Information > ② Android Device Recommendation Information, ③ Tizen

Device Recommendation Information].

⑦ GALAXY Specials Information: It shows whether a Samsung SDK was used or not. Developer-type Sellers

15

can only register applications using one or more Samsung SDKs. Information for each field will be extracted

from the binary and displayed accordingly. For details, refer to [5. Attachment > 1) Binary Extraction

Information > ④ Galaxy Specials Information].

⑧ Additional Information: Information referred to during application certification evaluation.

⑨ Resolution: Devices will be recommended based on this information and device recommendation information.

The resolution selected in [B. Add Binary] will be displayed.

D. Selected Device/Detailed Device Settings: Function to set up devices for binaries

- If you click the number to the right of [Selected Device], [Detailed Device Settings] will pop up and you can

select devices for each binary. Refer to [5. Attachment > 2) Precautions for Binary Registration > C. Criteria

for Binary Display in the Store] when selecting devices.

- A list of all devices, which are determined to be suitable for your application based on the device

recommendation information in [C. Detailed Binary Information] and resolution, will be displayed. However,

you cannot select devices that are not available for all binaries, and devices not suitable for your application

will not be displayed.

- For a Gear application, a list of devices will appear in a combination of a mobile device paired with a Gear

device.

∙ e.g. Galaxy S6-Gear S2: The application will be available to sell when the Galaxy S6 device and the

Gear S2 device are connected.

- For Gear applications for certain Tizen OS's, you can select devices in a combination of non-Samsung

16

mobile device and Gear device as well.

∙ In the [Detailed Device Settings] pop-up, the combination of a non-Samsung mobile device (Android OS

& iOS) and a Gear device will be displayed as 'Devices other than Samsung (Android)' and 'Devices

other than Samsung (iOS).' You can only select whether services will be provided or not. Even if you

select yes, services might not be available on certain mobile devices depending on their specs.

∙ For Standalone Gear applications, you can select 'Devices other than Samsung (Android)' and 'Devices

other than Samsung (iOS)' as well.

∙ For Linked (Wearable) Gear applications, you can select 'Devices other than Samsung (Android)' as well.

E. Non-recommended Devices/Check Compatibility of Non-recommended Devices: The function that

checks why the binary cannot be sold for certain devices

- If you click [Non-recommended Devices], the [Check Compatibility of Non-recommended Devices] pop-up

will appear, and you can check the compatibility between unavailable devices and the registered binary.

- If you want to sell your binary to devices that appear to be unavailable, refer to [C. Detailed Binary

Information] and change your binary information.

3) Country & Price Menu

The following describes the Country & Price menu. In Simple mode, only the fields marked as required (*) will be

displayed. The other fields will be displayed in Advanced mode only.

A. Price (*): Settings for the application's selling price

- To make your application a paid one, you need to change your status to Commercial Seller.

- If you switch between Free and Paid, the distribution country and price information will be reset.

- The standard price entered is in USD, and the local price for the country is automatically applied based on

the exchange rate of the day.

B. Payment Method: Notice and settings for a paid application's payment method

17

- Check the precautions for each payment method. You can only set up the phone bill method on your own.

C. Country: The function to set up countries of sale and prices for each country

- If you do not set up countries of sale, your application will be automatically sold in all available countries. The

list of available countries is subject to change, depending on the situation.

∙ Countries and regions where you can sell your application, depending on its price setting

Both paid and free applications

can be sold Europe, CIS, Asia, The Americas, Middle East & Africa, Global A

Only free applications can be sold Pan-Latin, Pan-Africa, Global Free

∙ A list of countries that are unavailable in each situation

① Your application uses the Google Mobile Service

* Check the settings in [2) Binary Menu > C. Detailed Binary Information].

China ② The Linked (Host) Deeplink set in the Gear Linked (Wearable) binary is

available from Google Playstore only


③ Your application uses Plasma (Samsung In App Purchase)


Countries and regions

where only free

applications can be

sold

④ Your application uses VoIP


⑤ Application with the age restriction 18+

* Check the settings in [1) App Information Menu > J. Age Restriction].

Saudi Arabia, Kuwait,

and Bahrain

⑥ Application where the GRB age rating is 18+ but there is no certification

document

* Check the settings in [1) App Information Menu > K. Rating Certificate

for Available Countries].

Korea

⑦ The seller's nationality is US American Iran

- If you enter the standard price of [A. Price] and click the [Apply] button, the prices for all countries will be

18

automatically changed, based on the exchange rates of the day.

- You cannot enter a price lower than the minimum price. The minimum unit and minimum price may vary by

country.

- The phone bill in [B. Payment Method] will be applied only after you click the [Apply Phone Bill] button. If you

choose phone bill, your application may be sold at a different price from the price entered. So make

sure to check it after applying the method. Galaxy Apps is not responsible for any loss incurred due

to user negligence in checking prices. Please take the precautions below.

∙ Make sure to check the amount allowed for phone bill payment for each country. You can only replace

the price with selectable amounts, and the amounts allowed for phone bill payment varies by

country.

∙ Click the [Apply Phone Bill] button, and the amount for phone bill payment that is the closest to the

entered price will be automatically selected. If the price entered is higher than selectable phone

bill amounts, the highest phone bill amount will be selected. Please make sure to check the

changed prices next to each country.

- For countries where carriers have different phone bill prices, click [Carrier Prices] for details.

19

∙ If you click a displayed price, payment will go through with the price of the corresponding carrier. In the

store, the displayed prices will be shown as the main prices.

∙ Example for Russia) If you select 35 p., the application price will be shown as 35 p. in the Russian store.

But users of MTS will pay 33.53 p. for the application.

D. Selling Starts: The settings for the date when the application becomes available for sale

- If you put a checkmark in [Selling Starts on the Day of Approval], the application will automatically become

available for sale on the day of certification evaluation approval.

E. Selling Ends: The settings for the date when the application is withdrawn from the store

- If you put a checkmark in [Permanent], the application will continue to be available for sale as long as it has

no issues.

4) In App Purchase Menu

The following describes the In App Purchase menu. The menu will be activated only after you register a binary to

which Samsung In App Purchase (Plasma) is applied. In Simple mode, only the fields marked as required (*) will

be displayed. The other fields will be displayed in Advanced mode only. For details, refer to the 'In App Purchase

Guide.'

A. In App Purchase List: A list of registered IAP items

20

- If you register a binary with IAP applied, an [Item Group ID] and [Item Group Name] will be automatically

provided. The [Item Group ID] is a unique ID that distinguishes an item group from other groups in the store,

and cannot be changed. The [Item Group Name] is a name that distinguishes the seller's item group from

others' groups. It can be modified, and used for multiple items groups.

- Once the application becomes available for sale, its item groups cannot be changed. However, each item's

information can be modified.

- If the application has item groups with the same App ID (Package Name) as the application, you can load

them using their [Item Group ID].

B. Add Item/Update Item: Add IAP items and update added items

- Use [Switch to Simple Mode] to enter only the required item information, or use [Switch to Advanced Mode]

to register item details as well.

- Item types include Consumable, Non-consumable, Non-recurring subscription, and Auto-recurring

subscription. Once the application becomes available for sale, you cannot change item types.

∙ Consumable: Use the item once, and then it will disappear.

∙ Non-consumable: Purchase the item once, and use it continuously. Items can be restored after the

application is deleted and reinstalled.

∙ Non-recurring subscription: Purchase once and receive items regularly. Items can be restored after the

application is deleted and reinstalled.

∙ Auto-recurring subscription: After the initial payment, payment recurs and items are provided every time

a new cycle specified by the seller begins. Items can be restored after the application is deleted and

reinstalled.

- Applications where IAP is applied are regarded as paid applications. For information about payment methods

and how to use the Country menu, refer to the [3) Country & Price] menu.

C. Item Bulk Upload: Function to upload multiple items in bulk

- Enter item information in the provided Excel file, and upload it. The entered items will be registered at the

same time and displayed in the list.

21

5) Certification Menu

The following describes the Certification menu. In this menu, you can register reference materials for those who

will evaluate your application. For information about certification evaluation items, refer to the 'Certification Guide'.

A. Comments for the Certification Team: References for application certification evaluation

- If your application requires login and payment testing, you need to provide a temporary ID, password, and

fake card number, in order for it to be evaluated correctly. If incorrect or insufficient information is provided,

your application may be rejected.

- Apart from the information above, your application's concept, precautions for testing, and other information

will be helpful for accurate and fast evaluation.

- If it is not the first time your application is evaluated, or if your application has been updated, please enter

every change.

- You can respond and send attachments for app certification, such as copyrighted materials and video links

for certification review reference. (Attachment limit: 10Mb)

22

5. Attachment

1) Binary Extraction Information

The following describes the items automatically extracted from registered binaries. For Android APKs, the values

will be extracted from manifest.xml. For Tizen TPKs, they will be extracted from tizen-manifest.xml, and for WGTs,

they will be from config.xml. You can only register binaries if all required fields are complete (*).

① Binary Basic Information

Field Description

App ID (Package Name)

(Android *) (1000 bytes)

Extracted only if the OS is Android.

Package ID (Tizen *) (1000

bytes)

Extracted only if the OS is Tizen.

Version Name (*) (1000 bytes)

The values below will be extracted from the version.xml file of the

application displayed in the store.

∙ APK: Version Name

∙ WGT/TPK: Version

* Version Code is an integer converted from Version Name, and it is used

to compare binary versions when an application is registered.

API (MinSdkVersion)

· APK: minSdkVersion (default value: 1)

· WGT: api-version (default value: 1)

· TPK: required_version (default value: 2.3.1)

② Android Device Recommendation Information

∙ If there are no criteria for determining if a field is used or not used, 'not used' is the default value. The

exception is TouchScreen where 'used' is the default value.

∙ If your binary uses every field, we only recommend the devices that support the corresponding functions.

If your binary does not use the fields, we recommend all devices. However, if Faketouch is used while

TouchScreen is not used, we only recommend Homesync devices.

Field Description

Telephony

(Call/SMS)

∙ When one or more instances of uses-feature exists in the manifest * <uses-feature android:name="android.hardware.telephony" android:required="true"/> * <uses-feature android:name="android.hardware.telephony"/> * <uses-feature android:name="android.hardware.telephony.cdma" android:required="true"/> * <uses-feature android:name="android.hardware.telephony.cdma"/> * <uses-feature android:name="android.hardware.telephony.gsm" android:required="true"/> * <uses-feature android:name="android.hardware.telephony.gsm"/> ∙ When one or more instances of uses-permission exists in the manifest * <uses-permission android:name="android.permission.CALL_PHONE" /> * <uses-permission android:name="android.permission.CALL_PRIVILEGED" /> * <uses-permission android:name="android.permission.MODIFY_PHONE_STATE" /> * <uses-permission android:name="android.permission.PROCESS_OUTGOING_CALLS" /> * <uses-permission android:name="android.permission.READ_SMS" />

23

* <uses-permission android:name="android.permission.RECEIVE_SMS" /> * <uses-permission android:name="android.permission.RECEIVE_MMS" /> * <uses-permission android:name="android.permission.RECEIVE_WAP_PUSH" /> * <uses-permission android:name="android.permission.SEND_SMS" /> * <uses-permission android:name="android.permission.WRITE_APN_SETTINGS" /> * <uses-permission android:name="android.permission.WRITE_SMS" />

∙ When uses-feature required = "false": uses-feature has priority, even when the Telephony permission is given. Therefore, the binary is considered to not support Telephony. * <uses-feature android:name="android.hardware.telephony" android:required="false"/> * <uses-feature android:name="android.hardware.telephony.cdma" android:required="false"/> * <uses-feature android:name="android.hardware.telephony.gsm" android:required="false"/> ∙ When neither uses-feature nor uses-permission is present in the manifest

NFC

∙ When one or more instances of uses-feature exists in the manifest * <uses-feature android:name="android.hardware.nfc" android:required="true"/> * <uses-feature android:name="android.hardware.nfc"/> ∙ When the uses-permission below exists in the manifest * <uses-permission android:name="android.permission.NFC"/>

∙ When uses-feature required = "false": Even if NFC permission is given, the binary is considered to not use NFC because uses-feature has priority. * <uses-feature android:name="android.hardware.nfc" android:required="false"/> ∙ If neither uses-feature nor android.permission.NFC exists in the manifest

Edge Single

Mode

∙ If the following metadata is present in the manifest file, the binary is considered to use Edge Single Mode. * <meta-data android:name="com.samsung.android.cocktail.mode“ android:value="edge_single" />

∙ If the following metadata is present in the manifest file, the binary is considered to use Edge Immersive Mode. * <meta-data android:name="com.samsung.android.cocktail.mode“ android:value="edge_immersive" />

If the following meta-data is present in the manifest file, the binary is considered to use Edge Feeds Mode. * <meta-data android:name="com.samsung.android.cocktail.mode“ android:value="edge_feeds" />

∙ If the following metadata is present in the manifest file, the binary is considered to use Edge Single + Mode. * <meta-data android:name="com.samsung.android.cocktail.mode“ android:value="edge_single_plus“ />

∙ When metadata does not exist in the manifest

Faketouch

∙ When one or more instances of uses-feature exists in the manifest * <uses-feature android:name="android.hardware.faketouch" android:required="true"/> * <uses-feature android:name="android.hardware.faketouch"/> * <uses-feature android:name="android.hardware.faketouch.multitouch.distinct" android:required="true"/> * <uses-feature android:name="android.hardware.faketouch.multitouch.distinct"/>

∙ When uses-feature required = "false" * <uses-feature android:name="android.hardware.faketouch" android:required="false"/> * <uses-feature android:name="android.hardware.faketouch.multitouch.distinct" android:required="false"/> ∙ When no instances of uses-feature case exist in the manifest

24

TouchScreen

∙ When one or more instances of uses-feature exists in the manifest * <uses-feature android:name="android.hardware.touchscreen" android:required="true"/> * <uses-feature android:name="android.hardware.touchscreen"/> * <uses-feature android:name="android.hardware.touchscreen.multitouch" android:required="true"/> * <uses-feature android:name="android.hardware.touchscreen.multitouch"/> * <uses-feature android:name="android.hardware.touchscreen.multitouch.distinct" android:required="true"/> * <uses-feature android:name="android.hardware.touchscreen.multitouch.distinct"/> * <uses-feature android:name="android.hardware.touchscreen.multitouch.jazzhand" android:required="true"/> * <uses-feature android:name="android.hardware.touchscreen.multitouch.jazzhand"/> ∙ When no instances of uses-feature case exist in the manifest

∙ When the following uses-feature exists in the manifest * <uses-feature android:name="android.hardware.touchscreen" android:required="false"/>

③ Tizen Device Recommendation Information

∙ If there are no criteria for determining if a field is used or not, 'not used' is the default value.

∙ If your binary uses every field, we only recommend the devices that support the corresponding functions.

If your binary does not use the fields, we recommend all devices.

Field Criteria for determining usage

Camera ∙ When the following feature exists in the manifest

* <Feature Name="http://tizen.org/feature/camera" />

GPS ∙ When the following feature exists in the manifest

* <Feature Name="http://tizen.org/feature/location.gps" />

Network

∙ When one or more of the following features exists in the manifest

* <Feature Name="http://tizen.org/feature/network.telephony" />

* <Feature Name="http://tizen.org/feature/network.telephony.mms" />

* <Feature Name="http://tizen.org/feature/network.telephony.sms.cbs" />

* <Feature Name="http://tizen.org/feature/network.wifi" />

IrLED ∙ When the following feature exists in the manifest

* <Feature Name="http://developer.samsung.com/tizen/feature/irled" />

UV ∙ When the following feature exists in the manifest

* <Feature Name="http://developer.samsung.com/feature/sensor.ultraviolet" />

Air pressure ∙ When the following feature exists in the manifest

* <Feature Name="http://tizen.org/feature/sensor.barometer" />

Magnetic ∙ When the following feature exists in the manifest

* <Feature Name="http://tizen.org/feature/sensor.magnetometer" />

Ambient ∙ When the following feature exists in the manifest

* <Feature Name="http://tizen.org/feature/sensor.photometer" />

Heart rate ∙ When the following feature exists in the manifest

* <Feature Name=“http://developer.samsung.com/tizen/feature/heart_rate_monitor” />

④ Galaxy Specials Information

25

∙ You can select the Galaxy Specials category only if the binary uses one or more of the following fields.

∙ If there are no criteria for determining if a field is used or not, 'not used' is the default value.

Field Criteria for determining usage

Samsung

Developer

SDK

∙ When the following user-permission exists in the manifest

* <uses-permission

android:name="com.samsung.android.providers.context.permission.WRITE_USE_APP_FE

ATURE_SURVEY" />

Samsung

IAP SDK

∙ When the following user-permission exists in the manifest

* <uses-permission android:name="com.sec.android.iap.permission.BILLING"/>

S Pen SDK ∙ When the following uses-feature exists in the manifest

* <uses-feature name="com.sec.feature.spen_usp" android:required="true"/>

Smart

Connectivity

SDK

∙ When the following metadata exists in the manifest

* <meta-data android:name="SmartConnectivity" android:value="true" />

PEN.UP

SDK

∙ When the following metadata exists in the manifest

* <meta-data android:name="PENUP" android:value="true"/>

⑤ Additional Information and Gear Linked (Host) Deeplink

Field Description

Additional

Information -

VoIP

∙ When one or more of the following exists in the binary

* <uses-feature android:name="android.software.sip.voip" android:required="true"/>

* <uses-feature android:name="android.software.sip.voip"/>

* <uses-feature android:name="android.hardware.sip.voip" android:required="true"/>

* <uses-feature android:name="android.hardware.sip.voip"/>

∙ When one or more of the following exists in the binary

* <uses-feature android:name="android.software.sip.voip" android:required="false"/>

* <uses-feature android:name="android.hardware.sip.voip" android:required="false"/>

Gear Linked

(Host)

Deeplink

(Gear

Linked

(Wearable)

*)

∙ If the following metadata exists in the xml, SAMSUNG Galaxy Apps Deeplink information

will be considered to be included.

* <tizen:metadata key="master_app_samsungapps_deeplink" value="[SAMSUNG Galaxy

Apps deeplink URL]"/>

∙ If the following metadata exists in the xml, Google Playstore Deeplink information will be

considered to be included.

* <tizen:metadata key="master_app_playstore_deeplink" value="[Google Playstore deeplink

URL]"/>

∙ If the following metadata exists in the xml, 3rd

store Deeplink information will be considered

to be included.

* <tizen:metadata key="master_app_3rd_url_deeplink" value="[3rd Store deeplink URL]"/>

26

2) Precautions for Binary Registration

A. Tizen Gear Binary Criteria

- If Standalone or Linked (Wearable) is selected in [4. Enter Application Information > 2) Binary Menu > A.

Gear App Type], you can only register .wgt and .tpk.

- Linked (Wearable) binaries must include the Deeplink information of Linked (Host) binaries.

- If the binary is Integrated or Linked (Follower), meta information must be included after the manifest.

<meta-data android:name=" GearAppType" android:value="wgt”/>

<uses-permission android:name="com.samsung.wmanager.APP"/>

B. Application Version Management

- Binary versions must meet the requirements below, in comparison with previously registered versions.

∙ Different binaries must have different versions.

∙ If the value of MinSdkVersion or MaxSdkVersion is smaller than 1, the binary cannot be registered.

∙ If the value of MinSdkVersion or MaxSdkVersion is bigger than the allowed limit, the binary cannot be

registered.

- Versions of the applications that were deleted during registration or certification evaluation, or that have been

withdrawn from sale can be used again.

C. Criteria for Binary Display in the Store

- The binary will be only shown on the devices that support the API Level (OS version) between the

MinSdkVersion value and the MaxSdkVersion value.

- If multiple binaries support a device's API Level (OS version), the binary of the highest version will be shown.

D. Management of App ID & Package ID

- All binaries registered in an application must have the same App ID. When they are re-registered or updated,

the same App ID must be used.

- The App ID of other applications cannot be used, but that of those that have been deleted or withdrawn from

sale can be used.

E. Signing Key Management

- All binaries must include a Signing Key. Those that include a Test Signing Key may be rejected during

registration or their sale may be terminated.

- All binaries registered in an application must have the same Signing Key. When they are re-registered or

updated, the same Signing Key must be used.

application registration guide - samsung...

Documents