Skip to Content
Author's profile photo Former Member

Android 5 Jelly Bean: I Say Innovation, You Say Fragmentation…

Ah, June. The beginning of summer, when the kids are finally released from school, and Gadgets are finally released from the Purgatory between Digitimes Taiwan rumor and Midwestern Best Buy store shelf.

The hottest gadget rumor, lately even hotter than the iPhone 5, and wayyy hotter than the quickly-dismissed Facebook phone, is the Google Nexus tablet. This would be Google’s second attempt at mobile hardware – its Google Nexus smartphone was a non-starter. It will allegedly be built by Asus, not Google’s recently-swallowed Motorola Mobility, and run Nvidia’s quad-core Tegra 3 chipset. It will be 7 inches, cost a Kindle-matching $200 and be the debut of the latest Android update, version 5.0, aka Jelly Bean.

For consumers, Jelly Bean should indeed be sweet. Rumors say goodies include a Siri-like voice assistant, Google’s suddenly market-leading Chrome Web browser, better touch keyboard, more integration with Google services and more tablet-specific features.

For enterprises, rumored features they would care about include the ability to run on laptops (and possibly even dual-boot with Microsoft Windows), a file system, increased protection from malware, including the dumping of Adobe’s already-dying mobile Flash player.

The other good news for enterprises is that Jelly Bean heralds a new era wherein Google will only release one major Android update per year.

How sweet will Android Jelly Bean be for enterprises?


Google started off frenetically, taking the ‘ship early, ship often’ mantra literally. In 2009, Google released three updates to Android (Cupcake, Donut and Eclair).

After complaints, it slowed the pace to bi-annual updates in the last two years.

The problem is that Google’s hardware partners still haven’t caught up. Android 4.0 Ice Cream Sandwich is only running on about 5% of devices today. Almost two-thirds of devices are still running Android 2.3 Gingerbread. Even Android 2.1 Eclair, released 2.5 years ago, has more users than ICS.

The Samsungs and HTCs of this world remain slow about releasing their newest hardware with the latest Android update installed (though the vendors would retort that Google’s processes are to blame). They are also excruciatingly slow about making Android updates available to devices already out in the field (if at all).

By going to one update a year, providing better previews to key hardware and software partners, and clamping down on roadmap rumors, Cupertino-style, Google can go a long way towards turning a negative (fragmentation) into a positive (sustained, regular innovation).

I am also hoping that the lack of leaks about hard-core enterprise features in Jelly Bean are only because these kinds of features aren’t sexy enough for the Rumor Mill.

Broadly speaking, Android remains the least secure and manageable of the major mobile platforms, partly because it lacks those features itself, but mostly because it doesn’t allow third-party developers to easily implement them.

If Google opens up a significant number of Android APIs related to securing and managing devices, this would improve its reputation immensely, and overnight turn it into a true enterprise and BYOD contender versus iOS.

In the meantime, enterprises wanting to deploy Android should consider emulating companies like my employer, SAP. SAP has more than 1,000 workers using Android devices. But not just any devices: it has only approved Samsung Galaxy smartphones and tablets. Samsung has done special engineering work on Android to grant IT departments running selected Mobile Device Management (MDM) software, including SAP Afaria, stronger manageability and security than they would have over other Android devices.

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Steve Rumsby
      Steve Rumsby

      Fewer Android releases will certainly help with the fragmentation issue (if you see it as an issue, that is!). The other part of that issue is the sheer number of different Android devices out there. As I see if, manufacturers are focused so much on the next new device that they have no resources available to support the old ones. How many new Android handsets does Samsung produce each year? More than Apple have produced iPhone versions ever?

      I see SAP's approach of only supporting a very small set of Android devices as admission of this as a problem. It isn't just handset manufacturers that can't keep up. App and complementary software developers (like Sybase with Afaria) find it hard to support all Android devices also.

      As you say, one man's fragmentation is another man's innovation. I think the Android approach and the Apple approach are two extremes and maybe there's a happy medium somewhere - more frequent innovation than Apple with less fragmentation than Android? I'm sure one major Android release per year is a step towards that.

      Author's profile photo Former Member
      Former Member

      I wonder if there will emerge a business-class of Android smartphones that the MDM vendors and enterprise app makers will focus on supporting since, as you say, there are just too many devices. Samsung already has this with its Galaxy S line of devices.

      In terms of being the middle choice between Android and Apple, this is what Windows Phone/Windows 8 would love to be. We shall see.