Go to Content


Home > Library

bada application packaging & publishing guide for Android developers

By bada Master | 8478 views | Nov 29, 2011

To install and run an application on an Android or bada Smartphone, the developers should sign the application with the developer's private key and upload the application to a distribution channel such as the Android market or Samsung Apps. This signing procedure applies a unique key to the application on the basis of the host machine (computer) of the developer, and prevents unauthorized persons from registering a developed application to the market by signing an application and uploading an application to the market because the key is different.

Figure 1 . Android's packaging


Then register the signed application binary file to the publishing site (http://market.android.com/publish) of the Android market with the necessary image and description.
In bada, developers should register the developed application to the Samsung bada developer site (http://developer.bada.com), issue the manifest.xml file, build the application in the Eclipse IDE and registers the application to the Samsung Apps Seller site.

Registering Developers

Registering the application to Samsung Apps requires building with the certified manifest.xml file followed by the completion of the packaging. The certified manifest.xml file can be received after registering with the bada website (http://developer.bada.com) as a developer. The application registration process for an already registered bada developer is as follows.

Issuing Application IDs

First, select the Application Manager from the MyApplication menu.

Figure 2. bada’s MyApplication

Select the Generate a New Application Profile button to move to the Basic Information screen where you can enter the description about the application.

    Figure 3. Generate a New Application Profile button in the ApplicationManager

In the Basic Information screen, you should fill in the Set your application name field and check for duplication. Then enter a description about the application in the “Describe your application” field.  Fields with the * mark must be filled in.

  Figure 4. Basic Information of the ApplicationManager

Then you have to enter the Application version and API version in the Advanced Information screen. First, fill in the Application version field.

Figure 5. The version field in the Advanced Information
Then select the API version. Be aware that if bada 2.0 is selected, the application type needs to be selected from 4 types of applications.


    Figure 6. Selecting the bada 1.x application type in the Advanced Information screen

For bada 2.0 API, the application should be specified as one of the four application types.

Figure 7. Selecting the bada 2.0 application type in the Advanced Information screen

Clicking the Generate button after entering the application information generates the manifest.xml file.


Figure 8.  Completion


Configuring the Privileged API for the Application

bada’s manifest.xml file contains the privileges for the device resources for applications as well as the application ID. Therefore, after the completion of the Application ID generation, the privileged API should be selected. For example, if you want to use the Notification service, you have to select the service as shown by the figure below. In the same context, the Camera privilege should be selected in the Media field in order to use the camera.

       Figure 9. Selecting a Privileged API
After the selection, click the Next button to finish the configuration.

Creating the manifest.xml file

After selecting bada based mobile phones compatible with the OS type selected in the Advanced Information screen, clicking the Finish button generates the manifest.xml file.  

                                                                                             Figure 10. Download manifest.xml

Then, if you download the manifest.xml file here, the application registration is completed. Then, let's look at how to replace the manifest.xml file in the Eclipse project and build the application.
You can reissue the manifest.xml file by clicking the application name in the bada developer site or selecting the MyApplication menu and modifying the app information of the site. If the API version to be used is changed, press the Modify button in the version information page to change the API version.

Extracting an App from Eclipse

Overwrite the default manifest.xml file in the root directory of the Eclipse project with the downloaded manifest.xml or back up the downloaded manifest.xml file.


     Figure 11. Download manifest.xml

Then change the Build Configuration to Target-Release to build the application for real bada Smartphone devices. When the build is complete, run Make Package to create the package file.


Figure 12. Generating the bada app package with Make Package



Registering with Samsung Apps

You can use the developer ID that you registered with on developer.bada.com, on the seller.samsungapps.com site. In the initial login, you can sign up as a Private or Corporate Seller.

  Figure 13. Seller types in Samsung Apps
To register as a seller, fill out the form and receive a confirmation by email. Clicking the URL in the confirmation email will complete the registration process. Now you can login as a seller and proceed with the registration process, depending on the application types.


   Figure 14. Selecting the Application Type in Samsung Apps

The app registration process consist of the Basic information, Display information and Final Review screens. Fill in the forms in sequence.

   Figure 15. The Application Registration Process in Samsung Apps

As the first step, enter the basic information of the application in the Basic Information screen so that the application can be found by the Samsung Apps search system. Let’s have a look at some of the important information. Start with selecting bada in the Select OS field and then the screen resolution.

Figure 16. OS Selection during the Application Registration

Then select the category of the application.

   Figure 17.  Category Selection during the Application Registration
In the binary file registration screen, once a zip file created by Make package is selected, the bada application is validated by the server and the result is displayed.

     Figure18. Registering the binary file during the application registration
Once this step is completed, the download status can be monitored by MyApplication in the Application tab. The application approval takes 7 working days and a game application takes 15 working days.

Using Mobile Devices

In the case of Android, you can get a Google developer account at $25/year and immediately register your application to the Android market.
However, unlike Android, bada applications can be developed and released for free. It is also possible to install applications under development on mobile devices, and it only requires registering a certification to the mobiles devices in use.
On a Wave phone, select Settings > Connectivity > USB utilities> Mass storage to change the phone to a removable memory device.

                                                                                   Figure 19. Changing the device to a Removable Memory Device

Now the Test Root certification needs to be copied and registered. The Root certification is the rootCaCert.cer file located in the Tools\sbuild folder under the directory where bada is installed. Copy the file to the Other folder of the mobile device.
For Wave phones, run the My Files program and select the Other folder, then you will find the rootCACert.cer file which was copied in the previous step.
Select this file to install the certification and then connect the mobile device.  
Did this document help you? Yes | It's good,but ... | Not Helpful