Friday may forever change BBM as we know it. (Can BBM on iOS/Android be 'turned off'??)
People always remark on the 'reliability' and 'immediacy' of BBM. Up until now, confined to and fully baked into the BlackBerry OS, there is no way of 'signing-off' BBM other than to shut down your device or disable radio connections. This has enabled the 'D'[elivered] and 'R'[ead] indicators to almost serve as a 'sign of life' of the recipient when one fires off a BBM. That is, if I send someone a BBM, and don't contemporaneously see a 'D', I know either they have their phones off, are out of coverage (in flight, etc.), or there is an issue with something along the communication path (i.e. the sending BlackBerry, the network, or the receiving BlackBerry).
This type of "if it's alive, it must have a pulse" 'inherency' of BBM is what has made BBM feel so much more 'connected' than any of the other third-party messaging applications available even on the same BlackBerry handsets. One concern that I have now that BBM is going to iOS and Android, is that, since it is not baked into the OS, its usefulness as the 'pulse' indicator of our devices will be lost.
So, my question for anyone that has any knowledge on this is: as long as the BBM app is installed (obviously an iOS/Android user should be allowed to uninstall it), will it be active as a background service that is always on regardless of whether a window or widget is open and running? Will users be able to 'close it', 'log off', or 'shut down BBM'?
OR are we sacrificing the very basic operating principles upon which BBM has become the most 'reliable' and 'immediate' messaging system, all in hopes of adding a few more friends to our increasingly lonely party??