BlackBerry Messenger

~ how it started ~

BlackBerry Messenger (BBM) launched on August 1, 2005 as a feature on BlackBerry handsets running RIM's proprietary OS. By 2010 it was the dominant messaging platform among certain demographics: corporate workers, urban teenagers in the UK and parts of Asia, the Saudi business class, the Indonesian middle class, the Caribbean youth. At peak it had about 91 million active users.

RIM (BlackBerry) released BBM for iOS and Android on October 21, 2013, in a desperate try to compete with WhatsApp, but by then it was too late. WhatsApp had won. BBM Consumer was retired on May 31, 2019. BBM Enterprise (a paid version for organisations) continues in 2026 as a niche corporate product, run by Emtek (an Indonesian company). The cultural moment of BBM ended about 2014.

~ the rap sheet ~

~ the PIN ~

Every BlackBerry handset had a unique 8-character hexadecimal PIN. Adding a contact on BBM required exchanging PINs, you scanned a barcode, typed in the PIN manually, or sent it via SMS. The PIN was, your BBM identity, separate from your phone number.

The exchange of PINs became, briefly, a social ritual in its own right. Two professionals meeting at a conference would, in the 2008-2012 era, often exchange PINs before they exchanged phone numbers. Two flirting students at a university in Manchester or Mumbai or Riyadh would write each other's PINs in notebook margins. The PIN was, paradoxically, both more anonymous than a phone number (no link to your country, your carrier, or your name) and more intimate (it was bound to your specific physical handset).

When BlackBerry launched BBM on iOS and Android in 2013, they kept the PIN identity. New cross-platform BBM users got a generated PIN that was bound to their account rather than to a handset. The cross-platform PIN had less of the original feel; it was, just an opaque username. The original PIN's tie to a physical device gave it gravity that the iOS/Android version never recovered.

~ R / D ticks ~

BBM's defining UX feature was the R/D status ticks. When you sent a message, you saw:

• (no tick), sending
• D, delivered to the recipient's device
• R. Read by the recipient

WhatsApp's blue ticks (introduced in 2014) are direct descendants of BBM's R/D system. But BBM had the system first, and made it more central to the experience. The transition from D to R was, for a generation of BBM users, the moment of social anxiety. You sent a message. You watched the D. You waited for the R. The R appeared, then... nothing. Why no reply? Are they typing? Have they decided not to reply? Are they in a meeting?

The R-without-reply period defined a particular kind of digital interpersonal stress that did not exist before BBM and persists in modern messaging. The original BBM R/D ticks, however, came with an implicit social contract: serious users replied promptly. The platform was used for business, and not replying was considered rude. Modern WhatsApp blue ticks have lost this social weight; the R-without-reply has become normalised.

~ where bbm dominated ~

BBM's user-base distribution at peak in 2012-2013 was geographically distinctive. The dominant markets:

• Saudi Arabia, UAE, Kuwait, Qatar. the Gulf business class lived on BBM for almost a decade. Royal families. Government officials. The phrase "BBM me" was Arabic-English code for any kind of confidential exchange.
• Indonesia. By 2012, Indonesia had over 12 million BBM users, more than the United States. BBM was, briefly, the de facto national messenger.
• Nigeria. Wealthy and middle-class Nigerians used BBM widely. The platform was associated with status (BlackBerry handsets were expensive in Nigeria in 2010).
• Caribbean nations. Trinidad, Jamaica, and other Anglophone Caribbean countries had unusually high BBM penetration.
• UK urban youth. The 2011 London riots were, famously, organised partly via BBM. The encrypted, peer-to-peer messaging was harder for police to monitor than SMS or social media.
• The corporate world globally. Wherever executives carried BlackBerrys, BBM was the default in-company messenger. Many multinational companies had de facto BBM cultures from 2008 to 2014.

~ the london riots ~

On August 6-10, 2011, riots broke out across London and several other UK cities following the police shooting of Mark Duggan. The riots became the largest civil disturbance in English memory in a generation. They were also, notably, organised in major part via BlackBerry Messenger.

BBM's encrypted, peer-to-peer architecture made it harder for police to surveil than SMS or open social media. Rioters could broadcast group messages to dozens of contacts at once, coordinating which areas to target, when to gather, and when to disperse, though the pattern was widespread enough that the British government considered, then declined to enact, emergency powers to suspend BBM service during the riots.

The episode was BBM's last major cultural moment of dominance, because it showed that the platform was more than a corporate communication tool; it was a serious social infrastructure. It also accelerated, ironically, public awareness of BBM as a privacy-preserving alternative to other messaging, an awareness that arrived just as BBM was about to lose its installed base to the iPhone.

~ the slow goodbye ~

BBM died with BlackBerry's hardware collapse. Once corporate IT departments moved their employees from BlackBerry to iPhone or Android (a transition that happened in most large companies between 2010 and 2014), the user could no longer message colleagues over BBM, which is why the network effects unwound.

The 2013 cross-platform launch of BBM on iOS and Android was a Hail Mary. It worked technically, the apps were decent, but the user-base migration had already happened. People who had used BBM as the corporate default were now using whatever their new iPhone came with (iMessage) or whatever became dominant in their region (WhatsApp in most of the world, Line in some Asian countries, KakaoTalk in Korea).

The 2019 consumer shutdown was, by then, mostly a formality. Most active users had migrated away years earlier. The shutdown announcement on April 18, 2019 caused a small wave of nostalgia in BBM's holdout markets (Indonesia particularly), but no organised campaign to save it.

~ the hole it left ~

The PIN-based identity. The PIN was a username decoupled from your phone number, your email, and your real name. Modern messengers use phone numbers (WhatsApp, iMessage) or email addresses (Telegram, Signal). The ability to have a messaging identity that wasn't tied to a personally-identifying piece of contact information has, mostly, gone away. We are, in 2026, more findable than BBM users ever were.

The encrypted-by-default messenger. BBM was end-to-end encrypted from launch in 2005. WhatsApp didn't add E2EE until 2016. iMessage was encrypted from launch but only worked between Apple devices. BBM was the first widely-used cross-handset encrypted messenger. The "encrypted by default" feature took the rest of the industry a decade to catch up to.

The corporate weight. There is no current consumer messenger with the corporate gravitas BBM had. iMessage is for everyone. WhatsApp is for everyone. Slack is enterprise-only. The middle space, a messenger that was used for serious business but also worked for personal texts - has not been recreated.

~ words from mourners ~

"my BBM PIN was 2A1B5C9D and i still know it by heart in 2026. i do not know my own current home phone number. some things etch themselves harder than others.". m.ö. 42

"my entire freshman year of university (2010-2011, manchester) was on BBM. when i got an iPhone in 2012 and migrated to iMessage, i discovered that about 60% of my friend group used different messengers. it took two years for the network to converge on whatsapp.". a.t. 33

"i was a saudi banker from 2008 to 2014. BBM was the only messenger our entire firm used. when our IT department migrated everyone to iPhone in 2014 my whole social and professional network was thrown into the air. some people i had BBM'd daily for six years i never spoke to again because they did not migrate to whatsapp at the same time.", k.s. 47