If you are thinking about monetizing your Series 40 application but reluctant go through those numerous In-application Purchase API’s boring guides, take IAP application template and use it in your project with minimal adaptation.
Save your time, focus on your project and leave IAP routine for me!
That is the main goal of the IAP application template project. Please try it and let me know how I can improve it.
Easing your digital life
30.07 I started porting FifteenPuzzle game project to Series 40 platform and today 10.08 that work is completed. Having promised to complete the project in 5 days I observe the golden rule of project management in action : multiply your project estimation three – two times before passing the estimations to your customer
But nevertheless… Meanwhile I have explored Scalable Graphics in Series 40 for possibility of applications localization and created a wiki article. FifteenPuzzle game project now contains SVG main menu and text in SVG document is translated to English , Finnish and Russian. The whole the application features list is the following:
1) main menu SVG
2) device language detecting and supporting automatically
3) SVG text localization
4) supports screen sizes:
240 x 400 Asha 31X
320 x 240 Asha 30X
240 x 320 Asha 20X
128 x 160 Asha 1XX
5) Disables SVG automatically on low-range devices (Asha 1XX)
Check it out
If you are watching the wiki article series “Quick start in game development for Series 40”, this announcement for you. I am glad to say the series is complete. An application project complements the articles and shows how functionality is built up step-by-step. So it is convenient to examine the code difference to understand how it works. The latest project step is available for download from article “Game development for Series 40: Main menu implementation” or from here. The game path-finding and collision detection algorithms are left outside of the series. Perhaps i will return to that when i have time. So far it was good coding race and interesting platform exploration for me. I hope it is useful for you as well. Please comment and ask – each and every question will be answered.
There is interesting observation in business model comparison
Nokia provides several business models for developers:
1) Free download.
2) Paid download.
3) In-App Advertising.
4) In-App Purchasing.
There are two applications published on Ovi store almost simultaneously in about end of this May. The apps are exactly the same but targeted to different platforms and implement two different business models.
One is a paid application for Harmattan devices. Other is targeted for Symbian platform and implements In-App Purchasing API with try and buy approach. The both apps are not promoted and have little visibility on the market.
So what is interesting about gathered data statistics:
1) The income result for the both is almost the same at the moment
2) During time income is growing exponentially for In-App Purchasing application variant while paid download application shows steady result
3) Downloads for In-App Purchasing application variant exceeds paid counterpart in 300 times.
From the data statistics I can conclude the try-and buy application with In-App Purchasing API is self-promoted. And that promotion is quite efficient — you do not need anything to reach considerable volume of downloads. To leverage that effect consider side-loading your application from other sources than Ovi Store. And to reach even more think how to incorporate social network services as “share with ….” , “game score …” — for example Facebook scores API
But the key point is the software quality. Try and buy scheme is the fare trade that proves fundamental “Quality is in the eye of the beholder”.
If you got recognition with Try and buy application model, be proud of making really good things!
Series 40 full touch and Nokia SDK for java 2.0 introduce great improvement in application capability for low-price range devices. There are enough materials that explain new things as 3D, sensors, touch UI, etc… Mostly the documents are for experienced developers hungry for new application features. What about newbies in Series 40? We are going to fill the gap with the wiki article series “Quick start in game development for Series 40”.
Why games? I think nowadays for individuals it is hard to compete with business applications on the market by several reason. One of the reasons is – devices are sold with preinstalled good application collection for every-day users’ needs. There is no much room for improvement for third-party developers. Not the same situation is in game world. Express yourself! Game development is more art than business app development. Game development requires more than just programming and UI design skills. It might start from making a story, making characters and end-up living creatures in your world. That is rather exiting opportunity. Considering growing low-price device market available by Nokia you can get even some profit for your game or at least recognition. Target your game to Nokia Store!
So, how do I start? Please go to the wiki and follow the step-by-step instructions. So far there are two articles in the series starting from creating game application skeleton to adding touch support in it. I hope to keep my pace and release more articles in near future on regular basis. What will be next in the series:
- Path-finding and collision detection algorithms
- Main menu implementation
- Supporting devices with different capabilities. That is actual question for SVG graphics and screen geometry because touch screen supporting is not conflicting in code implementation with key-only devices as Nokia 110.
- Advertising your game with social networks, like sending game scores via Facebook (honestly I have only vague idea how to implement it. Let’s see how it goes. But definitely that feature is in great demand)
Caution! The articles are focused on technical problems only – bring there your imagination and art