Slashdot Mirror
The (Big) Problem With RIM
An anonymous reader writes "Research in Motion, by all accounts, had a terrible week. But things might get even worse. The Canadian technology company posted dismal quarterly earnings numbers, missing revenue and sales targets, while margins continued to shrink. Co-CEO Mike Lazaridis conceded the PlayBook had been thwarted by a lack of apps and content, not necessarily by a weak platform. Like Apple with its iOS, and Microsoft with Windows, creating a successful platform will be dependent on the eco-system it supports, but RIM hasn't shown ability to foster that."
Speculation has begun as to whether or not RIM will wind up having a PlayBook firesale in the same vein as the TouchPad.
I had a curve 8330 and predicted this years ago.
They had a funny policy of only releasing security fixes for their OS, meanwhile leaving out features that should have been in it from the beginning.
Simple things like being able to autosplit text messages, it couldn't do, simply capped you at 160 characters.
Or even being able to adjust the vibrate functionality on a text message notification to buzz once for half a second, had to buy an app for that. Shortest vibrate was 2x 1 second vibrations. Very annoying. Oh, and it couldn't vibrate and ring at the same time for a call. It would start the ringtone and in 5 seconds start the vibrate and kill the ringtone, then just continue vibrating for the duration of the call. Had to buy an app to fix that too.
I don't recall the rest of what they left out. I remember there were at least like 4 things that the OS desperately needed but that they wouldn't put in.
I believe their reasoning was "that way they'll buy the next phone hoping it's better with its newer OS", forgetting the part where if your current customer is annoyed with you, the last thing they're going to do is go buy something else from you. So then I got an android...
I ended up with a Playbook from winning a contest just about a year ago. I was super excited to get one -- all the specs were great and it seemed like a winning device. The conference I was at had only one, and they kept it behiend a glass case. They wouldn't let any of the devs touch it, but they handed out Playbook Emulators (software) that you could build apps against. Over the course of the next 4 months, the API changed soo many times, and the Emulator was so buggy that it was almost pointless to develop against it.
From that point, it was 6 months before I got the real device in the mail.
A lot of promises that made the device a best-seller still haven't materilized.
- It was said it was going to ship with the ability to run Android and old BBx Apps.
- It was said that devlopers could develop apps in native QNX. Such an SDK has still not been released, except for a few select partners (I've been a BB developer for YEARS, and thought I could make this list... I guess not).
- There were BB phones that were supposed to be released immediatly after the Playbook that ran QNX. This would allow devs to target one SDK / App development model for both phones and tablets. We have not seen anything about a new QNX phone yet.
- It was said that there would be a version that had GSM/CDMA capabilities coming... It's been bumped off their road map. You can either use WiFi, or tether to an existing BB phone.
- There is no 'smartphone' stuff in there. No Calendar, no Mail, nothing. You can tether to an existing BB phone and emulate some of those things, but if your phone is off, or out of range you loose those apps. Who pays hundreds of dollars and can't check your mail on a device!
- There has been a real lack of business apps. Still no SSH app, still no RDP app. No email, no word processor, etc. These are the things people will notice when they check out the devices in the store. If the developer eco-system wasn't supporting these types of apps, RIM should have whipped them up to fill in the gaps. They didn't, and they still don't exist.
- They've scared off most developers because of the way they run their program. You have to register your device with your program and download a developer 'token' that is only good for 30 days. Every 30 days you need to re-register your device to be able to deploy apps to it. Additionally, you have to bake those tokens into your app, which means that your apps can really only be tested for 30 day windows. To get your tokens approved it can take DAYS. Submitting stuff to the App World is a similar process as Apple, except you get more feedback when your apps get rejected.
Now, all that being said, hardware wise I think the device is REAL nice.. One of the best tablet screens I've ever encountered. I love the gestures (the borders of the device are touch sensitive, and most of the gestures you use with the device orgionate from there). The web browser is really solid, and the multi-tasking works very well. Because of the screen, it's one of the few devices I can read a full newspaper on without having a lot of strain on my eyes. The OS is also beautiful too -- and much better laid out than iOS or Android. The battery lasts about 8 hours of continious use, which is great for a device like that.
That being said -- I don't use it every day. I don't even use it every week because the lack of apps to do my work. At this point, it is a glorified web browser and that's about it. Give me the ability to do my day-to-day job (like I can on the iPad or Samsung tab), and it would be the device to carry around. But not until then.