If they had done this before Nokia bought in to Windows Phone 7 then we might actually have seen a great user interface on Nokia's excellent hardware.
Maybe RIM could adopt it instead? They could really use a better UI, plus a platform that actually scales well to tablets. Plus they have a large enough install base that once they get rid of their disastrous programming environment developers might actually start writing good apps for their phones.
I agree that Nokia would have been a nice fit for WebOS, but people who don't think Windows Phone is has a great interface for a phone are squarely in the minority.
But yes, it's great that two things came out of Nokia+Microsoft: Microsoft finally has a really solid mobile hardware partner, and Nokia finally has a well-designed operating system.*
*That they care about. Shed a tear for MeeGo Harmattan.
Nokia switching to an open-sourced WebOS would never have happened. They already had a beautiful, slick and usable operating system, and at least some kind of a strategy of bootstrapping it into a viable ecosystem (using QT on Symbian as the incentive to develop for QT on Meego).
It's still hard to say whether the decision to basically can Meego and bet everything on WP7 was the right one. But at least there was some kind of a case to be made on WP7 having a larger potential ecosystem, and Microsoft being willing to give Nokia huge bags of money. For WebOS it would have been a case of downgrading in every important sense. No real eco-system, no in-house experience, no other company backing it, no real technical advantages over Meego.
I've been an iPhone user since 2007 and have had every model with the exception of the 4s. I fully intended on moving to Android, specifically the Galaxy Nexus, but after playing with the Mango UI I bought the Samsung Focus S and I'm glad I did. It is by far the best OS I've used on a phone yet! It makes the iOS UI simply look dated (which in all honesty it hasn't changed much since 2007).
Unfortunately, the app ecosystem has not caught up to the system UX yet. A lot of the apps are slower and have fewer features than their iOS/Android counterparts. That seems to be the case with webOS as well. Hopefully, these platforms catch on a little bit to provide a refreshing counterbalance to the app grid UX of iOS/Android.
There are definitely far fewer apps in their app marketplace. However, the core apps that I use quite frequently are there and are just as good as their iOS counterparts (if not better...both Spotify and Twitter I prefer on Mango). There are a few exceptions here for me like 1Password which is not near as good as the iOS version but to be fair they offer it for free on Mango compared to the 15.00 price tag on iOS.
The one thing I'm really excited about though is that the developer tools are second to none. Microsoft has made it very simple to build very nice looking applications very quickly. As a developer that just moved to this platform I see the limited apps as great opportunity to help improve this platform even further and I plan on doing just that!
So you're saying you're a "developer" that was using iOS, planned on going to the Nexus and then you just decided to go to windows phone after playing with a Focus S and now after getting your new phone suddenly you're going to start developing for windows phone. Sure.
RIM has already settled on QNX for its next-generation OS (their tablet runs on it), and I think they just don't have the software/UI chops to handle it either way.
I can see WebOS being concurrence/counterbalance to Android and W7P (mostly Android) for other phonemakers than Samsung (who already has bada)
QNX is the underlying RTOS. Application UI is done in Adobe AIR, which is a dead platform. JS/HTML5 on top of QNX would capitalize on their strengths (more responsiveness over Android) and patch over their weaknesses.
When the Playbook was launched, you could develop both AIR and HTML5 apps. All their other SDKs have been in beta ever since.
HTML5 apps are apparently wrapped in AIR internally, and maybe that's what made my app more laggy than in iPad Safari. But HTML5 app dev is nothing new for RIM.
> JS/HTML5 on top of QNX would capitalize on their strengths (more responsiveness over Android) and patch over their weaknesses.
We're talking about RIM here, how would web technologies (a game they are still late at) "capitalize on their streights"? Let alone "patch over their weaknesses"?
I'm guessing that nailer is referring to the fact that QNX is a realtime OS, which could provide decreased UI latency compared to Android. QNX is a "strength" of RIM, so using it to their advantage would "capitalize on their strengths."
As an aside, I always thought it was weird that QNX was owned by Harman for a while...
Continuing to use QNX's RTOS would capitalize on their strengths.
Having a application development platform that has actual developers and a growing community would path over the weakness of Adobe AIR, which has neither.
The PlayBook ships with a recent version of WebKit and all Blackberry 7.X phones contain a WebKit based browser. Starting with the Torch last summer most BB phones shipped with WebKit. The days of the Java based browser on BlackBerry's are over.
Please correct me if I am wrong, but that is not the main benefit of WebOS. I believe the main benefit of WebOS is that it supports HTML5/JS applications natively in the OS, and they are not bound by a browser frame.
Nobody wants to have to open a browser and load a bookmark to get to an application that has browser widgets taking up space at the top, bottom, and side of the screen. They want a home screen icon they can tap once and get an application with native look and feel. If developers can write that app in HTML5/JS then it's a win/win for both developers and users. Developers get a highly portable framework that allows them to rapidly develop software and users get a native app experience.
QNX is a micro kernel, theoretically they could support multiple application programming environments at the same time on the same phone, and they should. Ie they could now chirn out a phone that can support webos, rim and android apps simultaneously
While I agree I really don't see hardware manufacturers adopting webOS. Since webOS is now Open Source it would be much easier for them to adopt the innovations of webOS (particularly interface wise) and use it as a shell on top of Android. That way you get the Android marketplace and the advantages of webOS.
I guess HP could enforce the patents to keep those innovations locked to webOS but it's kind of hard to do that AND promote webOS as an open solution for people to use.
Maybe RIM could adopt it instead? They could really use a better UI, plus a platform that actually scales well to tablets. Plus they have a large enough install base that once they get rid of their disastrous programming environment developers might actually start writing good apps for their phones.