Interested in learning what's next for the gaming industry? Join gaming executives to discuss emerging parts of the industry this October at GamesBeat Summit Next. Register today.
How does BlackBerry plan to rescue its ailing mobile empire? Well, it’s not just banking on gold smartphones, it seems. It hopes regulation will help save its bacon.
BlackBerry CEO John Chen has revealed some interesting thoughts on the much debated subject of net neutrality, touching on what the definition of the term should encapsulate. And interestingly, he reckons developers should be forced to produce applications for all mobile operating systems, not just the big players such as Android and iOS.
This has been a perennial problem for both BlackBerry and Windows Phone, with many big-name apps either taking their time to arrive on the scene, or simply never showing up at all. And this is bad news for them, because apps are seen as being key to success, irrespective of whether the hardware is any good.
Generally speaking, net neutrality has come to define the principle that Internet service providers (ISPs) and the relevant authorities should treat everything equally — a single tier where no website, application, or demographic is given preferential treatment, particularly for financial gain. It’s all about protecting the free and open Internet.
Chen, however, says that net neutrality should be regulated at the “application and content layer.” In a letter sent to a number of high-ranking U.S. Senate figures, which was later adapted for a blog post, Chen says:
Neutrality must be mandated at the application and content layer if we truly want a free, open and non-discriminatory internet. All wireless broadband customers must have the ability to access any lawful applications and content they choose, and applications/content providers must be prohibited from discriminating based on the customer’s mobile operating system.
Chen goes on to cite Netflix, which has been a strong supporter of net neutrality at a carrier level, as one example of where companies fail to treat all operating systems equally. Indeed, the video-streaming service has hitherto failed to launch an app for BlackBerry, though it does have one for Windows Phone.
The CEO accuses Netflix of “discriminating” against BlackBerry customers, and “many other applications providers similarly offer service only to iPhone and Android users.”
“This dynamic has created a two-tiered wireless broadband ecosystem, in which iPhone and Android users are able to access far more content and applications than customers using devices running other operating systems,” says Chen. “These are precisely the sort of discriminatory practices that neutrality advocates have criticized at the carrier level.”
While some may argue that Chen has a point on a very broad level, it’s important not to confuse the issue of net neutrality here. ISPs charging some companies or consumers more than others to deliver faster Web access goes against the very notion of a “free and open Internet.” Actively forcing private companies to build an app for a specific platform simply isn’t practical on any real level, and would not work.
Who would these rules apply to? Just big companies with the resources to splash out on a BlackBerry app that will be used by so few people?
Think about it. There are thousands of indie developers out there, working away in their bedrooms to produce what they hope will be at least a minor smash hit on Google Play or Apple’s App Store. Are these individuals really expected to invest time and resources in learning how to build apps for a whole new operating system, one that will see very little in the way of financial return?
Even Android, which holds the lion’s share of mobile market in most countries, has had a tough time getting developers to adopt a “non-iOS first” mindset when building apps. But at no point has any sane person suggested that iOS developers be forced to code for Android. It would be nice if they did, sure, but it shouldn’t be legislated.
Chen even points to its own proprietary BlackBerry Messenger (BBM) service as one example of how BlackBerry has opened its own services to third-party platforms.
“Unfortunately, not all content and applications providers have embraced openness and neutrality,” he says. “Unlike BlackBerry, which allows iPhone users to download and use our BBM service, Apple does not allow BlackBerry or Android users to download Apple’s iMessage messaging service.”
Indeed, BBM finally launched on Android and iOS in 2013, meaning anyone could now message each other across different platforms. But this wasn’t done in the spirit of openness — BBM was one of the few BlackBerry offerings that still had a degree of traction on a consumer level, and this was its way of ensuring BBM didn’t die off.
Why did BBM take so long to land on Android and iOS? And why, after that, did it take so long to arrive on Windows Phone — almost a year later?
Chen also points to BlackBerry making its security-focused BES12 device management software available to iOS and Android. Again, BlackBerry has had to put a renewed focus on its software, making it available on multiple platforms — because its hardware business is no longer the force it once was.
To suggest that BBM or BES12 was launched on Android and iOS for any reason other than self-preservation would be disingenuous at best.
BlackBerry basically rested on its laurels and was blindsided by the emergence of Apple and Google in the smartphone realm — it failed to innovate quickly enough and it’s now paying the price. This has happened to many other companies through the foggy ruins of time — companies that failed to adapt and move with the zeitgeist.
BlackBerry has already been pushing hard to open up to Android apps, but this doesn’t cover all apps and doesn’t support things like Google Play’s in-app purchase functionality. So developers still have to re-jig things for BlackBerry.
HTML5 is becoming increasingly used on mobile, bypassing the need for native apps altogether, but native apps still rule the roost on smartphones. What Chen is probably hoping for is a common coding language that spans all mobile operating systems — so that developers can easily tweak their handiwork so that apps work like a charm on all devices. However, this is unlikely to happen any time soon.
Chen’s logic makes sense on a broad level. He argues that net neutrality should extend to content in apps, which is currently siloed by operating systems — and why should access to content be restricted by a lack of interoperability?
But if that’s the argument, then Chen’s target shouldn’t be the content and application providers, because they merely work within the limitations of the operating systems. To suggest for a second that there should be an official mandate that stipulates which platforms a developer should build for is crazy and completely unworkable.
VentureBeat's mission is to be a digital town square for technical decision-makers to gain knowledge about transformative enterprise technology and transact. Learn more about membership.