RIM: Shooting themselves in the foot.

My new startup is well on its way. igotihav now has a website, a Facebook app, and an iPhone app. You’ll be hearing more about it now that I have time to blog more.

Apple took a while to approve the app. While I was waiting I completed most of the Android version. It’s in test now and will be coming soon. In fact, I had so much time that I decided to take a look at a BlackBerry version.

I had heard horror stories about developing apps for the BlackBerry but just assumed that it was a bit more difficult than Android. After all, it was Java, and they did have an Eclipse plug-in, right?

Well I’m here to tell you, all of the stories were right. I suppose this should have been my first clue:


That’s me attempting to log in to the BlackBerry Developer Zone and failing. And there is no place to "contact the help desk" by the way. When I emailed the webmaster I got this response:

Thank you for contacting BlackBerryTechnical Support. The email you submitted has not been delivered. Please find many alternative support options below.

Hmmm. That was helpful. Not.

Oh well. So I downloaded the tools. I use Eclipse on my Mac so it should be fine. Wait. PC ONLY? Seriously?

Ok, so I’ll run under Parallels.So I install Eclipse and fire it up. But it doesn’t work so well with the BlackBerry simulator. RIM recommends their Java Development Environment(JDE). So I install that, and it works a bit better.

The simulator is another story. It seems that each version of the simulator is for a different OS version, and mocks up a different RIM device. I’m working in OS 6.0, so my simulator pretends to be the Torch 9800. Hmm. So that means that I can’t test my 6.0 code on a Bold? Or any other non-touchscreen device? Oh and it takes about 10 minutes to start up. Just imagine how many coffee breaks I’ve had in the past two weeks.

Fine. So I write some code, and things are humming away when I run it. Until I start to debug the code. Then the simulator starts throwing all kinds of exceptions around. Null pointer. Illegal state. You never liked my mother. Oops, sorry about that last one.

And this little gem:

BlackBerry JVM Error 545

And my favorite one of all:


That one happened repeatedly whenever I typed a key into an EditField. So I switched from EditFields to TextFields. No visual cue that you should be entering text there in either case, but at least the TextField didn’t blow up. And these aren’t little blow ups. They require me to restart the Parallels virtual machine – reboot basically.

Then I tried to set a border on the field. The JDE walked me through the setBorder() method perfectly. Unfortunately the compile insists that even though the JDE thinks that it is there, it is an unknown method, and therefore simply will not work.

I’ve banged my head against the wall for two weeks trying to get these things to work and I will eventually prevail; I don’t give up that easily. But I have a point in writing this.

RIM makes a wonderful email device; people clearly love it. But though they aspire to be more they seem to be failing miserably at it. For a company that has been building BlackBerries for over 10 years, their SDK is abysmal, and their tools just awful. Their look and feel lags both Android and the iPhone, by at least one technology generation. I can forgive their PC only mentality as it is still dominant, but tools that have been around for years should work much better.

Forgetting the iPhone for a second, I was able to write the bulk of my Android app with fewer lines of Java code resulting in a much prettier and better working interface. The BlackBerry version looks like an old-school DOS application by comparison.

The best money RIM could spend would be to hire four or five bright developers and fix their SDK. Just match what Android does, because that should be enough for now. Worry about iPhone later because they are just out of their league right now.

And really, fix all of your products like Developer Zone. When I told people that I was developing a BlackBerry app they all asked "Why?". You really don’t want to alienate the developers that you already have.

Stop shooting yourselves in the foot.

I’ll try to keep you all updated on my progress. And if you’re from RIM and want to talk to me, feel free to email me at larry@larryborsato.com. Even if you don’t agree with me.


Powered by Bleezer

3 thoughts on “RIM: Shooting themselves in the foot.

  1. Larry, insightful blog, and really echoes the common experience with BB dev. I recently launched an iPhone app, Nocturnal, and now contemplating BlackBerry, but with a bad taste in my mouth for what’s ahead. Time will tell.

    On a side-note, you might find some great help and insight at Mobile Innovation Week taking place in September in Toronto (mobileinnovationweek.com) . I’ll be attending. Check out the FITC module, should be a great fit for what you’re going through.


  2. Hey Larry,
    from my run-ins with RIM it sounds like their primary support mechanism is the support forums (that’s where their community managers roll). They actually do have a lot of non-rim champions who will provide answers pretty quickly there, and if you don’t get a response for a few days, that’s when a community manager should jump in to help. They also have some technical RIM people answering questions that the community cannot and doing a bit of advocacy.

    That being said, I’m not sure how in the workflow of an average developer that it’s made obvious that this is the first or best place you should go as I doubt everyone’s first inclination is to post on a public forum when they can’t get things to work, but I think they have the mindset that if you are doing self-service, you would probably search the forums, perhaps knowing you won’t get help any other way.

    To their credit, from what I’ve seen and heard, they’ve managed to build a strong community in the forums, so perhaps give it a try and perhaps you’ll find some answers, or at least a place to provide your story for them to see (I believe I saw a thread for that, and there was some good horror stories that are in there).


  3. Pingback: The PlayBook Launches, RIM Plays Catch Up « Spark

Leave a Reply