Blackberry Connect, Success or Doomed to Fail?

Comments

Blackberry Connect the software from RIM that allows 3rd party hardware manufacturers like Palm and Nokia use Blackberry push-email technology was suppose to be the next big thing for RIM. It would allow RIM to concentrate on being a software company, which they always claimed they were even though 70% of their revenue comes from hardware. But the main reason to see Blackberry Connect succeed is that it will cement RIM’s Blackberry technology as the de facto standard when it comes to push-email. After that it would be almost impossible for anyone to topple RIM, much like how Microsoft has dominated the desktop OS market for years.

It’s a smart tactical move for RIM and it seemed like RIM is/was going to get to that point eventually. The first pictures of Blackberry Connect running on the Palm Treo surfaced during the 2005 3GSM World convention and resurfaced again at this year’s convention. The 2006 pictures showed Blackberry Connect was ready but it needed to be certified both by Palm and RIM, a process that can add months onto the already long wait. Palm users are the most excited group to see Blackberry Connect but after years of waiting you have to wonder if they would still care for it when it finally comes out.


There have been a few phones that have released with Blackberry Connect; Sony-Ericsson P910, Siemens SK65, several Nokia devices, and the O2 Xda II. However, none of these devices have been big hits and users wanting push email would rather just buy a Blackberry model outright, instead of one running Blackberry Connect.

With Nokia, they first launched Blackberry Connect in Europe with the Nokia 9300 in 2004 and eventually brought the device to North America this year. But with software issues and technical glitches non-related to Blackberry Connect, the phone has been a very slow seller. Nokia will try once again with the new E-Series phones to be release in a few weeks but you have to wonder how much backing Nokia will give to Blackberry Connect, especially after they spent $430 million buying Intellisync.

That brings us up to the question of why would any of these company want to seriously back Blackberry Connect? Nokia has Intellisync, Motorola is coming out with the Q which runs on Windows Mobile, and Palm has been doing fine without Blackberry Connect and has teamed up with Microsoft for the Treo 700w.

  • Rod Pearson

    One of the problems with the Connect licensing is that there is no provision requiring licensees to support RIM’s IT Policies. They are free to support or not support which ever items they choose. This is a big issue for Enterprise IT shops where mandatory IT Policies are one of the major reasons RIM is the market leader in this field

  • Rod Pearson

    One of the problems with the Connect licensing is that there is no provision requiring licensees to support RIM’s IT Policies. They are free to support or not support which ever items they choose. This is a big issue for Enterprise IT shops where mandatory IT Policies are one of the major reasons RIM is the market leader in this field

  • George

    One point I think you fail to mention is that the lawsuit with NTP and RIM could be reason why Blackberry Connect was so slow to being adopted. There was major issues with it and the hardware companies didn’t want to get sued themselves! Blackberry Connect first came out in 2004, which would of gave RIM 2-3 years to promote their technology before any real threat came along, see Microsoft.

    If Blackberry Connect fails, you can totally blame it on RIM not settling with NTP sooner.

  • George

    One point I think you fail to mention is that the lawsuit with NTP and RIM could be reason why Blackberry Connect was so slow to being adopted. There was major issues with it and the hardware companies didn’t want to get sued themselves! Blackberry Connect first came out in 2004, which would of gave RIM 2-3 years to promote their technology before any real threat came along, see Microsoft.

    If Blackberry Connect fails, you can totally blame it on RIM not settling with NTP sooner.