1 min read

BlackBerry not worried about Boeing’s self-destructing smartphone


Media reports are calling it a potential BlackBerry killer, but the Waterloo, Ont.-based smartphone manufacturer doesn’t appear to be concerned.

According to published reports and a filing posted to the web side of the Federal Communications Commission (FCC), aircraft manufacturer Boeing is developing the Boeing Black (H8V-BLK1), designed to be a smartphone primarily for secure communication between government agencies and their contractors.

Boeing said last year it was working on an Android smartphone, and the FCC filing offers more insight. The device will be a dual-band SIM phone supporting GSM, WCDMA and LTE using Miro SIM cards, and will also feature an HDMI port, USB, WiFi and Bluetooth.

The handset would appear to target a key segment of BlackBerry’s core market – enterprise customers with a need for highly secure communications. However, Jeff Holleran, senior director of enterprise product management at BlackBerry, told CDN the Boeing phone isn’t really a threat to their business.

“From what I’ve seen in the press, Boeing is working on a self-destructing phone,” said Holleran. “That’s something that’s super niche, and isn’t something the customers we’re looking at from regulated industries would be interested in going after.”

The self-destruction refers to the Boeing phone’s non-serviceable design, which would see the hard drive wipe and the phone become unusable if the sealed back was removed or the phone was tampered with.

1 Comment

  1. This phone sounds a little redundant to me. Most MDM software, including BES, allows you to remotely wipe your device so the self destruction is old news. BB10 allows full device encryption and password protection so if you try to unlock it 10 times it wipes the device ie. self destruction. The most important question about a device like this is what it does when a user installs a compromised app, which is where the real security risks are.

Leave a Reply

Your email address will not be published. Required fields are marked *

Post comment