[anon(1049620)]

Why did RIM spend a year implementing this? Had they put all that effort into getting the NDK, Cascades, and their "open" development community launched months ago, then today we'd already have the apps that you find on Android and iOs ported to the PlayBook, NATIVELY. Instead, consumers are going to be stuck with a buggy, inconsistent experience for running Android apps, and the developers of said apps aren't even going to bother improving the experience by using native PB development tools. It's a lose-lose, and what I think is a major strategic mistake.

RIM: If you're willing to bet that developers are going to embrace your new approach to development as a whole, the tools, the community, the ability to unlock the incredible capabilities of the PlayBook, then WHY would you create a virtual machine to run Android apps? If expanding the application ecosystem is your goal, then all you needed to do was make it easy for developers to code for the PB, not give them an excuse to be "lazy" and port Android apps over (50% of which aren't even going to run properly and will need to be recoded -- and probably won't be -- regardless).

[narci]

http://forums.crackberry.com/general...player-662947/

http://forums.crackberry.com/blackbe...ective-663010/

http://forums.crackberry.com/playboo...er-who-663209/