I was getting pretty comfortable with the idea that Mobility practice was coalescing around a Workspace/container that could deliver a strong set of collaboration applications and a business application ecosystem on any employee owned device.
Think Good and their Good Dynamics ecosystem, Citrix with Receiver, Xen Mobile, and WorX, etc and emerging players like Dell.
And there is no doubt they can deliver a very secure email and collaboration application experience, all without the enterprise managing or messing with the employees device via MDM. Admittedly the cost is the use of an “imposed UI” versus the native UI on the device, but overall I have been feeling pretty clever and even liked by my end users.
But a set of dialogues this week that I have had the opportunity to be part of have me feeling profoundly less comfortable
1. Talking to Good last week about their roadmap, they revealed that some of their more mature, larger customers were now coding not only internal applications to the Good API’s that allow access to the secure container, but also B2B applications as well. Wow! What are the implications of getting developers to code to the Good API’s? Can you say lockin? But how else do you leverage the secure container?
2. Then I had a talk with the Microsoft CIO. Beyond the kind of corporate applications you might want to protect in a container, Microsoft is seeing huge value and massive groundswells of innovation from staff building mobile apps to solve employee problems like finding colleagues, mapping campuses, helping people track shuttle buses via GPS, pointing a camera at a building to identify it and find a meeting room etc etc. Small things maybe, but building energy around mobile. Well to do that enterprises need an application wrapping/store deployment that perhaps bypasses the container. Oh, and by the way this employee engagement with Mobile is not a new idea. The team at Apple was advocating this three years ago….I just forgot as we fought to get an acceptable container deployment established.
3. Then of course the Microsoft announcements of Office 365 clients for almost every platform bring new capabilities and challenges. They automatically stream updated versions of the client at connection, removing a lot of application management worries…and in small ways bring policies and capabilities that feel like a light weight container…How might this integrate into a mobility strategy?
Yikes. Pretty clear that there will be no “once and done” when it comes to mobility strategy, whether MDM, EAM, EMM or whatever flavour/acronym you have embraced.