📜 ⬆️ ⬇️

Samsung Bada Application Development - Part 2

Hello everyone, this article is a continuation of the first part . I will talk about my experience with the Samsung Apps Store, what could be the difficulty and what is the dry residue. First there will be a theory, then practice. I have tried to give as many tips as I can.

Accommodation in the Samsung Apps Store

I recall the process of placing the application in the store. We create an application profile on developer.bada.com, then create the corresponding profile on seller.samsungapps.com. I think that there will be no particular difficulties if you are familiar with English. I liked the fact that for any country you can set a localized description, price policy and even the name.

At the end, you need to upload the package (package, archive with the application) to the server. Robots will conduct a primary analysis of the package - integrity, proper structure, manifest. Then begins the multi-step process of acceptance into the store (approval). Treat him as an exam for a strict teacher - patience and hard work all, and you should not wait for freebies. The procedure consists of 5 levels:
After passing through all 5 levels, the application is finally placed in the store. On the second, third and fourth in case of failure, the Koreans will send a detailed list of all errors, with comments and (device test) video (!). After correcting errors on the list you should be skipped on. However, at the last level, the change will take place before the first critical error. You will also be provided with a detailed report and video. After correcting the error, it is likely that they will find another one.
The typical duration of a single attempt is two weeks. Optimistic forecast - one week. Pre-test does not take longer than a day, most of the time is spent on device test and confirmation. After each failure, you need to create a manifest with a larger version on developer.bada.com and use it during the next build, otherwise the robot will not allow unloading the package. The most embarrassing moment - during the delivery can not be unloaded new version . This means that before unloading the updated package, you need to check ten times whether everything is fixed, whether new errors have appeared, etc. Then it will be too late.


So, we have the Bada application, which we tested on the simulator and made sure that it works. The first rule is based on bitter experience: the next mandatory step is to check the application on the hardware . With each release of the new version. Every time - completely. If there is no iron, then you can use the Samsung RTL ( I already wrote about it ). For me it was the only way. Not very convenient and has significant limitations, but for static things it works.

During testing on the device, pay attention to even the smallest details, inscriptions, buttons, sizes, screen rotation. Do not forget to change the splash screen from default to your own - this is a copyright infringement of Samsung. White and black box methods should be applied. This will save you time for device test.

After extensive testing, you must carefully review the code manually and determine the privileges used . The built-in analysis is good for nothing - in my code of three privileges, it did not identify any. This step requires an excellent knowledge of the privilege system by heart, since sometimes even the most obvious API calls are under a virtual lock. This is useful for pre-test.

My success story

My application is BadaArchiver. Page in the store. This 7-Zip, compiled under Bada, wrapped in a GUI. I’ll say right away, if it were not for my extensive experience with 7-Zip , I could hardly have managed to port the code, and you shouldn’t rush to compete with me in the hope of a fast port. A lot of little things, driven only by Igor Pavlov and me. Sorry, carried away.
I passed the application from the fifth attempt and spent 2 months on it. I started as a complete newbie, with little experience developing on other mobile platforms.
The first attempt failed on pre-test due to privileges. I looked at Osp :: Media :: Image :: DecodeN (), which requires the Osp :: Media IMAGE privilege.
The second attempt failed because of the default splash screen and unintended screen rotation. I changed the screensaver, but simply banned the rotation.
The third and fourth attempts failed due to serious shortcomings. For example, I have not provided for action in case a memory card is not inserted.

Examples of videos from Koreans in which they show errors:

I set the price of my creation $ 10 worldwide, except Russia. Countrymen put 100 rubles, added a description in Russian and allowed to pay by SMS. For two days of sales, I earned about $ 200. I was surprised when I discovered it. Nicely. In a couple of weeks I can provide statistics.


You can develop Bada applications. The approval procedure is not the fastest, but as transparent and fair as possible. Many details that are poorly covered in the official documentation, but all problems are solved. Money is paid, the market is actively developing.
Perhaps I have nothing more to add. As always, happy to answer your questions.

Source: https://habr.com/ru/post/105451/

All Articles