QNX to power BlackBerry handsets too
Not just a tablet OS
RIM has plans for QNX to replace its existing handset operating system, though there will be one more version before the company adopts a single-OS strategy.
RIM bought QNX last April and is using the OS on its PlayBook tablet, but has now confirmed that it will be using the diminutive OS in its phones too, with one new release of the BlackBerry OS as a stepping stone to a common platform.
Version 6 of BlackBerry OS is only just out of the door, and has been well received as matching but not exceeding the competition. Version 7 is now in development, but that will be the final version of the OS as RIM expects to have its entire portfolio of applications ported over to QNX by then.
Your correspondent evaluated QNX for a set-top box about 12 years ago, but found the lack of Java support intolerable (we ended up using VxWorks). So it's strange to hear that Java support remains problematic, with development on the PlayBook limited to JavaScript and AIR (and native QNX of course).
But that's a temporary problem, and one that RIM will need to swiftly address if it's going to bring the 10,000 applications currently available on BlackBerry handsets to the PlayBook.
Once that's done there seems little reason to maintain separate platforms, so it comes as no great surprise that RIM won't. ®
COMMENTS
@Let's hope..
Clearly Conrad you don't understand the Nokia software strategy which is to keep both Symbian and MeeGo as each OS targets very different markets, and there will be Qt on top of both. It's a great strategy, as Symbian and MeeGo both have very different strengths.
Qt is a cross platform run-time that is being received very enthusiastically by developers and it will allow those developers to code for Symbian and MeeGo at the same time, and to not care about what OS their apps are deployed to.
RIM don't have the luxury of Qt and the future for them will be messy as they try to transition developers from BB OS to QNX. If there is no compatibility between QNX and BBOS 6 and with the stated aim to ditch BBOS after v7 I can't see why developers will continue to invest more time developing for BB OS, whatever version.
Sounds like a revrse takeover!
RIM buys QNX; QNX squeezes out the RIM OS.
Let's hope it is as secure and as reliable. as the RIM. As well, even if the US requires backdoors, other countries will get 100% secure transmissions.
@RTP Qt
I'm well aware that Qt is available for QNX, but what point is that when Qt isn't available for BB OS? Without Qt being available on both platforms, the benefit of a cross platform run-time is entirely lost.
RIM need to get their developers off of BB OS as soon as possible, either by providing a short-lived cross-platform run-time (Qt would be ideal, but not in keeping with the proprietary nature of RIM and since the objective is to get to a single OS somewhat pointless) or by providing a compatibility layer or even BB OS emulator on QNX (similar to what Palm Software proposed many years ago when trying to ditch their old OS which they had already flogged off to Access for something newer - was it called Cobalt or something, was it even released in the end?)
By announcing that BB OS is going to die soon, any self respecting RIM developer would now be considering QNX only which should leave BB OS a little bereft when it comes to new applications. Can't help thinking that RIM may have been a bit premature with this announcement, unless they have something else up their sleeve.
A bit like...
...NeXT taking over Apple. Went quite well for them. Though Apple could concentrate on the desktop for several years while a bit of iPhone/iPad skunkworks went on in the background until it hit primetime. QNX has an huge customer base of varying industries. Will RIM be able to keep them happy while keeping enough the focus on the BlackBerry/PlayBook?
photon
@Zan
its not hard, the hardest part is finding the right app code-base to make your non profit app from and RTP back in the day did a fine job If you can code, and the current RIM RTP is still the same RTP6 codebase so it should be reasonable to take the above and code/port something werthwhile , are RIM still using photon as their base GUI BTW bill?
i ask as back in 2001, Dan said to me that we/anyone could replace that with any Amiga GUI we liked if we just write the GUI code and used the supplied hooks in the the RTP to insert it, a few hours work i seem to remember he said.
http://mobile.osnews.com/comment.php?news_id=77
"
Daryl was just a summer qnx intern back in the day but had good inventive idea's, wonder what your doing now Daryl if you read this.....?
....
(#527) Why wait?
By Daryl Low on 2001-09-03 02:25:52
No need to wait for QNX to release the iPAQ stuff or for us to write all the apps. The entire demo was written and tested (in a few weeks) on stock x86 machines running RTP. The basic formula was:
1) Grab a screen shot and draw a UI (with your favourite BMP editor)
2) Implement the UI (using PhAB)
3) Code the backend
4) Glue them together
There really wasn't any secret mojo involved here. Most of the "Memory" app was done in about 8 hours (most of which was staring at the code for "pidin" from cvs.qnx.com). A basic ToDo app shouldn't be much harder, same for an Address Book app, with a Day Planner app just a notch trickier. Come on people! Download a copy of RTP and get going! "
people might also remember the iPac port LOL
http://www.vitanuova.com/screenshots/charon_ipaq.jpg
http://eqip.openqnx.com/ipaq_bsp/embed_intro.html
so todays phones are massive and far more powerful compared to that device, it ran really nicely too.
