Replacing blackberry? The Mobility stack and the new revenue model

I’ve been working on some ideas about trying to graphically represent the complexity involved in the mobility world as the enterprise and the enterprise user move from the known and loved (?) environment of Blackberry  , to the unknown, complex, costly enterprise mobility space.

I’ve spoken and written on this subject recently, see the water’s presentation at my speaking page. The theory is that the supply chain is relatively simple when the enterprise chooses Blackberry.  The graphic below shows the typical components the enterprise needs to think about when provisioning even the basic applications (email, calendaring etc) onto the device. These are usually (as the diagram shows below on the right) limited to 2 or 3 suppliers such as  Blackberry, the Mobile carrier and perhaps Microsoft (if they supply your email server).

Supply chains for Enterprise mobility with blackberry.

Supply chains for Enterprise mobility with blackberry.

The problem occurs when you move away from the blackberry ecosystem and introduce a variety of devices into the enterprise. Typically the non-blackberry devices are not controlled and the moment you introduce enterprise data onto those devices the stack starts to become complicated. Working from the bottom up here are some of the reasons for this complexity;

Network access (red) – Often a managed blackberry device will come with a corporate mobile tariff which is often enabled for global roaming. One thing blackberry were very good at was making the effective use of network bandwidth using their protocols. As soon as you move out of this environment the user & corporation have to think about a) can they get a global mobile tariff with roaming that is not cost prohibitive.  b) If not perhaps you will also need to sign up for a Wi-fi service as well (such as boingo or iPass) to reduce cost.

Enterprise security (green) – Accessing your corporate data will require your organisation to support some security gateway that allow you to connect. This is big business for enterprise security firms. This will most likely mean you have to connect to a VPN gateway for web services gateway to receive your services.

Device and applications security (purple) – As part of the security policy of the enterprise you are likely to need to ensure the corporate owned data on your device is secure. This means the corporate has the ability to wipe that data if you leave or the device is lost, as well as apply policy to those applications (e.g. geo-fencing policy, time limited access). Most commonly this has been known as the Mobile Device Management (MDM) marketplace but it now includes how the device accesses the corporate network.

Applications – personal (blue) – Many individuals already have communications apps on their devices (e.g. Skype, google voice). Does the corporate allow these communications apps to be used for business?

Enterprise mobility stack vendors - shared

How much is the mobility pound shared

Applications – corporate apps (blue) – The enterprise will be making more and more app

lications available to mobile devices, this starts with communication apps, email, calendaring, contacts but then quickly extends into corporate IM, video and voice, filesharing, sharepoint etc.

So what does this mean…. ?

In Summary is the share of the mobility pound is getting very stretched , companies are now having to share the revenue that Blackberry once dominated and while this will create new revenue for additional functionality, much of what is described above is not new.

Advertisements

About beyondmobile.ltd

Blog Site for Jason Boud and Beyond Mobile Ltd.
This entry was posted in Market analysis and tagged , , , , , , , , . Bookmark the permalink.

One Response to Replacing blackberry? The Mobility stack and the new revenue model

  1. A great article. I would consider the validity of transience in the data and application ‘control’ of said – i.e. the information is where? memory-in-app/local storage/etc. It seems there’s much debate about device OS-control vs. device APP-control. Couple that with physical device access and application access in addition to the myriad of issues you’ve raised and mentioned – it becomes an interesting ‘playground’.

    There is perhaps errant thinking in ‘partitioning’ at an OS-level – not to dissimilar to handling failure at the infrastructure level rather than app-level (think DNS – it’s an app not a server with redundant disks).

    I’m not convinced the ‘framing’ is entirely central to the argument. A great article nonetheless. BYOD will prevail… who will be the first to say ‘utter control’?

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s