RIM Offers BlackBerry Service Without the BlackBerry
TheCybernator writes "RIM has announced that they're essentially planning to offer BlackBerry service ... without the BlackBerry. The company plans an app suite that will turn its push e-mail technology into a platform for Windows Mobile 6 devices. Less than a week after a network outage crippled BlackBerry users across North America, Research In Motion announced an application pack for Windows Mobile 6 devices that Canadian software developers said will intensify the competition for push e-mail. The firm has said that the BlackBerry Application suite will appear as an icon on the screen of the Mobile Windows device and load BlackBerry applications such as e-mail, phone, calendar, address book, tasks, memos, browser, and instant messaging. RIM said users will easily be able toggle between the two platforms, one of which would have a BlackBerry-style interface."
I mean, I'm not a crackberry head, so I haven't looked that hard, but I'm sure my rep told me it was coming "real soon now" for the Treo when I bought my 650 a couple of years ago.
Did it not materialize?
Do daemons dream of electric sleep()?
I suspect RIM is falling into the trap of believing that they can reduce winCE to a "poorly debugged set of device drivers". However, others have tried that path and failed.
For gods sake RIM, don't do a palm/netscape
There are shills on slashdot. Apparently, I'm one of them.
on my Nokia 9300. I don't use it, but the client is definitely installed.
This phone doesn't appear to be very popular in the U.S., but it's the most useful phone I've ever owned.
Got Trader Joe's? friendwich.com RSS feeds work now!
What is "push email"? (Seriously.)
http://www.palm.com/us/software/blackberryconnect/
Blackberry Connect...
BlackNova Traders
Great! A service I would never pay for is now on two different platforms! Now people can be even more annoying during meetings!
http://twitter.com/OLDTELEGRAM
Of course, that was a very limited time offer.
The simple truth is that interstellar distances will not fit into the human imagination
- Douglas Adams
Imagine: The service worked virtually flawlessly for years, and just a week before the announcement that they will be integrating Windows devices, it all goes crashing down.
RIP RIM.
You're nothing; like me.
Wish they would open up their platform to other email systems. Why limit it just to Microsoft junk.
It looks like "push email" works off a relatively new IMAP protocol extension.
1. Client connects to server, sends "IDLE" command
2. If/when server has mail for that client, it sends a message back through the connection opened (and left open) by the client
3. After getting a "there are messages for you" message, the client REALLY downloads the actual message (over same IMAP connection?)
4. Upon timeout, etc., client issues "DONE" and/or reconnects
Nice whitepaper:
http://www.isode.com/whitepapers/imap-idle.html
RFC 2177:
http://tools.ietf.org/html/rfc2177
I read the Wiki article - it's pretty weak. (For example, it generally seems that messages are not really pushed out to clients, but the notifications are.)
= 18854827
I think I found a white paper that explains at least the standard-based IMAP implementation better...
http://it.slashdot.org/comments.pl?sid=232039&cid
Apple's offering to the phone world, the iPhone, as well as competing smartphones, may be convincing RIM to make itself more of a wireless communications service than a PDA provider. Palm is an excellent example of what can happen if you hold on too long to your own OS and not extend yourself when competition (Windows CE/Mobile) arrived.
PDAs and phone functionality were blending fast before the iPhone was announced. Although it's still vaporware by definition, the iPhone's introduction is changing the competitive landscape. It's in RIM's interests if they can made any of their services with any phone, although the use of Berries would likely be preferable.
Vos teneo officium eram periculosus ut vos recipero is.
I wonder whether they implemented their WM apps in Java. If so, this probably wont catch on any faster than it will be able to send an email with a 50k jpeg attached... Also, it would be fun installing another VM (in addition to the mandatory .net 1.0 VM, which nothing in the universe uses) on a device with a maximum of 64mB of flash.
It would make me smile to run java on a segmented memory architecture, however. *wince*
(I am so incredibly unlucky that my job is to play in the guts of WM daily. I have never seen a more slipshod, written-by-isolated-teams-in-Bangalore OS... Oh God, and the design decisions made by MS US take the cake. No close button? Segmented memory? Useless, expensive binary signing? Fragile aygshell? Broken wait for multiple mutex / event functionality? Bugs, bugs, bugs, bugs, bugs, bugs, bugs, bugs, bugs, bugs, bugs, bugs, bugs, bugs, bugs, bugs, bugs, bugs, bugs, bugs, bugs, bugs, bugs, bugs, bugs, bugs, bugs, bugs, bugs, bugs, bugs, bugs, bugs, bugs, bugs, bugs, bugs, bugs, bugs, bugs, bugs, bugs, bugs, bugs, bugs, bugs? Intentionally obfuscated POOM fields? Broken POOM data change notifications? Total divergence between behavior and documentation? Yup. WM surely has it all.)
I don't get it, if I was running a windows device with outlook already installed, why would I bother w/ blackberry's apps?
BlackBerry Connect's big problem was that there was no concept of a hardware ID - a 'PIN' in BlackBerry terms. PIN-to-PIN messaging is popular because it is fast, reasonably secure (doesn't use the Internet) and shows when the receiver gets the message. BB Connect didn't support it and I suspect that's part of the poor uptake of the service. If this doesn't either then I see no reason to use it instead of the push messaging on Windows Mobile, particularly with the overhead of the BB JVM running inside another VM...
Microsoft: We're worried about this iPhone thing eventually getting into the business marketplace.
RIM: We understand, but we don't think it's a big deal right...
Microsoft: Do you want us to give you the chair?
RIM: No sir.
Windows Mobile already provides Push email through MS Exchange via DirectPush. Exchange is by far the most common groupware app, so I don't see who they're targeting with this service, at least running on Windows Mobile. Perhaps Lotus Notes people, or other esoteric implementations, but those are dieing off quickly. Who's actually going to be buying this?
"The guide is definitive, reality is frequently inaccurate."
It's similar to IMAP IDLE expect that the phone doesn't need to keep a connection open.
The thing is, 'keeping a connection open' is just an abstraction. It's all really just a set of counters and data structures, there's no connection. A 'push e-mail' system talks to a socket listener, but that's just an abstraction too - the kernel sends the incoming packets in a different direction.
That's not to say that cell phones have as efficient a way of handling an idle TCP connection as they do on their notification level, but that's a different layer. There's no real reason that they couldn't implement that layer intelligently, making IMAP IDLE just as good. I think this is some of the frustration Apple must be running into with the iPhone and why they have the X deal with Cingular for a couple years, so the network layer can get some fixes to allow modern computing on it.
My God, it's Full of Source!
OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
Cool,
First they offer us the Blackberry without the network, now they offer us the network without the Blackberry. What next? No network and no Blackberry?
Hey, I've already got that upgrade!
"You can't fight in here, this is the war room!"
The big problem, from a enterprise standpoint, is that WM and Exchange do not allow you to encrypt removable media! From everything I have read on this new RIM "service" I do not see where they address that issue either!
In a secure enterprise environment, until someone addresses this (and Exchange 2007 & WM 6.0 do) WM is just too big of a security risk to let in the door of an enterprise class network. This is the main reason that RIM has won out so much in the direct-push battle.
With RIM's BES, Enterpises can control their end-to-end user experience with over 100 cofigurable security policies. WM and Exchange just cannot stackup yet.
Personally, I HATE the RIM service, the BES that puts an extra 4x the IOPS on my Exchange server, and the RIM devices. I am actually an advocate of WM and Exchange and would LOVE to see it in our enterprise environment but I cannot recommend we implement it until we have plugged the security holes.
And for all you haters, I own an 8800, a Treo 750 and an E62. I am a sys admin with over 10 years experience. I run our Enterprises Exchange, AD and BES environments. So yeah, I do know what I am talking about.
My company uses BlackBerries and we recently hired a new field operative who had his own Treo. Given the choice of installing an app on his Treo that will interface with our BES installation or having to purchase a new BlackBerry handheld unit for him we would rather just install a software package on his device. The fewer server applications & configurations we have to support, the better.
He has a windows CE enabled phone and we could place this app on his device while he's here and enable him to the BES and when he leaves uninstall it. It makes perfect sense to me.
Ask not what you can do for your country. Ask what your country did to you
I've been avoiding anything stamped blackberry because I've heard they don't work well with linux -- both sync client software and postfix/cyrus-imap servers. Is this still the case? The blackberry pearl looks like it might be a neat device but there doesn't seem to be much information about them online.
I'd be interested in hearing both success and horror stories.
Thanks.
You no longer need to die to go to hell! RIM is bringing you hell on earth!
Seriously though, does anybody think that the Blackberry UI is awesome? Does the Blackberry really have any fans? I've never met one, though I've met numbers of the opposition, and am one myself.
I would have to say that integration will be absolutely key to the success of failure of this product. The Windows Mobile platform tends to be very tightly 'woven' together, so that the applications can share data. If someone doesn't like/use their address portion of th software, but they still want integration with the e-mail and scheduling application -- it has to be there. On top of hat, I could see potential problems with "brand" dilution. If the device is no longer the Blackberry, you may find some aren't as keen because it isn't "a Blackberry". That being said, I will bet alot of companies will at least look into this, since it allows for more flexible development and greater productivity.
The point is that RIM tried for Windows compatibility, did a software upgrade, and their system crashed. We should tell them to STOP.
If there's an upside here, I'm not seeing it.
I've got - and had - loads of mobile gadgets. Most have disappointed me in some way or the other.
I always resisted the Blackberrys beacuse they were big, nerdy and expensive for just one 'killer app' - email push. Cracked for the new Pearl, though. It is great - 10 mins after unpacking it I was receiving mail. Also, it's small enough to be a convenient phone, decent 'gimmicks' like media player and camera and the email interface is fine - great for dealing with small mails in otherwise 'dead' moments. Google maps works great too - downloaded and installed in less than a minute. (Will we see apps like that on the iPhone?) I genuinely prefer it over my WM device, which I see as more of a 'toy'. One day I'll probably get a Linux smartphone to waste time playing with, but for serious business I need something like the Pearl - it 'just works'...that's 'awesome' enough for me.
Of course, for 'heavy' emailing, nobody in their right mind is going to use a 'berry or anything else - just fire up the laptop.
It's ironic that when RIM finally gives us a decent terminal, they feel pressured to widen the market by offering their service on other platforms. Having said that, I do miss the integrated GPS of my WM device, so...
yeah if i am mobile I want an unlimited data plan anyway so explain to me why push email is such a good thing - as opposed to say IMAP etc? Blackberry - people like you for the hardware not the service.
So kinda like Netscape trying to make the Internet the operating environment for the user, and the OS just "that thing in the background that keeps the machine running"? Good luck on this one, RIM. I foresee a future of random "unexplainable" crashes, connectivity glitches, and slow UI responsiveness for your software just as soon as the next update for Windows Mobile 6 comes out of Redmond.
I don't see why you need anything from Blackberry; many E-mail clients and servers support IMAP IDLE, which gives you the equivalent of push email.