imageBYOD 1.0 is over. Organizations have recognized the many shortcomings of existing Enterprise Mobility Management solutions and want more. Organizations want to deploy their applications and data securely to any device that is convenient to the end user. They want to manage their data, not their users’ devices. They do not want to have to acquire Ph.D-level expertise in cryptography and identity management in order to secure their data. They want to avoid wasting money maintaining multiple code bases across all the platforms their applications need to support. They want to decouple their mobility strategy from the whims of consumer mobile device vendors, their app stores, and any other third party dependency that makes no sense for their business.

The BYOD 1.0 story started in early 2010, when smartphones and tablets started infiltrating the enterprise IT environment in large numbers. A large crop of mobility startups arose to provide solutions that promised to help IT manage all these new devices flooding their networks.

This first generation of enterprise mobility management solutions focused on asserting control over employee-owned devices to enforce a baseline security profile. Early adopters have recognized the shortcomings of these heavy-handed solutions from Mobile Device Management and Mobile App Management vendors—MDM and MAM, respectively.

In the case of MDM, these shortcomings include requiring a user to cede control of their device to IT. This gives IT managers the ability to enforce device-level policies to reduce mobility risk, but at the expense of end user privacy. As a result, MDM-based BYOD programs face significant hurdles to end user adoption.

MAM vendors provide a finer-grained solution that rightly focuses security and management at the application level. However, these solutions require organizations either to rebuild their apps with a secure wrapper or re-engineer the apps with a low-level SDK that inserts management hooks directly into the app. Either way, organizations must incur a significant additional cost before receiving any value from a MAM solution.

Organizations are tired of these BYOD v1.0 solutions because they tend to create as many problems as they solve. One contrarian organization has even organized a session at an upcoming industry conference called "You Can Say No to BYOD." Clearly, there must be a better way to solve these problems, short of throwing the baby out with the bath water.

BYOD 1.0 was about managing end user devices. Managing devices required adding the infrastructure to your IT environment to make this possible. Typically, this resulted in slightly more security, accompanied by higher operating costs and technical complexity. BYOD 2.0 is about stripping away technical complexity where possible, inefficient processes, and wasteful spending. BYOD 2.0 focuses on what is most important to organizations: mobilizing their data.

BYOD 2.0 is about stripping away technical complexity where possible, inefficient processes, and wasteful spending. BYOD 2.0 focuses on what is most important to organizations: mobilizing their data.”

Application development for mobile has evolved in a way that results in redundant, expensive, and wasteful duplication of efforts. For so-called native development, engineers must implement the same application for each platform they need to support. This duplication results in the maintenance of multiple distinct code bases – one for each supported mobile platform – each solving the same problems. In addition, the steady stream of updates from the native OS vendors on these devices imposes frequent and immediate patching requirements for apps, lest they stop working. This model scales poorly.

Hybrid applications improve on this model somewhat by using cross-platform HTML5, JavaScript and CSS to create a single code base that can work across platforms. Unfortunately, these assets must then be packaged using a native packager, distributed through the same consumer app stores, and updated whenever the underlying OS introduces a new incompatibility. This model also scales poorly.

It would be better to be able to deploy pure HTML5 apps into a runtime environment that provides the management and security capabilities missing from hybrid and native apps and consumer web browsers. If the runtime provided an API bridge to native OS and device capabilities, organizations could reap the benefits of both web and native development without the drawbacks of either.

This secure, managed runtime environment would insulate organizations from the rapid evolution of the underlying devices. As long as the runtime supports the device, developers could confidently deploy their application to it with minimal additional testing.

Using a managed runtime to deploy pure HTML5 apps is how you can future-proof your enterprise mobility strategy. Imagine being able to eliminate the costs associated with multiple code base development, native packaging for hybrid apps, and deploying your business apps through public, consumer application stores. Imagine delivering your sensitive data to any device using a platform that is secure by design, giving you end-to-end data security and fine-grained access control for your data. Imagine being able to deliver a superior user experience on any device with a single code base. It’s time to stop dreaming; BYOD 2.0 is here and ready to deliver.

Learn more about how Sencha can help with your journey to BYOD 2.0.

.right, .alignright float: right; margin: 0 0 10px 10px;
.left, .alignleft float: left; margin: 0 10px 10px 0;

Continued – 

BYOD 2.0 Is Here