Since pb is open to android apps, does this mean that less developers are willing to make apps purely for app world?
Printable View
Since pb is open to android apps, does this mean that less developers are willing to make apps purely for app world?
I wouldnt worry about that too much. Basically any serious Android developer loking at PB would have ported by ow or has no goals to. But by enabling Android RunTime they have a chance to re-examine the Android apps again to see if it is worth it to port.
Inevitably someone will overlook native PB SDK options because of it. But right now choices are Adobe AIR (ok but cumbersome to work with - bad documentation for ActionScript Mobile specifically plus missing basic developer abilities like 2d arrays) or native sdk which i have also found cumbersome - its crashy too and not as compatible with other c++ oses as i would have liked...
Long story short you may even get some better quality apps this way too.
Your question is moot because Android player is, in fact, one of the ways that developers can make apps purely for App World. It's all about choice and RIM has finally realized that developers like choice. This method of creating PlayBook apps will appeal to developers who want an easy way to port their existing Android apps to the device. In addition, some Java developers welcome the opportunity to write apps for the PlayBook without having to learn a new language. This is possible because Android apps are coded in Java before being compiled into an APK file. Come to think of it, I probably would not have bothered to learn AS3 if the player had been available prior to the PB launch last April. I have begrudgingly come to accept AIR is a worthy development platform but I do miss using threads, method overloading and other advanced features available in the Java language.