Developers Defecting From BlackBerry
jfruhlinger writes "Mobile app developers who build for multiple platforms need to figure out how to conserve their resources somehow, and many are choosing to do so by not bothering to build apps for BlackBerry phones. It's a combination of declining market share and the general difficulty of building apps for the BlackBerry platform, one developer told Bloomberg: 'RIM brought in a touchscreen and mixed it with a thumbwheel, a keyboard and shortcut keys, it made it really difficult and expensive to develop across devices.'"
You mean to tell me that developers have been making apps for BlackBerry all this time? I coulda' swore that every time I saw an app that looked really cool it was only available for Android or iPhone. I can't even get that Angry Ducklings app that everyone is singing about.
I once took an excursion to Reddit, and later HN. Unlimited up/down voting sucks when dealing with a hive-mind.
All thirteen of them said so.
There are developers for Blackberry? O_O
The only reason blackberry is still in existence is because corporations and IT teams don't want to migrate to a new platform. Blackberry phones aren't anymore secure than an Android of iPhone with the proper corporate sync apps installed. Like many products, it became a standard even though a new and better product took it's place.
I've been saying this for years. Developing on the Blackberry was a nightmare...and I wasn't even on that team. Good riddance.
I made an app! Shoutium
Considering that with the Playbook they added the ability to support apps written for Android, they could essentially decide to do the same for their phones. The experience may be diminished, but they'll still be able to provide access to a large amount of apps.
This also raises the question of whether or not RIM's decision to allow Android apps to be ported to the Playbook has further influenced developers to abandon creating native applications as they believe that in the future this capability might be extended to BlackBerry's phones.
This in stark contrast to Apple's decision to limit third party development platforms on iOS to a large extent should make for an interesting comparison several years down the road when we can see how these choices have impacted developers and their choices regarding whether to develop native applications for RIM devices.
The first SDKs? WebWorks and Adobe AIR, ffs... they're still promising a native SDK, not to mention the Java SDK, oh and did I mention they plan to support Dalvik apps as well?
So, unlike Apple and Android with their clean, unified APIs, we're gonna have, what, 4 BBOS8 (when the QNX platform is meant to take over) SDKs, plus Android app compatibility... good job making sure the developer community remains deeply confused, RIM. Well played.
What phone should I move to now?
I bought a PALM centro because it was easy to sync with Evolution on my Ubuntu Desktop. Palm began to lose market share rapidly. Then palm abandoned local sync with the Pre. Then palm got bought by HP, and has apparently disappeared.
So instead, I bought a Blackberry Bold, because it was almost as easy to sync with my Ubuntu desktop. Then Blackberry began to lose market share...
So tell me, slashdot, what phone can I move to now that will allow me to sync easily and locally with evolution on my Ubuntu desktop. (Local ethics rules and security concerns prevent me from using cloud services like google calendar)
Trying to use sarcasm in text-based forums does not work.
Considering that with the Playbook they added the ability to support apps written for Android
No, they said they PLAN to add that support. When it will be delivered? Who can say.
they could essentially decide to do the same for their phones.
For existing phones? The ones with no Android specific buttons? The ones that were never built intending to run Android?
No.
The reason all this matters is that there is no coherent story about BB development anywhere (since the tablets use Air and the phones do not), and what development was going on was with a nightmare API (I looked over it once to evaluate doing a port to BB and ran away).
Blackberry has the same problem Nokia did, BB is just much more entrenched and harder to shake loose. But they haven't done anything to firm up the grip they had, and when it goes it will go fast.
"There is more worth loving than we have strength to love." - Brian Jay Stanley
Where I work, we are strongly discouraged from loading any non-business-approved applications on our BlackBerry phones. As a consequence, I have never bothered visiting the Blackberry app store. If I had a business-approved iPhone I imagine it'd be the same way, but since BlackBerry's entire focus is on business I'd imagine these sorts of restrictions are hurting their app sales more so than for comparable devices.
Anyway, isn't Elops mission complete now? He's just waiting for Ballmers command to become RIM's CEO so they can all start using some crappy toy xbox-controller OS for the phones.
Hope Blackberry either dies a quick death or one of their two CEOs demands that the BB OS gets a revamp a la QNX from the Playbook ,either way they are on life support as it is. With their present buggy bloated platform that is years behind the modern mobile OS (android/ios hell even windows phone), this news of mass developer exodus comes as no surprise to me.
I've often been amused at how nothing has changed at RIM since the early 00's their hardware is a complete joke for a modern smartphone.
Shareholders are going to flee soon if this all keeps snowballing.
To me, BlackBerry's software was well-designed and reliable, and it allowed me to do pretty much everything I expect a communications device to do, so I couldn't really picture what else I'd need to download.,
That's because like every other Blackberry user I ever knew, you NEVER LEFT THE EMAIL CLIENT.
Not even to talk...
There's a whole world of interesting applications for a smart phone if you don't respond to emails the second they arrive.
"There is more worth loving than we have strength to love." - Brian Jay Stanley
On the plus side, you can't accuse RIM of being ignorant of this problem, or of not taking it seriously.
RIM's decision to support Android apps on their new QNX-based OS must have been very painful and probably resulted in a backlash from partners who had invested a lot in their existing app platform.
The upside is that the Playbook and the next gen of BB phones will have access to the vast store of apps that consumers want these days in spite of the lack of developer support described in TFA.
As a BB developer, you can't use the api's that RIM developers can use to build apps. While Apple and Google do what they can to make life easy for their developers, RIM doesn't seem to like their developers.
no, I don't have a sig
The BB is a secure smart-ish-phone which makes it ideal for corporate/government use. It's locked down and encrypted.
Right, it does all that and then sends everything through Canada BES servers.
Or sometimes has the traffic take a side trip through something like a Saudi scanner depending on what country you are in.
To my mind this is what will move a lot of companies to Android/iPhone, they actually have full control of the security, and do not have to wonder just what mode BES is in when execs go traveling.
I figure the government must have their own BES servers that are immune from such nonsense. but even they are going to iPhones in greater numbers.
"There is more worth loving than we have strength to love." - Brian Jay Stanley
A related headline that may help explain the developer story.
This post comes with a double-your-money-back guarantee!
Any offense taken to this post is at your sole discretion.
A couple of nobody app developers aren't going to do a BB app! It is the end of RIM!
What a load of shit.
Blackberry isn't dead yet! Just in the past few weeks, I've seen tons of signs on the highways here in eastern Tennessee advertising Blackberries! They're selling them by the ton! Oh, wait! Those are signs for the fruity variety, not the phones. Sorry, my bad! ;-)
Blackberry phones aren't anymore secure than an Android of iPhone with the proper corporate sync apps installed
I think security is a pretty small bit of it. I think it has more to do with BB enterprise applications, as well as the fact that the BB platform is pretty homogeneous. If you swap an employee between two or three different BB phones, you can count on the same desktop software working in the same way for all of them. You can also manage the remote data for all of them the same way.
In contrast, Android for all its strengths is a nightmare of conflicting setups. There is no consistent sync software that I've seen so far, likely at least in part due to all the different deployments of Android across the different vendors with their Android phones.
And then the iPhone. Even if you overlook that it locks you into iTunes, the iPhone does have one huge downfall in the eyes of some users - which other seem to consider a great asset. I'm referring to being completely dependent on the touch screen for everything since it has only one button on the entire phone. Some people still prefer physical keys, and a touch screen that makes a clicking sound won't do it for that.
Damn_registrars has no butt-hole. Damn_registrars has no use for a butt-hole.
With less and less attention being given to the RIM platform, it's just going to make it harder and harder to get a RIM job.
I think the difference with Android and iOS is that Google and Apple don't buy out the good developers. It seems like RIM consistently does it, and then makes it a part of their OS. This stinks of the Microsoft embrace and extend approach to development of a platform. To be frank, blackberries don't "need" many apps. They are designed to be mobile E-mail/Contact Convergence platforms for corporations that use Exchange or Domino server infrastructure. So when things like Twitter apps or Web Browsers are made by others that work in a way that can be integrated to this existing infrastructure, RIM buys the good ones and makes it part of the approved platform. This works really well for things like enforcing copy and paste consistency, or adding/updating contacts consistency. Those are both really really big problems in iOS and Android. Additionally, multitasking seems to save state correctly (I am looking at you android browser and contact manager). While it is fun to pick-up the girlfriend's Samsung and shoot some birds at some swine, when I try to switch between a browser and a contact manager to add contact information, or make a selection of an address to add to a contact, I don't have to start all over on my Blackberry Curve, but I do on her Samsung. It makes me cry sometimes how little integration tasks I am used to on the Blackberry are completely missing on the iOS and Android platforms, since the others have so much more overall potential. But RIM has a decade head-start or so, so they should probably worry they will go the way of the PalmOS if they don't get their act together.
Seesmic was a crap app on BB. They always treated it as an "oh by the way" platform, and it shows in their product. They face stiff competiton from UberMedia (ubertwitter) and RIM's official twitter client which included in in all new BB devices. When you have a poorly rated app that is among the worst offerings, it's no surprise that downloads decrease. And as far as the multitude of OS versions and devices - if you design your app poorly, it will be difficult to manage that for any platform. And if you design it well, it's really not a major hurdle. Especially for the bb devices - every os 4.x (barely used anymore) through the upcoming 7.0 is backward compatible; and is fundamentally the same OS. Consider programming for win 2000 v xp - the same basic os but new features in xp. If you develop for 2000 the app will work on xp - though if you want to use all the xp features you'll make a build to support it that will extend (in oo fashion) the work you've done for 2000.
I am someone who has made several BlackBerry apps, the most recently was last month. To me, this is no surprise. If anyone has actually worked with the BB platform at all lately, they wouldn't be surprised either. The first point that must be addressed is: you have to target BBOS 4.5 or 4.6 to reach the maximum number of devices. Now, you may say "well, I have to target Android 2.0 or 2.1, which is the same.", except, it's not. BBOS 4.5 and 4.6 are awful, and they lack many features. In fact, even BBOS6 still lacks may features (the platform). Part of the problem is they're using J2ME, whereas Android uses almost a full compliment of Java.
I'm not going to go into details about everything that bothers me about the platform, but suffice to say that it needs a real markup language for the UI (it has none right now, unless you count some hacks people have released), and it needs to update the default controls. They look terrible, and they feel severely dated. And there's just the little things, like the TreeField doesn't allow variable row heights (wtf?), and there's no workaround. There's also no API call in the framework to generate standard 128-bit UUIDs, so you have to write that function yourself.. You can't change the background on a forum without subclassing.
Sorry, looks like I did start to ramble. Suffice to say it sucks, and you spend the majority of your time re-implementing things that have existed for years, or fighting stupid bugs, or fighting the ridiculous emulators that carry no documentation and do not support hotswap.
Sorry RIM. I'm Canadian, but your platform sucks, and I really hope you get your shit together with the magical QNX release that may or may not come.
I used to work for the Rimstitution back in the stone ages...we had people that were SO desperate to get RIM's crap viewed as cool, and they'd regularly post here trying to drum up support since the late 90's even. Now that we're finally seeing the decline of RIM it's nice to see that Slashdot stayed the course and never bought into the RIM hype during their prime (pity about the endless Apple worship here though).
Oh and incidentally, I challenge the view that RIM phones were ever "smartphones." They were good at what they were designed for--messaging. The whole "app" thing didn't happen until everyone else was doing it. Appworld has always been an also-ran as a result.
R.I.P
Research In Motion
If they were smart they would get out of the handset business entirely, and focus on making a customized version of the Android operating system that supports the encryption, IT policies, etc that RIM is well known for and sell it as an OS on someone else's handset.