Linked by Thom Holwerda on Tue 18th Oct 2011 21:02 UTC
PDAs, Cellphones, Wireless What many of us wondered the moment Research In Motion announced the PlayBook's QNX-based operating system has now transpired: the Canadian smartphone and tablet company has announced BBX, their QNX-based operating system for both smartphones and tablets - in other words, the expansion of the PlayBook operating system into smartphones.
Thread beginning with comment 493453
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[4]: ...
by Not2Sure on Wed 19th Oct 2011 16:41 UTC in reply to "RE[3]: ..."
Member since:

One aspect of your comment I don't necessarily agree on is the suggestion that RIM needs a change of leadership. Yes, Mike Lazaridis is not what you'd call charismatic, but at least he is not backing down and giving in to the pressure to adopt Android or WP7...

Well in effect he has. If you read closely you will see that Playbook and the next gen of RIM smartphones are completely abandoning the blackberry platform and API for an Android "app player" as a preferred method of application development with adobe AIR, a web runtime and a native C/C++ SDK as options.

It's kind of spitting in the current blackberry developer's faces who have supported your platform for years tbh that it's a priority to get an Android compatibility layer first before (or apparently ever) a bb compatibility layer. They are now looking at massive rewrites of existing apps for the next generation of phones. It is effectively giving CIO and CTO everywhere the chance / forcing the issue to decide whether to abandon Blackberry for Android, iOS and I'm pretty sure alot will. To keep your exisiting apps running on the next gen smartphones will mean deploying via the native SDK your own jvm, and an implementation of whatever j2me/bb api your app uses for each and every app bloating code size dramatically, or rewriting it for "Android"

I don't begrudge a (co-)CEO the chance to make choices and display leadership. They have made some great accquisitions recently for example. But they have to be accountable for their choices. The Blackberry brand has suffered under current leadership. It is seen as "old" and "slow" and now "untrustworthy." They ignored key markets for too long and just assumed the enterprise would never go anywhere else so they stopped innovating. WP7.5 has basically caught up to blackberry in terms of API completeness in 2 iterations and a couple of years.

Their hardware team got stuck cranking out models based on the same MSM platform with miniscule clock bumps while other manufacturers were upgrading to more performant platforms. It's with only the latest os that they have a decent OpenGLES implementation for example. Their only radical departure from was the Storm and we all know how well that went.

Those kind of strategic failures a CEO has to be accountable for in my book.

I agree they are far from "over" And this essentially represents a reboot of the blackberry line. They just better have some really great hardware to go with it or people will not follow them for the ride. Very little brand loyalty anymore.

HP and Nokia Boards of Directors are clearly incompetent but I don't see how their failures reflect on RIM's Board.

Reply Parent Score: 1

RE[5]: ...
by Moochman on Wed 19th Oct 2011 19:48 in reply to "RE[4]: ..."
Moochman Member since:

Hmm, I guess we see things differently. To my mind it's smart of them to abandon backwards compatibility with their old phone OS apps.

First of all, from an end-user perspective, from what I hear, Android apps tend to be a whole lot slicker, more polished, and better supported than their BlackBerry counterparts. It's like the difference between Windows Mobile 6.5 and Windows Phone 7--I think it's safe to say that WP7 end-users are collectively breathing a sigh of relief that those old Windows Forms apps are a thing of the past--and the story is bound to be similar for BBX.

As for the developers--how many BlackBerry-only (as opposed to BB and Android) developers are there really? And of those, how many of the apps they put out are truly innovative and not just making up for some deficiency of the BlackBerry OS? Really I'd estimate that the number of developers actually getting burned as you say is pretty low. And this, combined with the poor end-user story, means it makes sense that RIM didn't waste effort on backwards compatibility.

Reply Parent Score: 2