We know that many of you are looking forward to BlackBerry® PlayBook™ OS 2.0, and we wanted to provide you with an update on the progress that we’re making.
As much as we’d love to have it in your hands today, we’ve made the difficult decision to wait to launch BlackBerry PlayBook OS 2.0 until we are confident we have fully met the expectations of our developers, enterprise customers and end-users. And here’s what we’re doing to accomplish that.
This must have been a tough decision for RIM, though if it means a release that doesn't feel rushed, then it may benefit them in the long run.
The article does mention that BBM won't be available as a native client, and given that the service relies on a separate PIN for each device, it kind of makes sense. What I think would have worked better is if a native client was made available that would benefit non-BlackBerry users, but still allow the Bridge function for those who already have a BlackBerry and want to keep using BBM on their Playbook.
As much as we’d love to have it in your hands today, we’ve made the difficult decision to wait to launch BlackBerry PlayBook OS 2.0 until we are confident we have fully met the expectations of our developers, enterprise customers and end-users. And here’s what we’re doing to accomplish that.
This must have been a tough decision for RIM, though if it means a release that doesn't feel rushed, then it may benefit them in the long run.
The article does mention that BBM won't be available as a native client, and given that the service relies on a separate PIN for each device, it kind of makes sense. What I think would have worked better is if a native client was made available that would benefit non-BlackBerry users, but still allow the Bridge function for those who already have a BlackBerry and want to keep using BBM on their Playbook.