Vous êtes sur la page 1sur 78

Samsung GALAXY Apps

Application Registration Guide













Media Solution Center
Samsung Electronics



"
!
Application Registration Guide

Index

#$ %&'&() *'+),-./ 0 1&,+2') 3+452+5& .......................................................................................... 5
#6 %&'&() *'+),-./ ...................................................................................................................... 5
76 %&'&() 1&,+2') 3+452+5& ...................................................................................................... 5
7$ 8&59:)&. ;4<.-9< 0 =&+. ;>>'9(+)9-4:........................................................................................ 6
#6 ?4)&. @4,-./+)9-4 ,-. 3AB C&42 .......................................................................................... 6
;$ @4>2) =29<& ..................................................................................................................... 6
B$ ;>> @4,-./+)9-4 ............................................................................................................. 9
D$ B94+.E ............................................................................................................................ 16
1$ D-24).E 0 *.9(& ............................................................................................................ 21
?$ @4 ;>> *2.(F+:& .......................................................................................................... 28
G$ D&.)9,9(+)9-4 .................................................................................................................. 33
76 %+H& @4,-./+)9-4 94 &+(F 3AB C&42 ................................................................................. 34
I6 %2J/9) ;>>'9(+)9-4 .............................................................................................................. 35
;$ %2J/9) B2))-4 94 =.&E ................................................................................................. 35
B$ %2J/9) B2))-4 94 8&< .................................................................................................. 35
K6 1&,949)9-4 -, 9)&/: ,-. +2)- <&)&()9-4 +4< /+42+' 94>2) JE L% ..................................... 37
M6 L)F&. ;2)-N<&)&()&< @4,-./+)9-4 ,.-/ B94+.E.................................................................. 38
O6 1&,949)9-4 -, .2'&: ,-. H&.:9-4 /+4+5&/&4) 94 +>>'9(+)9-4 .............................................. 39
;$ P&.:9-4 &Q+/94+)9-4 RF&4 (F+45945 + J94+.E -. .&59:)&.945 + 4&R -4& ................ 39
B$ ;4<.-9< ......................................................................................................................... 39
S6 D.9)&.9+ ,-. <&)&./94945 =&+. 0 TALU ............................................................................... 39
;$ =&+. 7$V ........................................................................................................................ 39
B$ TALU #$V ...................................................................................................................... 39
W6 1&,949)9-4 -, /+>>945 ,-. <&H9(&:XJ94+.9&:....................................................................... 39
;$ %)-.& >-'9(E .................................................................................................................. 40
B$ %)+4<+.<: -, J94+.E /+>>945 94 )F& <&H9(& .............................................................. 40
D$ ?Q(&>)9-4: .................................................................................................................... 40
Y6 ;2)- 1&)&()9-4 94,-./+)9-4................................................................................................. 41
;$ P&.:9-4 .......................................................................................................................... 41
B$ P-@* ............................................................................................................................... 41
D$ =--5'& C-J9'& %&.H9(& ................................................................................................ 42
1$ Z&'&>F-4E ..................................................................................................................... 42
?$ AGD ............................................................................................................................... 43
G$ G+[&)-2(F ..................................................................................................................... 43

"
"
=$ Z-2(F%(.&&4 ................................................................................................................ 44
\$ =&+. 7$V ;>>'9(+)9-4.................................................................................................... 44
@$ D+/&.+ ]=&+.76 ........................................................................................................... 45
^$ =*% ]=&+.76 ................................................................................................................. 45
T$ A&)R-.[ ]=&+.76........................................................................................................... 45
3$ @.3?1 ]=&+.76 ............................................................................................................... 45
C$ %+/:245 1&H&'->&. %1T ]=+'+QE %>&(9+': G&+)2.&6 ............................................... 46
A$ %+/:245 @;* %1T ]=+'+QE %>&(9+': G&+)2.&6 ........................................................... 46
L$ % *&4 %1T ]=+'+QE %>&(9+': G&+)2.&6 ....................................................................... 46
*$ =.-2> *'+E %1T ]=+'+QE %>&(9+': G&+)2.&6............................................................... 46
_$ % \&+')F %1T ]=+'+QE %>&(9+': G&+)2.&6 ................................................................... 46
8$ %/+.) D-44&()9H9)E %1T ]=+'+QE %>&(9+': G&+)2.&6 ................................................. 47
%$ C2:9( %)2<9- ;*@ ]=+'+QE %>&(9+': G&+)2.&6 ............................................................. 47
I$ J+<+ ;>>'9(+)9-4 8&59:).+)9-4................................................................................................... 47
#6 %)&># N B+:9( @4,-./+)9-4 .................................................................................................. 47
;$ ;>>'9(+)9-4 Z9)'& ........................................................................................................... 48
B$ D-4)&4) )E>&................................................................................................................. 48
D$ B94+.E G9'& ..................................................................................................................... 48
1$ B94+.E `>'-+<............................................................................................................... 50
?$ 1&H9(& @4,-./+)9-4 ...................................................................................................... 52
G$ 1&)+9'&< 1&H9(& %&))945: ............................................................................................. 52
=$ @4 ;>> ;<...................................................................................................................... 54
\$ %+'&: ............................................................................................................................. 54
@$ 1&)+9'&< D-24).E 0 *.9(& %&))945: .............................................................................. 55
^$ 18C .............................................................................................................................. 59
T$ D+)&5-.E ....................................................................................................................... 59
3$ *-94): )- (F&([ +,)&. )F& :)&> # -, )F& +>>'9(+)9-4 .&59:).+)9-4 .............................. 60
76 %)&> 7 N 19:>'+E @4,-./+)9-4 .............................................................................................. 60
;$ 1&:(.9>)9-4 ................................................................................................................... 61
B$ A&R ,&+)2.&: ................................................................................................................ 61
D$ Z+5: .............................................................................................................................. 61
1$ @(-4 @/+5& ................................................................................................................... 61
?$ %(.&&4:F-): ................................................................................................................. 62
G$ %2>>-.)&< 3+452+5& ................................................................................................... 62
=$ ;<<9)9-4+' 3+452+5& .................................................................................................... 62
\$ %2>>-.) ......................................................................................................................... 64
@$ D&.)9,9(+)9-4 .................................................................................................................. 65
I6 %)&> I G94+' 8&H9&R ......................................................................................................... 66
K6 %)&> K D-/>'&)& .............................................................................................................. 67
M6 1&,949)9-4 -, 9)&/: ,-. +2)- <&)&()9-4 +4< /+42+' 94>2) JE L% ..................................... 67
O6 1&,949)9-4 -4 1&H9(& 8&(-//&4<+)9-4 D.9)&.9+ ................................................................ 68
S6 1&,949)9-4 -, .2'&: ,-. H&.:9-4 /+4+5&/&4) 94 +>>'9(+)9-4 .............................................. 68

"
#
;$ P&.:9-4 &Q+/94+)9-4 RF&4 (F+45945 + J94+.E -. .&59:)&.945 + 4&R -4& ................ 69
B$ J+<+ .............................................................................................................................. 69
W6 1&,949)9-4 -, /+>>945 ,-. <&H9(&:XJ94+.9&:....................................................................... 69
D$ %)-.& >-'9(E .................................................................................................................. 69
1$ %)+4<+.<: -, J94+.E /+>>945 94 )F& <&H9(& .............................................................. 70
?$ ?Q(&>)9-4: .................................................................................................................... 70
Y6 ;2)- 1&)&()9-4 94,-./+)9-4................................................................................................. 71
G$ P&.:9-4 .......................................................................................................................... 71
=$ P-@* ............................................................................................................................... 71
\$ Z&'&>F-4E ..................................................................................................................... 71
@$ AGD ............................................................................................................................... 72
^$ G+[&)-2(F ..................................................................................................................... 73
T$ =.-2> *'+E .................................................................................................................... 73
3$ Z-2(F:(.&&4 ................................................................................................................ 73
K$ J+<+ ;>>'9(+)9-4 1&H&'->/&4) *.-(&<2.&: ............................................................................ 75
#6 1&H&'->&. %9)& a 8&59:)&. +>>'9(+)9-4 <&H&'->/&4) 94,-./+)9-4 ..................................... 75
;$ 8&59:).+)9-4 >.-(&<2.& ................................................................................................ 75
B$ %)+4<+.<: ,-. /+4+5945 /+94,&:)$Q/' <&>&4<945 -4 :)+)2: -, .&59:).+)9-4 ,-.
J+<+ +>>'9(+)9-4 -4 %&''&. L,,9(& ...................................................................................... 75
76 @1? +4< %1Ta ;>>'9(+)9-4 <&H&'->/&4) ............................................................................ 76
M$ %&(2.9)E Z&:) .............................................................................................................................. 77
O$ ;>>'9(+)9-4 D&.)9,9(+)9-4 ............................................................................................................ 77



"
$
1. Select Platform & Default Language

1) Select Platform


N Please select a platform to register applications.
N When selecting Android or Gear, refer to 2. Register Android & Gear Applications, or refer
to 3. Register bada Applications when selecting bada.

2) Select Default Language

N If you selected the Android or Gear platform, you must select a language as the default
language.

"
%
N Select a language from the Default Language selection box and click [Next].

2. Register Android & Gear Applications

1) Enter Information for LNB Menu

A. Input Guide

Here are the 6 essential guidelines for easy registration of applications. Please read
them in advance to register your application easily.



You can enter whichever information you want to enter first.

"
&
Select a desired menu from the LNB menu and start entering information. For
example, you can register an application title or save information such as
distribution country before registering a binary file.

The bottom tip provides information required for input.
For each field, information helpful for input will be displayed in the bottom tip
section. If you have any questions regarding your input, see the tip section for
help. If no tip is displayed, click (2-1) or change the Show Tip at the top to
On. For example, if you want to know how to enter an application title, check (2-2)
at the bottom.



In Simple Mode, you can only enter required information.

"
'
If you do not wish to enter details, you can simply click [Switch to Simple Mode].
To enter detailed information, you can click [Switch to Advanced Mode] and
continue your registration. For example, you can just click [Switch to Simple Mode]
if you do not wish to enter non-required details such as YouTube URL.

If there is an error in the input, you will be notified immediately.
If there is a problem in any part of the input, an alert message will appear in red at
the bottom. If you see this message, modify the information accordingly. For
example, if the entered application title is already in use, an alert message that
says the title is already in use will appear when you move the mouse.



You can save even if you do not fill in all of the fields.
You can save information without filling in the fields you are not certain about or

"
(
have a hard time answering. Enter whatever information you can and click [Save].
For example, if the application title is the only thing you are sure about now, just
enter the application title and click [Save]. However, if the entered information has
an error when you click [Save], an alert message will appear in red and the
information will not be saved. For details about the [Save] button, refer to 2) Save
from Each LNB Menu.

You can tell by the status of the [Submit] button whether the information
can be submitted.
If the [Submit] button is grey, the information cannot be submitted because the
required fields have not been filled in. If you click the button, you can check a list
of the required fields that have not been filled in.
If the [Submit] button is red, the information can be submitted because all of the
required fields have been filled in. Click the button to submit your application.
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.
For details about the [Submit] button, refer to 3) Submit Entered Information.

B. App Information

Set Additional Languages


- When you first enter the App Information tab, the default language selected in
the platform pop-up window and the [AddLanguage] button are displayed at the
top. The name of the default language will be followed by "(Default)"
- If you added an additional language by clicking the [Add Language] button, the
[Select Language] box and the [Change Default Language] button will be
displayed.
- Click a desired language in [Select Language] and the name of the left language
tab will change to the selected language and fields for input will be provided
below.
- If you want to delete one of the added languages, click [Select Language] and
click [X]. Please note that the default language cannot be deleted.
- The input fields displayed for the additional language are as follows.
: Application Title (required field)

"
)*
: Linked (Master) Application Title (displayed for Linked Gear applications/
required field)
: Description (required field)
: New Feature (in Advanced Mode while in revision)
: Tags (in Advanced Mode)
: Screenshots
- Input standard for each field is the same as that of the default language.

Application Title (required field)

- You can enter up to 200 bytes as application title.
- The following will be checked to prevent duplicate application titles.
: You cannot use any application titles already registered by other sellers.
: You cannot use the title of your other application designed for the same type
of devices as the application you are currently registering.
: If an application has been deleted or its sales has been cancelled, you can
use its title.

Linked (Master) Application Title (required field)

- If you selected Linked (Follower) as Gear application type from the binary menu,
you must enter Linked (Master) application title.
- If you entered app information before a binary, the system will think required
fields are left blank and the [Submit] button will be shown in grey. If this happens,
please go to the App Information menu and fill in this field.

Description (required field)

"
))

- Please enter a description of your application. You can enter up to 4000 bytes.
- If you are selling your application in 2 or more countries, you must enter the
description of your application in English.
- For Linked (Follower) Gear applications, make sure to note in the description
that an interworking application must be installed in the user's mobile device for
this application to work.

New Feature

- If you are modifying your application, please enter the updated details. You can
enter up to 4000 bytes.
- You can see the entered description in the buyer channel.

Tags

- You can enter up to 15 tags. If you click [+], the number of tags fields will
increase up to 15 one by one.

Icon (required field)

"
)!

- You can register an icon image in two different ways.
: Find a file to register by clicking the grey section.
: Drag and drop an image file into the grey section.
(Please note that the drag & drop function is not supported in some
browsers.)
- Requirements for the icon image file are as follows.
: 512 X 512 pixels
: Less than 1024 kb in size
: PNG file

Screenshots (required field)

- You can register a screenshot image in two different ways.
: Find a file to register by clicking the grey section.
: Drag and drop an image file into the grey section.
(Please note that the drag & drop function is not supported in some browsers.)
- Requirements for the screenshot image file are as follows. JPG or PNG file
: Minimum length: 320 pixels, maximum length: 3840 pixels
: Image ratio 2:1
: You must register at least 4 images and you can register up to 8.

Category (required field)

"
)"

- Categories can be divided into general categories and For Galaxy categories,
and the For Galaxy categories are divided into upper and lower categories.
- Depending on platforms, binaries, permissions and more, the categories you
can select may vary.
- In For Galaxy category, you cannot select the same category more than once.

Age Restriction (required field)

- Select an age restriction rating. This age restriction system is based on
Samsung GALAXY Apps standard and selected age restriction rating will be
displayed by each countries age while distributing contents. Please refer to Age
Rating Guide document for different countries standards.

Kids Age Restriction (required field)

- This field is shown only when the Kids category has been selected. Select a
proper Kids age for the application.

Rating Certificate for Available Countries

"
)#

- An age restriction document is issued by an external organization the restriction.
Please upload any age restriction document, that you received from the particular
country, in the same way that you would upload an image format.
- Files in GIF, JPG, or PNG formats can be uploaded for images of certifications.
- See Age rating guide for details on age ratings such as ESRB, PEGI, GRB, or
MJ/DEJUS.
- Game applications
: If an application has an ESRB or PEGI certificate and age rating, it will be
assigned the corresponding MJ/DEJUS age rating (If attached, the MJ/DEJUS
certificate takes priority over the age ratings of ESRB, PEGI)
: If an application does not have either an MJ/DEJUS or an ESRB/PEGI
certificate, or the certificate is not attached even if the age rating is set, it will be
provided with an 18+ MJ/DEJUS rating. The age rating will be displayed as
18+ on the buyer screen.
: Both the age rating and the certificate of GRB must be registered to sell an
application with an 18+ rating in Korea. Otherwise, Korea will be excluded from
country for sale.

Support Language (required field)

- Check the languages supported by the application.

Open Source URL

"
)$

- If you used Open Source software, please enter the URL of your Open Source
License for legal notice.

"#$%&'( ")*$'( +,-

- If you have any privacy policy that requires a separate notification, please enter
its URL.
- If you selected the Kids category, you must enter the Privacy Policy URL. If not,
the category may change.

./ YouTube URL

- When you register a related YouTube URL, it will be displayed on the store.
- Please enter only the 11-digit video ID of the YouTube URL.

.0 Copyright Holder

- Enter the name of the person or company who holds the copyright for the
application.
- You can enter up to 100 bytes.
- If a company possesses the copyright, then the company name is appropriate,
and if it is held by an individual, please enter his/her name.
- If you enter the name of the copyright holder, the name will be displayed instead
of the seller's name.

"
)%

.1 Support E-mail (required field)

- Please enter an E-mail address to which users can send inquiries.

.2 Support URL

- If you have a support site, please enter its URL.

34 A-)9,E 8&:2')

- You can register up to 20 email addresses to which information about the status
changes of the application can be sent.

C. Binary

G Gear App Type (required field displayed when the Gear platform is selected)

- If you select Gear from the platform selection pop-up window, choose a Gear
app type.
- You can change Gear app types when registering a new application or re-
registering an existing one. But note that the binary information will be reset if you
do so.
- You cannot change Gear app types for updates.


"
)&
Binary List



- You can click [Add Binary] to upload a binary file.
- You can upload up to 10 binary files.
- When a binary file is uploaded, you can check the uploaded binary at the bottom.
- The number of the selected device(s) is the sum of device(s) set to all binaries
in the same application.

"
)'
- You can click the number of the selected device(s) to set supported devices.
- You can click [Check Compatibility of Non-recommended Devices] to find out
why certain devices are not recommended, for each binary file.
- If you wish to replace the uploaded binaries or revise resolution information,
click the edit button that looks like a pencil.
- Click the [X] button to delete binary files.
- If you click the name of a binary file, you can view details including device
recommendation for the binary, additional information, and resolution.
- Device recommendation and additional information are auto detected from
binaries, and you can refer to 4) Device Recommendation Information and 5)
Other Information from Binary for details.
- Binaries in the same application can be configured for multiple devices.
- Each binary status icon refers to the following.
: Registering: Appears when a binary is changed or a new application is being
registered (if a binary with complete certification, failed certification, or a binary
on sale is changed, the status is changed to "In registration".)
: Passed: Appears when the binary is certified.
: Rejected: Appears when the binary cannot be certified.
: On sale: Appears when the binary is included in an application on sale.

Binary Upload (required field)

- Click the [Add Binary] button to select a resolution and upload a binary file.
- (Resolution) You can select multiple resolutions. To modify resolution when
updating, you must upload a new binary file.
- (Resolution) The Gear Application can be configured only when the Gear App

"
)(
Type is Integrated.
- (Version) The version of Android your application uses is shown as the
VersionCode and it is automatically detected from the AndroidManifest.xml file.
VersionCode must be in integers and there should be no duplicates among
binaries.
- (Version) A version of an application that was deleted or removed from sales
during registration or certification can be used again.
- (Binary file) The name of a binary file must not contain spaces or special
characters. However, you can use the underscore, (_).
- (Binary file) You cannot use the name of a binary file more than once.
- (Upload) Click the [Cancel] button to cancel the process of file upload.
- (Upload) If you try to re-upload the same file after file uploading is interrupted, a
window where you can select Continue from the previous upload pops up and
you can continue to upload the file from the previous upload.
- (Upload) When a file is uploaded, API levels and versions of the binaries
registered for the same application are checked; please refer to (6) Version
Management Rules in Application for details on the version rules applied.
- (Gear binary upload) You cannot register a general binary after selecting the
Gear platform. In this case, all the binaries in the application must have the same
Gear App Type.
- (App ID) All binary files registered for an application must have the same App ID.
- (App ID) An App ID belonging to an application that was deleted or removed
from sales can be used again.
- (App ID) The same App ID must be used when re-registering or updating
binaries.
- (App ID) The App ID of a general application and that of a Tencent application
can overlap.
- (Signing Key) Android binaries must include a signing key.
- (Signing Key) All binaries registered for an application must have the same
signing key.
- (Signing Key) When updating or re-registering a binary, you must use the
signing key of the binary previously registered. (If the registered binary does not
have a signing key, the new binary to be added must not include a signing key.)

Detailed Device Setting Pop-up

"
!*

- When you click the number of the selected device(s) at the top of the binary list,
the [Detailed Device Setting] window will pop up.
- Based on the auto-detected information from binary uploading and manually
entered resolution, a list of all selectable devices will be provided.
- The same device list for the application will be provided, and the devices that
are not compatible with each binary will be deactivated.
- The device with the For Sale mark is the device set to the binary currently for
sale.
- You can select or unselect each check box to change devices to sell.
- The following devices cannot be selected.
: Duplicated devices found when verifying application titles
- When you change the device selection, make sure to click the [Save] button to
save the changes.
- (Gear Application) In Seller Office, the device you need to select when
registering a Gear application is called the Virtual Device Group.
- (Gear Application) For the Gear Application, all Gear devices are recommended
if Gear App Type is Linked(Follower) or Standalone, and some devices among
Gear devices are recommended according to the device recommendation
information if the type is Integrated.
- (Gear Application) The Virtual Device Group is named with a combination of
smartphone device name and gear-type device name.

"
!)
E.g.) Galaxy Note 3-Galaxy Gear: This is a name with the combination of
Smartphone "Galaxy Note 3" and watch-type device Galaxy Gear".
- (Gear Application) When you select Linked (Follower), you must select a virtual
device supported by Linked (Master).
- For details about the criteria of device recommendation, refer to 4) Device
Recommendation Information.

Pop-up window for checking compatibility of non-recommended devices

- You can compare a list of non-recommended devices and the registered binary
files to find out why certain devices are not recommended.
- Select a device group and a binary to check and then click the [Confirm] button.
Then the options that are not compatible with the binary will be displayed in red.
- If you wish to sell applications in a certain device group, check the options that
are not compatible with the group and make necessary corrections to the binary
file.

D. Country & Price

Price (required field)

- Select Free or Paid to indicate the type of your application. Free application
sellers can sell free applications only.
- If you want to charge for your product, you need to submit a Commercial Seller
Request. Click the [Go] button below to do so.
- If you switch between Free and Paid, the distribution country and price

"
!!
information will be reset.
- If Paid is selected, you must enter the standard price below. Enter the standard
price and click the [Apply] button.
- (Standard price policy) The price will be based in USD.
- (Standard price policy) When you click the [Apply] button, the local price for
each country, based on the exchange rate of the day, will apply automatically.

Payment Method

- In Advanced Mode, you can select a payment method for paid applications.
- Credit card and phone bill payment are the default methods of payment.
- If China is selected as a sales country, cyber-cash and prepaid card will be
added as default methods of payment.
- If Korea is selected as a sales country, micropayment will be added as a default
method of payment.
- If Russia is selected as a sales country, Qiwi will be added as a default method
of payment.
- If Japan is selected as a sales country and credit card is available as a payment
option, WebMoney will be added as a default method of payment.
- If the UK, France, Germany, Italy, Spain, Australia, Singapore, or Malaysia is
selected as a sales country and credit card is available as a payment option,
PayPal will be added as a default method of payment.

Country Settings

"
!"

- All countries displayed on the country list are selected by default.
- In the below cases, the countries will not be displayed on the list automatically
or excluded from the distribution countries in the stage of application submission.
: If Paid is selected, countries in Free Only Group will not be displayed.
: If the US is selected as a seller country, Iran will not be displayed.
: ([Submit] Exclusion of distribution countries) If the age rating is set as
18+ Saudi Arabia will be excluded.
: ([Submit] Exclusion of distribution countries) For game applications with
the GRB age rating of 18+ for which no GRB certificate is registered,

"
!#
Korea will be excluded.
: ([Submit] Exclusion of distribution countries) If there is at least one
binary with GMS=YES, China will be excluded.
: ([Submit] Exclusion of distribution countries) If there is at least one
binary with VOIP=YES, countries in Free Only Group will be excluded.
: ([Submit] Exclusion of distribution countries) If the App ID overlaps with
that of a Tencent application, China will be excluded.
: ([Submit] Exclusion of distribution countries) If IAP is set, countries in
Free Only Group will be excluded.
: ([Submit] Exclusion of distribution countries)
If the application is an IAP application with item mapping information
/the binary Plasma version is 1.0 or lower: Korea and China will be
excluded.
/the binary Plasma version is lower than 1.8: countries in the PSMS Only
Tier will be excluded.
/the binary Plasma version is lower than 2.0: the US will be excluded.
/the binary Plasma version is lower than 1.9: Korea will be excluded.
- If you select the check box at the top of country list and add a service country
later, the application will be sold in the added country automatically.
: For paid applications, if a new paid country is added
(The price of the application will be determined by applying the exchange
rate of the distribution day to the standard price.)
: For free applications, if a new free or paid country is added

Free Only Group Settings

"
!$

- If you select Free, the free only group will be added to the default country group.
- You can select or unselect a country for distribution.
- Default country group: Europe / CIS / Asia Pacific / America / Middle East &
Africa / Global A
- Free Only Group: PanLatin / Pan-Arab / Pan-Africa / Global Free

Paid country and price settings

"
!%

- For paid applications, you can select sales countries and set price for each
country. See below to learn more about the settings and the policy.
- (Price per country) If you enter a USD standard price and click the [Apply] button,
the price for each country will apply automatically according to the exchange
rates. However, if the price automatically applied is less than the minimum
payment price for the country, the minimum price for the supported payment

"
!&
option will be used to set the price.
- (Price per country) Sellers can manually change the auto-applied price for each
country. To change the price of a country, select its price input field and enter a
desired price. Please note that the standard price will not change according to the
changed price for the country.
- (Price per country) The minimum price unit and the allowed minimum price may
vary for each country.
- (Price per country) If Korea is selected as a sales country, a minimum of 310
won must be set with the increment of 10 won.
- (Phone bill price) For phone bill payment, most countries have a fixed
price. If you select [Phone Bill] with * in the image at the top, the phone bill
price allowed will be shown in the selection box.
- (Phone bill price) Even if you select 'Phone Bill' as the payment method,
no phone bill price allowed is recommended by default.
- (Phone bill price) If a phone bill price is set for each country, the manual
input field will change to a selection box.
- (Phone bill price) If a phone bill price is recommended, the phone bill price
closest to the standard price will be set as default. You can change the price
in the selection box if desired.
- (Phone bill price) If no phone bill price is set for each country, the manual
input field will be provided as usual and you can manually enter a desired
price.
- (Phone bill display price) For the countries such as Russia and Belarus where
phone bill prices differ by carrier, the phone bill prices will be divided into price
tiers. The main price of a price tier is called the display price and it is the highest
price in the price tier.
- (Phone bill display price) In the above case, the display price is displayed in the
selection box of price for each country, and the display price is also displayed on
the buyer screen.
- (Phone bill display price) If you wish to find detailed price information for each
country, you can click the [Carrier Prices] button in the country section.

Selling Starts

- Select a date when you want to start selling the application.
- You can click the calendar icon to select a certain date.

"
!'
- If you wish to start selling automatically upon application approval without
selecting a certain date, you can select the check box on the right.

Selling Ends

- Select a date when you want to end the selling of the application.
- You can click the calendar icon to select a certain date.
- If you do not wish to specify a date, you can click the selection box on the right.

E. In App Purchase

In App Purchase (IAP) Policy
- Applications with IAP configured can be distributed only in countries with paid
sales contracts.
- For countries with free service, the applications with IAP configured will be
distributed when the paid service becomes available.
- An Item Group set to applications cannot be modified. However, if a binary is
changed by adding a new application or re-registering an application, the Item
Group configuration will be reset.
- When you register, add, or change an Android binary set with IAP SDK, binary
upload may be restricted depending on the SDK version.
- You can always modify the Item information mapped to applications. However,
Item Add/Delete can be done while Registering/Updating applications.
- If there is Item mapping information in Android applications like in the cases
below, certain countries will be excluded automatically in the [Submit] step in red.
: the binary Plasma version is 1.0 or lower: Korea and China will be excluded.
: the binary Plasma version is lower than 1.8: countries in the PSMS Only Tier
will be excluded.
: the binary Plasma version is lower than 2.0: the US will be excluded.
: the binary Plasma version is lower than 1.9: Korea will be excluded.

If In App Purchase cannot be registered

"
!(

- In the cases below, IAP cannot be registered and the above alert page will be
provided.
: If you are a seller of free applications
: If there is no binary registered
: If a binary which does not support IAP is registered (all registered binaries
must support IAP)
: If the application is a Gear application
: If the application is a KNOX 2.0 application

In App Purchase List

- If you upload a binary that supports IAP, this list will be enabled and an item
group ID and item group title will be provided automatically.
- The item group ID cannot be changed.
- The item group title can be changed and it can be identical to the title of another
item group.
- If the Item Group ID is shown in the selection box, the Item Group which is set to
the application with the same App ID (Package Name) will be loaded.
- If you click [Add Item], a window where you can add an item will pop up.

"
"*
- If you click [Item Bulk Upload] and upload an Excel form, you can register items
in bulk.
- If you click each item title, a window where you can update an item
will pop up.
- Click the [X] button to delete an individual item.

Add Item / Update Pop-up

- In this pop-up window, you can create or update an item with the same item
group ID.
- Like other LNB menus, you can enter information in either Simple Mode or
Advanced Mode.
- Two duplicate item IDs cannot be used under the same item group ID. After
entering information, make sure to click the [Check] button.
- When you are updating an item, you cannot change its Item ID. Please be sure
of what you are entering the first time you enter an Item ID.
- Item types are categorized into Consumable, Non-Consumable, and

"
")
Subscription. Note that you cannot change item types in the stage of review or
update. Consumable items can only be used once. After being used, they
disappear just like coins in a game. Non-consumable items can be recovered
even if the application gets deleted and re-installed (can only be purchased once).
A subscription offers items regularly after one-time payment (items offered on a
monthly basis). Subscriptions can be recovered in the same way as non-
consumable items.
- Duration appears only when Subscription is selected as the item type and it
cannot be edited in the review or update stage.


"
"!

- For details about payment methods and price settings, refer to D. Country &
Price.
- After you fill in all fields, click the [Save] button.

Item Bulk Upload

"
""

- If you click [Item Bulk Upload] from the IAP list, the above window will pop up.
- Click [Download Excel Form] to download the file and enter required information.
If you upload a self-created Excel file, information in the file will not apply.
- If you upload a complete Excel file, you will see an item added to the list.

F. Certification

Comments to the Certification Team

- Enter comments to be referred to at certification evaluation.
- The following information must be listed in order to pass the certificate
evaluation: Login, Temporary Login ID, Password, Fake card number for testing
purposes. Failure to comply can result in denial of certification.
- Unnecessary QA failures can be prevented by providing the concept of the app,
self-test results, and by noting any precautions we should take while testing the
app. If an app is re-submitted after update or QA failure, please note all of the
changes made from previous version.

Attach Materials for Requesting Certification

- For certification, you can attach a file less than 1 MB for reference.

"
"#


Attach the Result of Self Testing

- You can register a Self-checklist, which developers can then use to test the
application before registering it.

Video Link for Certification Review Reference

- For certification, you can attach a video link for reference.

2) Save Information in each LNB Menu

[Save] is located both at the top and at the bottom of each LNB menu. You can
click this button anytime after filling in one field. Please use this [Save] button
often to prevent any loss of information due to unexpected errors. When you are
finished entering information, make sure to click the [Save] button.

If the entered information has an error when you click [Save], an alert message
will appear in red at the bottom. Please check the message and make necessary
corrections.

When all the required fields are saved without an error, the grey icon of App
Information / Binary / Country & Price will turn green and you can submit the
application. For details about application submission, refer to 3) Submit
Application.

Please note that you must enter the name of the Linked (Master) application if
you selected Linked as the Gear App type of the binary menu. In this case, the
green icon of App Information will turn into grey when you save the binary menu.
So you need to access it again to fill in fields again.


"
"$
3) Submit Application

A. Submit Button in Grey



If any of the required fields in App information / Binary / Country & Price is blank,
the Submit button will remain grey.

If you click the grey button, a window for the grey button shown in 3 below will
pop up and you can see a list of the required fields left blank.

Pop-up window for the gray Submit button

- You can view all fields left blank in each menu and you can click each field to
open it.

If you fill in the blank fields and save the information, the button will turn red.

B. Submit Button in Red


"
"%

When all the required fields for the application submission are saved, the button
turns red.

When you click the red Submit button, compatibility and consistency of each field
will be checked. Some information may become automatically excluded or you
may need to make some corrections.

When application submission continues

- If you click the red Submit button, a window pops up and asks if you wish to
continue with the submission. Here you can decide once again whether to submit
the application or not.
- If you continue with the submission, the pre-certification process will begin and
the application's status will be displayed as 'Pre-Certification' in My Application.
However, if you did not change the binary when re-registering or updating the
application, no pre-certification process will begin and you can check the progress
in Certification Status of My Application.

When application submission does not continue

- If you click the red Submit button, an alert window will pop up with information
appropriate for your application.
- In some cases, it contains changed information (e.g. distribution country), and

"
"&
you can submit the application only if you agree to the change.
- In other cases, it shows you what information you need to modify. After checking
the information, you can close it.
- After reading the content of the pop-up window and making necessary
corrections, click the red Submit button.

4) Definition of items for auto detection and manual input by OS

Type Field
Default Value
Recommendations
Binary Auto Detection
Telephony
(Call/SMS)
3G only is disabled.
If No is selected, all devices are
recommended.
If Yes is selected, only the devices with
the function are recommended.
Disabled by default if there is no
configuration in the manifest.
NFC
Disabled
If No is selected, all devices are
recommended.
If Yes is selected, only the devices with
the function are recommended.
Disabled by default if there is no
configuration in the manifest.

Faketouch
Disabled
If Touchscreen is disabled, Faketouch
is enabled.
If Enable is set, only Homesync
devices are recommended.
If Disable is set, all devices are
recommended.
If there is no configuration in the
Manifest, Disable is set by default.
TouchScreen
Enabled
If Enable is set, exclude devices that
do not support Touchscreen.
If Disable is set, recommend devices
are enabled with Faketouch.
If there is no configuration in the
Manifest, Enable is set by default.
Camera(Gear2)
Disabled (Displayed only for Gear 2.0)
If No is selected, all devices are
recommended.
If Yes is selected, only the devices with
the function are recommended.
Disabled by default if there is no
configuration in the manifest.
GPS(Gear2) Disabled (Displayed only for Gear 2.0)

"
"'
If No is selected, all devices are
recommended.
If Yes is selected, only the devices with
the function are recommended.
Disabled by default if there is no
configuration in the manifest.
Network(Gear2)
Disabled (Displayed only for Gear 2.0)
Network: 2G/3G/Wi-Fi
If No is selected, all devices are
recommended.
If Yes is selected, only the devices with
the function are recommended.
Disabled by default if there is no
configuration in the manifest.
IrLED(Gear2)
Disabled (Displayed only for Gear 2.0)
If No is selected, all devices are
recommended.
If Yes is selected, only the devices with
the function are recommended.
Disabled by default if there is no
configuration in the manifest.
Manual input Resolution(s)
Use a manual input value.
If multiple resolutions are selected, all
corresponding devices are
recommended.


5) Other Auto-detected Information from Binary

Type Field Description
Basic information
API
Configure it to support all API Levels
(API Level 1).
Length: 10
App ID(Package Name)* !"#$%&: 256
Version Code*
Binary version
Length: 1000, Format: Numbers
Version Name*
The value is used for display in the
store. There is no validity test when
uploading.
Length: 20, Format: No limit
Galaxy Specials
information
: If you select the Galaxy
Specials category, you can
register your application
when there is 1 or more of
the 7 features in the binary.
Samsung developer SDK
If there is no configuration in Manifest, it
is recognized as Disable.
Samsung IAP SDK
S Pen SDK
Group Play SDK
S Health SDK
Smart Connectivity SDK

"
"(
Music Studio API
Additional information
VoIP
If there is no configuration in Manifest, it
is recognized as Disable.
Google Mobile Service
('*' is a manifest or config file for required definitions.)

6) Definition of rules for version management in application

A. Version examination when changing a binary or registering a new one

The version of a new binary must meet the following requirements in comparison with
any binaries previously registered (including the binary being replaced).

B. Android

The Version Code must be an integer.
The Version Code for each binary must be different.
Registration cannot be processed if the value for MinSdkVersion or
MaxSdkVersion is less than 1.
Registration cannot be processed if the value for MinSdkVersion or
MaxSdkVersion is higher than the allowed limits.

7) Criteria for determining Gear & KNOX

A. Gear 2.0

The Standalone Gear binary uses the .wgt file format.
The manifest file in the Gear binary of the Integrated and Linked (Follower) types
includes the following meta information:
<meta-data android:name=" GearAppType" android:value="wgt/>
<uses-permission android:name="com.samsung.wmanager.APP"/>

B. KNOX 1.0

Manifest in the Android binary must include the KNOX 1.0 identifier.

8) Definition of mapping for devices/binaries


"
#*
A. Store policy

Only apk files suitable for the user device environment will be displayed.
If you change a device, you can download an application with a different binary
(apk) for the device with the same content/product ID.
If multiple binaries are mapped to a device, multiple registrations are allowed and
you can download a binary compatible with the OS version on your device. Also,
if there are multiple OSs with the same version, a binary with the highest Version
Code will be downloaded.
If an application is registered for a specific device, but the OS version of the user
device is not compatible with the API level of the binary, the application may not
be displayed in the device's store.
In the event when 'MinSdkVersion=9 and MaxSdkVersion=14' :
b Download is available for Gingerbread devices which have API Level 9
b The store cannot be displayed on Froyo devices which have API Level 8
(filtered)
b The store cannot be displayed on Icecream Sandwich MR1 devices which
have API Level 15 (filtered)

B. Standards of binary mapping in the device

N Version of the devices OS = supported API Level.
A binary corresponding to the version of the devices OS is mapped.
If there are multiple binaries corresponding to the version of the devices OS, the
one with the highest Version Code will be mapped.

N Version of the devices OS < supported API Level
Product is not displayed in the store for the users device (filtering)

N Version of the devices OS > supported API Level (if a MaxSdkVersion value
exists)
Product is not displayed in the store for the users device (filtering)

C. Exceptions

If all the following criteria are met, a device cannot be registered for multiple binaries.

If the range of API Level available for support is the same or included in the range
of other binaries.

"
#)
b Example: Binary A supports API Level 7-15, but binary B supports API Level
8-14.
If all configured devices are included in, or are the same as the device list of
another binary.
b Example: Binary A supports devices 1,2, and 3, but binary B supports
devices 1 and 2.
If the Version Code is lower than that of the binary
b Example 1. The Version Code of binary A is 2, and that of binary B is 1.
b Example 2. Binary A supports API Level 7-15, but binary B supports API
Level 8-14 and if all devices configured for binary B are included in binary A,
binary B cannot be registered because the Version Code is lower.

9) Auto Detection information

A. Version

Samsung Apps uses the Version Code listed in manifest.xml.
b <manifest xmlns:android="http://schemas.android.com/apk/res/android
android:versionCode="2 android:versionName="1.0.0.1 package="package
.name.sample"
The Version Name is the Version of the application that is displayed to buyers on
the channel.

B. VoIP
If any of the following uses-feature cases exists in the manifest, the application is
considered to support VOIP.
b <uses-feature android:name="android.software.sip.voip"
android:required="true"/>
b <uses-feature android:name="android.software.sip.voip"/>
b <uses-feature android:name="android.hardware.sip.voip"
android:required="true"/>
b <uses-feature android:name="android.hardware.sip.voip"/>
If uses-feature required = "false", the application is considered not to support
VOIP.
b <uses-feature android:name="android.software.sip.voip"
android:required="false"/>
b <uses-feature android:name="android.hardware.sip.voip"
android:required="false"/>


"
#!
C. Google Mobile Service

- If the following meta-data exists in the manifest file, the application is considered to
support Google Mobile Service.
* <meta-data android:name="com.google.android.gms.version"
android:value="@integer/google_play_services_version"/>

- If a meat-data is not listed in the manifest, the application is considered to not use
Google Mobile Service.

D. Telephony

N For the following cases, the application is considered to support Telephony..
If any of uses-feature cases exists in the manifest
b <uses-feature android:name="android.hardware.telephony"
android:required="true"/>
b <uses-feature android:name="android.hardware.telephony"/>
b <uses-feature android:name="android.hardware.telephony.cdma"
android:required="true"/>
b <uses-feature android:name="android.hardware.telephony.cdma"/>
b <uses-feature android:name="android.hardware.telephony.gsm"
android:required="true"/>
b <uses-feature android:name="android.hardware.telephony.gsm"/>
If any of uses-permission exists in the manifest
b <uses-permission android:name="android.permission.CALL_PHONE" />
b <uses-permission android:name="android.permission.CALL_PRIVILEGED"
/>
b <uses-permission
android:name="android.permission.MODIFY_PHONE_STATE" />
b <uses-permission
android:name="android.permission.PROCESS_OUTGOING_CALLS" />
b <uses-permission android:name="android.permission.READ_SMS" />
b <uses-permission android:name="android.permission.RECEIVE_SMS" />
b <uses-permission android:name="android.permission.RECEIVE_MMS" />
b <uses-permission
android:name="android.permission.RECEIVE_WAP_PUSH" />
b <uses-permission android:name="android.permission.SEND_SMS" />
b <uses-permission
android:name="android.permission.WRITE_APN_SETTINGS" />

"
#"
b <uses-permission android:name="android.permission.WRITE_SMS" />

N For the following cases, the application is considered as not supporting Telephony.
If uses-feature required = "false": uses-feature has priority, even when the
Telephony permission exists. Therefore, the application is considered as not
supporting Telephony.
b <uses-feature android:name="android.hardware.telephony"
android:required="false"/>
b <uses-feature android:name="android.hardware.telephony.cdma"
android:required="false"/>
b <uses-feature android:name="android.hardware.telephony.gsm"
android:required="false"/>
If neither uses-feature case nor uses-permission exist in the manifest

E. NFC

N For the following cases, the application is considered to support NFC.
If any of uses-feature cases exists in the manifest.
b <uses-feature android:name="android.hardware.nfc"
android:required="true"/>
b <uses-feature android:name="android.hardware.nfc"/>
If a manifest exists in the uses-permission below
b <uses-permission android:name="android.permission.NFC"/>

N For the following cases, the application is considered not to support NFC.
If uses-feature required = "false" : uses-feature has priority, even when the NFC
permission exists. Therefore, the application is considered as not supporting NFC.
b <uses-feature android:name="android.hardware.nfc"
android:required="false"/>
If neither uses-feature case nor android.permission.NFC exist in the manifest

F. Faketouch
N For the following cases, the application is considered to support Faketouch.
* <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"/>

"
##

N For the following cases, the application is considered not to support Faketouch.
If 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"/>
If uses-feature case not exist in the manifest.

G. TouchScreen

For the following cases, the application is considered as using Touchscreen.
When one or more uses-feature cases exist 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 uses-feature case exists in the manifest
If the following uses-feature exists in the manifest, the application is considered
as using Touchscreen, but the use of it is not mandatory.
* <uses-feature android:name="android.hardware.touchscreen"
android:required="false"/>

H. Gear 2.0 Application

- If the following uses-permission exists in the manifest, the application is considered
to support the Gear 2.0 device.
* <uses-permission android:name="com.samsung.wmanager.APP"/>

"
#$
* <meta-data android:name=" GearAppType" android:value="wgt/>

I. Camera (Gear2)

- If the following feature exists in the manifest file, the application is considered to
support Camera.
* <Feature Name="http://tizen.org/feature/camera" />

- If a feature is not listed in the manifest, the application is considered to not use
Camera.

J. GPS (Gear2)

- If the following feature exists in the manifest file, the application is considered to
support GPS.
* <Feature Name="http://tizen.org/feature/location.gps" />

- If a feature is not listed in the manifest, the application is considered to not use GPS.

K. Network (Gear2)

- If one or more of the following features is listed in the manifest, the application is
considered to use Network.
* <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" />

- If a feature is not listed in the manifest, the application is considered to not use
Network.

L. IrLED (Gear2)

- If the following feature exists in the manifest file, the application is considered to
support IrLED.
* <Feature Name="http://developer.samsung.com/tizen/feature/irled"/>

- If a feature is not listed in the manifest, the application is considered to not use
IrLED.


"
#%
M. Samsung Developer SDK (Galaxy Specials Feature)

- If the following user-permission exists in the manifest file, it is considered that the
application uses Samsung Developer SDK.
* <uses-permission
android:name="com.samsung.android.providers.context.permission.WRITE_USE
_APP_FEATURE_SURVEY" />

- If the user-permission does not exist in the manifest file, it is considered that the
application does not use the Samsung Developer SDK.

N. Samsung IAP SDK (Galaxy Specials Feature)

- If the following user-permission exists in the manifest file, it is considered that the
application uses Samsung IAP SDK.
* <uses-permission android:name="com.sec.android.iap.permission.BILLING"/>

- If the user-permission does not exist in the manifest file, it is considered that the
application does not use the Samsung IAP SDK.

O. S Pen SDK (Galaxy Specials Feature)

- If the following uses-feature exists in the manifest file, it is considered that the
application uses S Pen SDK.
* <uses-feature name="com.sec.feature.spen_usp" android:required="true"/>

- If the uses-feature does not exist in the manifest, it is considered that the application
does not the S Pen SDK.

P. Group Play SDK (Galaxy Specials Feature)

- If the following meta-data exists in the manifest file, it is considered that the
application uses the Group Play SDK.
* <meta-data android:name="GroupPlay" android:value="true" />

- If the meta-data does not exist in the manifest file, it is considered that the
application does not use the Group Play SDK.

Q. S Health SDK (Galaxy Specials Feature)


"
#&
- If the following meta-data exists in the manifest file, it is considered that the
application uses the S Health SDK.
* <meta-data android:name="SHealth" android:value="true" />

- If the meta-data does not exist in the manifest file, it is considered that the
application does not use the S Health SDK.

R. Smart Connectivity SDK (Galaxy Specials Feature)

- If the following meta-data exists in the manifest file, it is considered that the
application uses the Smart Connectivity SDK.
* <meta-data android:name="SmartConnectivity" android:value="true" />

- If the meta-data does not exist in the manifest file, it is considered that the
application does not use the Smart Connectivity SDK.

S. Music Studio API (Galaxy Specials Feature)

- If the following meta-data exists in the manifest file, it is considered that the
application uses the Music Studio API.
* <meta-data android:name="ProfessionalAudio" android:value="true/>

- If the following meta-data does not exist in the manifest file, it is considered that the
application does not use the Music Studio API.

3. bada Application Registration

1) Step1 - Basic Information


"
#'


A. Application Title

Please enter an application title of under 100 bytes. Click the [Check] button to
check if the same application title is in use.
If the application title is already in use, the Application Title must be changed.
Devices with the same application title cannot be selected if the device is
duplicated.

N If an application title is duplicated
The application title can be used if it was previously registered by the same Seller
but for a different device.
The application title cannot be used if it was previously registered by another
Seller.
The application title can be used if the previous instance has been deleted or
cancelled from sales.

B. Content type

Select an available content type for each OS.
If you change the content type when registering new applications, all information,
including the OS, will be reset.
The Content type cannot be edited for re-registration or update.

C. Binary File


"
#(


Register binary file.
The application title, OS, and content type must be entered before you can
upload a binary file.
For bada and Android, you can upload up to 10 binary files to an application
(except other OSs and bada widgets)
When the binary is uploaded, the binary information will be created.
When the first binary is uploaded when registering a new application, a content ID
is created and the new application is added to the registration list. All binaries
uploaded thereafter, including the second binary, will be saved under the same
content ID.
Binaries in the same application can be configured for multiple devices.
Auto detection, manual input, resolution, etc, are displayed in Binary Details, but
you can only view the information, not edit it.
You can click the [Modify] button to change the binary file in a binary upload pop-
up window and modify information such as Resolution, Manual Input Details, and
Version.
You can toggle the [ + ] or [ - ] button to open or close the details section.
If you click the [Delete] button, the binary and the device information configured
for the binary will be deleted. If all registered binaries are deleted, the information
you have entered for sales will be reset.

N The binary status will be displayed as an icon for the following
Registering: Appears when a binary is changed or a new application is being
registered (if a binary with complete certification, failed certification, or a binary on
sale is changed, the status is changed to "In registration".)
Passed: Appears when the binary is certified.
Rejected: Appears when the binary cannot be certified.
On sale: Appears when the binary is included in an application on sale.

"
$*

N Version information by OS
bada: Version (auto detection)
See <"Definition of items for auto detection and manual input" by OS in 5.
Appendix> for details on binary version.

D. Binary Upload



Resolution and manual input cannot be edited when updating an application and
those can be edited only after the binary is changed.
You can use the [Save] function after you save the first binary when registering a
new application.

N Resolution
You can choose from multiple types of resolution and both numbers and English
characters are displayed.

N Manual Input Details
Can only be selected for bada or Android.

"
$)
If 'No' is selected in Manual Input Details, all devices are recommended. If 'Yes' is
selected, all devices using the function are recommended.
Can be selected for bada: VR, Camera Key, VoIP, NFC, Google Mobile Service
Google Mobile Service: Since the sale of applications containing services
provided by Google such as Google map, Gmail and Google Talk are prohibited
in China, China will be automatically excluded from target countries when Yes is
selected.

N Version
The AppVersion of applications for bada is automatically detected from the
manifest.xml file. AppVersion can only be set between 0.0.1 and 35.35.1295 and
it cannot be shared between binaries. A binary with a higher API Version must
have a higher value than one with a lower API Version.
The version information for widgets (Windows Mobile and bada) is extracted from
the config.xml file. Application version information can have up to 10 digits
including both numbers and dots. (e.g. 1.0.0.1)
If you change a binary when updating a bada application, the new binary version
must be higher than that of the previous one.
A version of an application that was deleted or removed from sales during
registration or certification can be used again.

N Binary file
Binary file name must not contain spaces or special characters. Special
characters except an underscore "_" cannot be used in a file name.
Two different binaries with the same name cannot be used in the same
application. However, the same binary name can be used for a different
application or Seller.
Using Progress Bar, you can check the progress of uploading an application file.
Click [Cancel] button to cancel the file upload.
When the binary is uploaded, all the API Levels and versions registered in one
application are verified and the version rules as shown in <hen the binary is
uploaded, all the API Levels and versions registered in> apply to the verification.
There is only a limit on the file size when uploading widgets (Uploaded widgets
(bada and Windows Mobile) can be up to 2 MB).

N The following file formats are available for uploading
bada: .zip (except widget)



"
$!
N Rules for applying an App ID
The same App ID can only be used multiple times within the same application.
(All binaries registered in the same application must have the same App ID.)
An App ID belonging to an application that was deleted or removed from sales
can be used again. (including App IDs from other Sellers)
The same App ID must be used when re-registering or updating binaries.
The App ID of the Tencent application can overlap with the IDs of general
applications.

N Rules for applying a signing key
The signing key of all binaries registered for the same application must be the
same.
If you update or re-register an application, you must register a binary with the
same signing key as previously.
(However, if the binary of the application previously registered does not have a
signing key, it must be added or replaced without a signing key.)

E. Device Information



When the binary is uploaded, the numbers of recommended devices and selected
devices are displayed in device information.
Number of recommended devices: total number of devices available for
configuration to all binaries.
Number of selected devices: total number of devices configured for all binaries in
the same application.
Integrated management of device settings is available from "Detailed Device
Settings".
Select the [Detailed Device Settings] button to view or change the device settings
and binary configurations.
See <"Definition on Device Recommendation Criteria" in 5. Appendix> for details
on device recommendation criteria.
Example of device recommendations: Devices which do not use Flash are
excluded from the recommended devices if the content type is Flash.

F. Detailed Device Settings

"
$"



In Detailed Device Settings, you can select multiple devices from the
recommended devices that are available for selection according to auto detection
or entered directly when the binary was uploaded.
Please note that the number of selected applications and the number of
applications for sale may be different depending on the result of application
certification.
Depending on the set device, the countries available for application sales are set
automatically.
The device list for the same application remains the same at all times and only
the devices available for each binary will be activated.
The devices configured for the binaries for sale will be marked with () when
updating applications.
You must click the [Save] button to save and apply the device settings after you
finish editing the device settings for a binary.

N The following devices cannot be selected.
Incompatible devices
Duplicated devices found when verifying application titles

N Example of device settings
If 10 devices are recommended when you register an application and you only
select 5 of them, then you can still add or remove devices from the list when

"
$#
revised after the start of sales (distribution).
If a device registered to an application for sale is deselected from the list while it's
being updated, users who have purchased the application for this device will not
be able to download the updated application.
The application can still be added to/removed from the 5 set devices if the
authentication is rejected before application sales begin.
If some devices are 'Rejected' without authentication, you can get approval by
registering again without those rejected devices.

G. In App Ad

In App Ad settings will be displayed for bada applications.
You may select to include advertisement content.

H. Sales



N Settings for free/paid
Please choose whether you are going to offer the App as a free or paid
application. If you are not a commercial seller, you can only offer free applications.
If a seller does not have Commercial Seller Status, he or she cannot select Paid
Application. A link to the commercial seller status page appears at the bottom of
the page.
Settings for free/paid can only be configured when a binary is registered.

"
$$
If you change the settings for free/paid, the country and price settings will be reset.
When the settings for free/paid are selected, the country available for the service
and the price for the country are applied.

N Set the price by sale period
It can only be configured when the content type is set as Native, Flash or Web
App and all binaries registered to the application are based on bada SDK 2.0.

N Payment Method
It can only be configured for paid applications when credit card and phone bill are
configured as the default method of payment.
Cyber cash and pre-paid card will be configured as the default methods of
payment if China is set as a country for sale.
Micropayment will be configured as the default method of payment if Korea is set
as a country for sale.

N Free Trial
It can only be configured when the content type is set as Native, Flash or Web
App and all binaries registered to the application are based on bada SDK 2.0.
The following ranges are available when setting the time period.
b Hours: 1 ~ 23
b Days: 1 ~ 31
b Weeks: 1 ~ 16
b Months: 1 ~ 12

N Selling Starts / Ends
Please enter the period to be displayed.
Click an icon from the calendar to select a date. When you check the box on the
right, the application will automatically be made available for sale from the
approval date. If no sales start date has been set, then the application will go on
sale as soon as the certification is complete.

N Please note that the information for sales will be reset in the following cases.
When a new binary is added
When a binary is deleted
When binary information is edited
When device information is edited

I. Detailed Country & Price Settings

"
$%

Click [Detailed Country & Price Settings] button to set the country of sale and the price.



N Country list
The list of all countries set for the device according to the binary configuration is
displayed.
All countries displayed are selected by default.

N The Free Only group is divided into the following regions and countries.
Pan-Latin
Pan-Arab
Pan-Africa
Global Free

N The country list will exclude the following cases.
When paid is selected: Free Only Group
If Google Mobile Service is set as Yes for any registered binary: China
If VoIP is set as Use for any registered binary: Free Only Group
For the following: Korea
- All bada paid applications
- bada applications with IAP configured

"
$&
If the App ID overlaps with that of the Tencent application (relevant in China only).

N Consent for the range of the Samsung GALAXY Apps service and country
expansion
When the number of paid countries is increased for paid applications
When the number of paid countries and selected countries in the Free Only
Group is increased for free applications.
The price based on the exchange rate on the day of release will apply when an
application is released for country expansion.

N Standard price
It is applied based on U.S. dollars (USD).
The standard price and the local price are displayed as 0 for free applications.
The minimum input unit and the minimum payment price are displayed in the local
currency by country.

N Local price
When you click the [Auto Input] button after you enter the standard price, the local
price is automatically applied for the country based on the exchange rate of the
day.
If the price from the automatic calculation is lower than the minimum price of
payment for the country, it will be automatically changed to the minimum price of
payment supported by the methods of payment for the country.
The local price for the country is the same regardless of the Payment Method.
The standard price remains the same even if the local price for the country is
changed.

N Phone Bill price
If the method of payment is set to Phone Bill, 'Apply Phone Bill Price' is used by
default.
In all countries where phone bill payment is available, you can click a selection
box to choose the phone bill price. All phone bill prices for the country are
displayed.
The phone bill price closest to the standard price is selected as the phone bill
recommendation price by default. If there are two prices equally close to the
standard price, the higher price will apply.
If you deselect Apply Phone Bill price, the selection box changes to an input
window and you can enter a price manually.


"
$'
N Phone Bill display price
The phone bill prices are displayed in Tiers for countries (e.g. Russia and Belarus)
which have different phone bill prices in that country depending on the carrier.
The display price is the main price in a price tier and it is the highest price in the
tier.
The display price is displayed in the selection box as the local phone bill price by
country. It is also displayed on the buyer screen.
You can click the [Carrier Prices] button to view the detailed price information.

N If Korea is set as a country for sale
Micropayment is set as a required method of payment.
The minimum price must be set as 310 won and you can change the price by a
difference of 10 won.

N Set the price by sale period



You can set the price by sale period if 'Yes is selected for Set the price by sale
period and it can be selected in the same way as a normal price setting.

"
$(
You can set three different prices and the period (day, week, month) can be
duplicated.

N Set the price by sale period cannot be configured in the following cases.
If only Permanent is set.
If both period units and numbers are duplicated.
If two periods are the same. (Example: if both 7 days and 1 week are configured.)
If the price set for a shorter period is higher than that of a longer period.

J. DRM



When you select to use bada, select whether to implement DRM or not.
If free trail are enabled, DRM is automatically applied.

K. Category



The 'Category' label defines the type of application. Category' consists of primary
and secondary items. You cannot select duplicate items. The category may be
changed when the application is actually displayed on the site, depending on the
results of the approval process.
Select an age restriction rating. This age restriction system is based on Samsung

"
%*
GALAXY Apps standard and selected age restriction rating will be displayed by
each countries age while distributing contents. Please refer to Certification Guide
document for different countries standards.
An age restriction document is issued by an external organization the restriction
will be approved so long as relevant documents are submitted. Please upload any
age restriction document, that you received from the particular country, in the
same way that you would upload an image format.
Files in GIF, JPG, or PNG formats can be uploaded for images of certifications.
See Age rating guide for details on age ratings such as ESRB, PEGI, GRB, or
MJ/DEJUS.

N Game applications
If an application has an ESRB or PEGI certificate and age rating, it will be
assigned the corresponding MJ/DEJUS age rating (If attached, the MJ/DEJUS
certificate takes priority over the age ratings of ESRB, PEGI)
If an application does not have either an MJ/DEJUS or an ESRB/PEGI certificate,
or the certificate is not attached even if the age rating is set, it will be provided
with an 18+ MJ/DEJUS rating. The age rating will be displayed as 18+ on the
buyer screen.
Both the age rating and the certificate of GRB must be registered to sell an
application with an 18+ rating in Korea. Otherwise, Korea will be excluded from
country for sale.

N Runs Offline
Runs Offline? Select either Stand-alone or Net-based to choose.

L. Points to check after the step 1 of the application registration

If you click the [Next] button at the bottom after entering information, the second
phase of application registration will appear once the information you entered in
the required fields and the dependency tests for country, price, category, etc. are
complete.
If multiple binaries are registered, binaries with no selected devices will be
deleted in the step 2.
The update will not be completed if a "Rejected" binary is found during
certification. Please check the status icons of the binary items and delete or
replace a "Rejected" binary before continuing to update the application.

2) Step 2 - Display Information

"
%)



A. Description
Please enter a description for the application. You can enter a description of up to
4000 bytes. Any excess description will not be displayed on Samsung GALAXY
Apps.
If you are selling your application to more than one country, please enter the
description of your application in English only.
Seven special characters (#, *, {, }, <, >, &) can be entered.

B. New features

If the contents of the application are edited, please input the updated content.
The update is limited to 4000 bytes of information and can be checked through
the Buyer Channel.

C. Tags



You can enter up to 15 tags.
Duplications or prohibited words youve already used cannot be entered.
If you click the [+] button, 10 new input windows are added at the bottom for
additional input.

D. Icon Image

Click the Search button and upload the image to be used as the icon of the
application.

"
%!
Images must be in PNG format. Size: 512x512 pixels, under 1024 KB.



E. Screenshots

The screen shot is an image displayed on the buyer channel.
Register 4 screenshot images.
The set image sizes are 800x480 or 1920x1080 in Landscape mode and 480x800
or 1080x1920 in Portrait mode; other sizes will not be registered.
(jpg, gif or png format under 500KB).

F. Supported Language



Check the languages supported by the application.

G. Additional Language


"
%"


Select another language if you want to add the description of the application in
other languages.
When you select a language, an input field for the language is displayed at the
bottom.
When you enter an application title using another language, you must click the
[Check] button as you did when you entered the basic information, to check that
the same application title is not already in use.
The verification rule for the main application title in the first phase also applies to
the duplication check for the application title in additional languages, but it does
not apply in the following cases.
b If the application title is a duplicate of the main application title.
b If the application title is a duplicate of the application title in another language.
The application title should be under 100 bytes.
You can enter a description for the application of up to 4000 bytes. (Seven special
characters (#, *, {, }, <, >, &) can be entered.)
The tag functions for additional languages are as same as those of the main tags.

"
%#
The same file size, resolution, and format limitations apply when registering a
screenshot image for an individual language as when registering the main
screenshot; you also use the same registration method.
After registering the language youve selected, click the [Save] button to create
the W icon at the right of the application title of the language. Select the W
icon to show the content registered for the language at the bottom.
Deselect the checkbox to delete all content registered for the language. The W
icon disappears.

H. Support



N Copyright Holder
Enter the name of the person or company who holds the copyright for the
application.
If a company possesses the copyright, then the company name is appropriate,
and if it is held by an individual, please enter his/her name.
If there is a copyright on the application, enter the Copyright Holder. The
information of the Copyright Holder will be displayed as the Seller name in the
store.

N Support E-Mail
Please enter an E-Mail address for users to send questions regarding your
application.

N Support URL
The URL can be registered, if there is any related site.

N Notify Result
You can register up to 20 email addresses to receive information about products.

"
%$

N YouTube URL
If you register a URL for a YouTube video, the URL will be displayed in the Mobile
Store when your application is approved.
Only standard YouTube URLs can be registered.
(http://www.youtube.com/watch?v=(video ID)).

I. Certification



Enter comments to be referred to at certification evaluation.
The following information must be listed in order to pass the certificate evaluation:
Login, Temporary Login ID, Password, Fake card number for testing purposes.
Failure to comply can result in denial of certification.
Reference material to be used during the certification screening can either be
attached if it does not exceed 1MB or a link with a related video is also
acceptable.
You can register a Self-checklist, which developers can then use to test the
application before registering it.
Unnecessary QA failures can be prevented by providing the concept of the app,
self-test results, and by noting any precautions we should take while testing the
app. If an app is re-submitted after update or QA failure, please note all of the
changes made from previous version.


"
%%
3) Step 3 Final Review



This is the part to check the input data. Please confirm that all data are entered in
conformity with the guide.
Click the [Back] button to go to the previous page. Click the [Confirm] button to
complete registration of the content you have registered to this point and transfer
it to the evaluation stage. Click the [Back] button to go to the previous page.





"
%&
4) Step 4 Complete



This is a guide page for completion of registration.
For Android and bada applications, a pre-examination is performed after the
registration is complete, and so their registration status in My Applications will be
displayed as "Pre-Certification". However, no pre-examination is performed if a
binary is not changed when re-registering or updating an application and
therefore, you can view the progress by looking at the certification status in My
Applications.
You can register a banner for the application when the registration is complete.


5) Definition of items for auto detection and manual input by OS

OS Type Field Default value
bada

Auto
Detection

API * Length: 10
Flash*
Exists only for bada 2.0 and higher. Conformity test
for content type is only performed for bada 2.0 and
higher.
App ID* Length: 256
Version*
For widgets, the version information in config.xml is
detected.

"
%'
Length: 10, Format: Numbers, Dots
Widget ID*
For widgets, the widget ID in config.xml is detected.
(Content ID : Widget ID = 1:1)
Manual
Input

Power VR Use a manual input value.
Camera Key Use a manual input value.
Google Mobile Service Use a manual input value.
VoIP Use a manual input value.
NFC Use a manual input value.
Others

Resolution Use a manual input value.
('*' is a manifest or config file for required definitions.)

6) Definition on Device Recommendation Criteria

OS Type Field Recommendations
bada

(all contents
type
except
widget)

Auto
Detection

API *


Flash *

If Flash is selected as the content type, devices
without Flash are excluded from the recommended
devices.

App ID*


Version*


Manual
Input

Power VR*

If No is selected, all devices are recommended.
If Yes is selected, only the devices with the function
are recommended.

Camera Key*

If No is selected, all devices are recommended.
If Yes is selected, only the devices with the function
are recommended.

VoIP*


NFC*

If No is selected, all devices are recommended.
If Yes is selected, only the devices with the function
are recommended.

Google Mobile Service*


Others

Resolution*

If multiple resolutions are selected, all
corresponding devices are recommended.


7) Definition of rules for version management in application

"
%(

A. Version examination when changing a binary or registering a new one

The version of a new binary must meet the following requirements in comparison with
any binaries previously registered (including the binary being replaced).

If the API Level is higher, the version must be higher.
If the API Level is lower, the version must be lower.

B. bada

The version must be between 0.0.1 and 35.35.1295.
The version for each binary must be different.
A binary with a higher API Version must have a higher version than the lower
binary.
If the MaxSdkVersion value is equal to or higher than that of other registered
binaries, then the API Level with the higher value will be considered.
min = SdkVersion, max = 2.0
If the API Level is higher, the version must be higher.
If the API Level is lower, the version must be lower.

N Rules for Version Code test depending on API Level
If there is at least one binary that has a value of MaxSdkVersion
b Compare the values of MaxSdkVersion for all binaries.
b For a binary only with a value for MinSdkVersion, the maximum API Level is
considered to be Max.
If there is no binary with a value for MaxSdkVersion, only MinSdkVersions are
compared. to be Max.

8) Definition of mapping for devices/binaries

C. Store policy

Only apk files suitable for the user device environment will be displayed.
If you change a device, you can download an application with a different binary
(apk) for the device with the same content/product ID.
If multiple binaries are mapped to a device, multiple registrations are allowed and
you can download a binary compatible with the OS version on your device. Also,
if there are multiple OSs with the same version, a binary with the highest Version

"
&*
Code will be downloaded.
If an application is registered for a specific device, but the OS version of the user
device is not compatible with the API level of the binary, the application may not
be displayed in the device's store.
In the event when 'MinSdkVersion=9 and MaxSdkVersion=14' :
b Download is available for Gingerbread devices which have API Level 9
b The store cannot be displayed on Froyo devices which have API Level 8
(filtered)
b The store cannot be displayed on Icecream Sandwich MR1 devices which
have API Level 15 (filtered)

D. Standards of binary mapping in the device

N Version of the devices OS = supported API Level.
A binary corresponding to the version of the devices OS is mapped.
If there are multiple binaries corresponding to the version of the devices OS, the
one with the highest Version Code will be mapped.

N Version of the devices OS < supported API Level
Product is not displayed in the store for the users device (filtering)

N Version of the devices OS > supported API Level (if a MaxSdkVersion value
exists)
Product is not displayed in the store for the users device (filtering)

E. Exceptions

If all the following criteria are met, a device cannot be registered for multiple binaries.

If the range of API Level available for support is the same or included in the range
of other binaries.
b Example: Binary A supports API Level 7-15, but binary B supports API Level
8-14.
If all configured devices are included in, or are the same as the device list of
another binary.
b Example: Binary A supports devices 1,2, and 3, but binary B supports
devices 1 and 2.
If the Version Code is lower than that of the binary
b Example 1. The Version Code of binary A is 2, and that of binary B is 1.

"
&)
b Example 2. Binary A supports API Level 7-15, but binary B supports API
Level 8-14 and if all devices configured for binary B are included in binary A,
binary B cannot be registered because the Version Code is lower.


9) Auto Detection information

F. Version

Samsung GALAXY Apps uses the Version Code listed in manifest.xml.
b <manifest xmlns:android="http://schemas.android.com/apk/res/android
android:versionCode="2 android:versionName="1.0.0.1 package="package
.name.sample"
The Version Name is the Version of the application that is displayed to buyers on
the channel.

G. VoIP

If any of the following uses-feature cases exists in the manifest, the application is
considered to support VOIP.
b <uses-feature android:name="android.software.sip.voip"
android:required="true"/>
b <uses-feature android:name="android.software.sip.voip"/>
b <uses-feature android:name="android.hardware.sip.voip"
android:required="true"/>
b <uses-feature android:name="android.hardware.sip.voip"/>
If uses-feature required = "false", the application is considered not to support
VOIP.
b <uses-feature android:name="android.software.sip.voip"
android:required="false"/>
b <uses-feature android:name="android.hardware.sip.voip"
android:required="false"/>

H. Telephony

N For the following cases, the application is considered to support Telephony..
If any of uses-feature cases exists in the manifest
b <uses-feature android:name="android.hardware.telephony"
android:required="true"/>
b <uses-feature android:name="android.hardware.telephony"/>

"
&!
b <uses-feature android:name="android.hardware.telephony.cdma"
android:required="true"/>
b <uses-feature android:name="android.hardware.telephony.cdma"/>
b <uses-feature android:name="android.hardware.telephony.gsm"
android:required="true"/>
b <uses-feature android:name="android.hardware.telephony.gsm"/>
If any of uses-permission exists in the manifest
b <uses-permission android:name="android.permission.CALL_PHONE" />
b <uses-permission android:name="android.permission.CALL_PRIVILEGED"
/>
b <uses-permission
android:name="android.permission.MODIFY_PHONE_STATE" />
b <uses-permission
android:name="android.permission.PROCESS_OUTGOING_CALLS" />
b <uses-permission android:name="android.permission.READ_SMS" />
b <uses-permission android:name="android.permission.RECEIVE_SMS" />
b <uses-permission android:name="android.permission.RECEIVE_MMS" />
b <uses-permission
android:name="android.permission.RECEIVE_WAP_PUSH" />
b <uses-permission android:name="android.permission.SEND_SMS" />
b <uses-permission
android:name="android.permission.WRITE_APN_SETTINGS" />
b <uses-permission android:name="android.permission.WRITE_SMS" />

N For the following cases, the application is considered as not supporting Telephony.
If uses-feature required = "false": uses-feature has priority, even when the
Telephony permission exists. Therefore, the application is considered as not
supporting Telephony.
b <uses-feature android:name="android.hardware.telephony"
android:required="false"/>
b <uses-feature android:name="android.hardware.telephony.cdma"
android:required="false"/>
b <uses-feature android:name="android.hardware.telephony.gsm"
android:required="false"/>
If neither uses-feature case nor uses-permission exist in the manifest

I. NFC

N For the following cases, the application is considered to support NFC.

"
&"
If any of uses-feature cases exists in the manifest.
b <uses-feature android:name="android.hardware.nfc"
android:required="true"/>
b <uses-feature android:name="android.hardware.nfc"/>
If a manifest exists in the uses-permission below
b <uses-permission android:name="android.permission.NFC"/>

N For the following cases, the application is considered not to support NFC.
If uses-feature required = "false" : uses-feature has priority, even when the NFC
permission exists. Therefore, the application is considered as not supporting NFC.
b <uses-feature android:name="android.hardware.nfc"
android:required="false"/>
If neither uses-feature case nor android.permission.NFC exist in the manifest

J. Faketouch

N For the following cases, the application is considered to support Faketouch.
* <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"/>

N For the following cases, the application is considered not to support Faketouch.
If 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"/>
If uses-feature case not exist in the manifest.

K. Group Play

If the following meta-data exists in the manifest file, the application is considered to
support GroupPlay.
* <meta-data android:name="GroupPlay" android:value="true/>

L. Touchscreen

"
&#

For the following cases, the application is considered as using Touchscreen.
When one or more uses-feature cases exist 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 uses-feature case exists in the manifest
If the following uses-feature exists in the manifest, the application is considered
as using Touchscreen, but the use of it is not mandatory.
* <uses-feature android:name="android.hardware.touchscreen"
android:required="false"/>





"
&$
4. bada Application Development Procedures













1) Developer Site : Register application development information

A. Registration procedure

Sign up
Generate a new application profile
Set application version
Select privileged groups to use
Set up bada components
Select system requirements
Download manifest.xml
: The manifest.xml file contains the application ID, privileges, application features,
and other design and runtime information.

B. Standards for managing mainfest.xml depending on status of registration for bada
application on Seller Office


Seller Office
-Register your application
- Sell your application
IDE and SDK
- Write your application.
- Test your application.
Developer Site
- Create your application ID.
Download
manifest.xml
Select System
Requirements
Set up
Components
Assign Privilege
Groups
Generate New
Application
Profile
Develop Mobile
Application
Run in Simulator
for Testing
c 1&H&'->&. %9)& d
Run on Target
Device for Testing
Package for Release
and Deployment
Build UI
c @1? +4< %1T d
Application
Registration

Sales

Application
certification

Security Test

c %&''&. L,,9(& d
Text

"
&%
Application
Type
Classification
developer.bada.com
Change Classification
Details
Change App
ID
Version
upgrade
Native bada
Initial
registration
New New
Get manifest.xml from Generate a New
Application Profile in
developer.bada.com and register the
binary containing the file.
The multiple use of App ID is only
available if Device is different. Also, the
App ID of a deleted application can be
reused after termination.
Modify the
rejected
application
and re-
register it
(Re-exam).
Same Same
Do not modify the manifest.xml file and
maintain the existing binary for Re-exam.
Modify the
existing
application
by using
Update
(Revision).
Same Same
In case of the binary being unchanged
Maintain the existing binary without
changing manifest.xml for revision in
Seller office.
Same
Upgrade
needed
In case of the binary being changed
Perform Add Version for the application
registered in developer.bada.com and
use it after downloading the relevant
manifest.xml file.
Registering
of already
registered
applications
as new
applications
New New
To re-register the same binary as the
previously registered application without
revision/re-exam, replace the
manifest.xml file with the newly issued
one from Generate a New Application
Profile in developer.bada.com so that
App ID is not duplicated and the
application can be successfully
uploaded. The multiple use of App ID is
only available if Device is different. Also,
the App ID of a deleted application can
be reused after termination.

* Warning: Do not arbitrarily manipulate the manifest.xml file issued from develpoer.bada.com.

2) IDE and SDK: Application development

Develop Mobile Application
Build UI
Run in Simulator for Testing
Run on Target Device for Testing
Package for Release and Deployment
b Generate a Zip file from Project > Make Package.

"
&&
b Select the files and folder to be included in the package.
b Enter a new package name and select an output folder.
b Check the created package in the output folder.

5. Security Test



The security of an application is verified before the evaluation of the certification.
The progress of the operation is shown as "Pre-Certification" under the
registration status of Applications > My Applications.
In the situation where the process has failed, the seller will be notified via e-mail.
To find out the reason for the rejection, go to the certification status in My
Applications and click the pop-up icon with "Pre-Review Rejected" status.
If the application passes pre-examination, it will go on to the Certification Status
and the pre-examination process will begin within a day.
A bada application in .zip format will automatically converted into an .oap file after
going through DRM (Optional) selection, API certification, and Code signing.

6. Application Certification

All applications that pass the certification test will be put on sale

In the situation where certification has been rejected, the seller will be notified via
e-mail. To find out the reason for the rejection, go to the certification status in My
Applications and click the pop-up icon with "Rejected" status.

"
&'
All applications that passed the certification will not be distributed on real time. A
maximum of a day is needed as the applications will be distributed to stores by
the server via the automatic distribution.