A thread live and kicking in CB Forums has brought forth several arguments and would-be explanations behind BlackBerry and Google uniting ecosystems for BlackBerry World allowing full access of Android apps within BlackBerry World. Could this deal potentially make money for Google while allowing BlackBerry to solve it’s biggest problem, apps? Sporting a 4.2.2 Android Jelly Bean runtime on BlackBerry 10.2, I speculated back in May BlackBerry was working to amass an app catalog of up to 1 million and take the fight directly to Apple and Samsung.
And I wasn’t taking out of THIN AIR Jefferies in a research report made such claims:
“The Blackberry 10 has got the support from a private company, which will allow the whole Android catalog to be ported on BB10 devices, and the user will feel that the whole catalog is native and has not been ported. The company will provide the solution that will be a link between BB10 and Android ecosystem of more than 700,000 touch enabled apps”
Within the latest forums comes an interesting reasoning behind all the subterfuge:
“Actually you’re incorrect and I can confirm the legitimacy of the OP and I’m not associated with the OP. I don’t even know who the OP is or his friend.The runtime has been released in BB World so that BlackBerry can now update the runtime outside of carrier’s control to enable access to Google Play and whatnot when this hits. It’s not a minor update, there is more to come.
Google and BlackBerry has recently entered an agreement to bypass the Open Alliance relationship so that BlackBerry can deploy Google Play onto BlackBerry 10 as well as enable the currently disabled Google Services Framework (GSF) embedded into the runtime. Meaning not only in the future will users be able to download apps directly from Google Play on device, every single native functionality will be available for use. In plain English, every single Android application will work without the need to sideload, without the need for a debug token or any form of method to enable functionality to work. But you’ll need to be on a 10.2.1 build or higher…