Linked by Thom Holwerda on Wed 30th Jan 2013 23:06 UTC
PDAs, Cellphones, Wireless And so, today, RIM announced its Hail Mary - a brand new mobile operating system (well, sort-of new), as well as two new devices. In addition, the Canadian company also officially changed its name from Research In Motion to Blackberry. The first few reviews of Blackberry 10 are already out, and it's not bad. The problem, however, is that in the case of Blackberry, 'not bad' could easily mean 'not good enough'.
Permalink for comment 551023
To read all comments associated with this story, please click here.
RE[2]: My thoughts
by Nelson on Thu 31st Jan 2013 13:28 UTC in reply to "RE: My thoughts"
Member since:

As you wrote its the first iteration and going to improve. It already improved a lot according to those I know who had access to that before and gave it tries (like on the Playbook).

To try to get the Android ecosystem aboard is a very good strategy. The execution seems to be not finished yet but if it is it will pay out.

I don't know how good of a strategy it is. It is supposed to be a short-term fix. Android ports of popular apps while they convince people to write native BB10 apps.

However if it wont be ready in the short term, then its pointless.

What the hell kind of experience is it to have an app store filled with a bunch of foreign feeling apps, which do everything from text selection to navigation using a different UI paradigm than the host platform. That's nonsensical.

For the platform-integration: That is a vital point in many cases but in some its not that important. Games for example. If they are stable and reasonable fast its enough reason for that bridge to exist and to be supported and delivered on the devices.

Games are a small exception, but again, if performance isn't up to snuff, its a moot point. There is no advantage at this point in time.

With Android, HTML5, Qt, native and AIR they seem to offer a rather bright set of very different ways to get apps on there platform. This I see as very unique selling point. It decreases the investment needed to bring apps to there platform and maintain them in many cases. Taken the small market share it may still not be enough to convince everybody to bring there apps over but I think it still decreases the burden significant and so ROI can be reached faster.

I disagree with the direction, but I can understand why they chose to do what they did. It isn't easy to bootstrap an OS.

I just wonder how many AIR apps exist to matter, or how many meaningful HTML5 apps (I'm still waiting for someone to point me to one good HTML5 app) are ported.

I'd be interested in the breakdown between Native, HTML5 and Android ports on BlackBerry World.

If the dev-story is improved future, like better Android integration, then I think its a huge advantage and the fruits become a selling point. My hope is many more platforms start similar projects to easier developers work. Its the way to go.

This Android compatibility everywhere needs to die. This is such a terrible idea from a UX POV that its not even funny. It is almost beyond words that a developer is able to sleep at night knowing that they did some half-assed port of their Android app.

BlackBerry's QML based native platform is very good. They just need to convince people to use it, and not port their Android garbage over.

I'm worried about how BlackBerry World will look a year from now. Potentially a bigger wasteland than the Android app store.

Reply Parent Score: 3