Android applications are built with Java. Gradle is (finally) a mature and well-known build framework. Jenkins is a Java-first Continuous Integration platform and already has fantastic support for Gradle (as well as Maven and Ant) out of the box. So what’s the problem?
Will it be called Lollipop? Licorice? Lemon Sorbet? OK, that’s a stretch.
Chances are, you probably aren’t concerned with the real name of Android L. In fact, you’re likely not looking ahead at all, given the fragmented state of the platform and the lead-time before your organization fully upgrades (note: fragmentation is getting better with over 85% of the Android ecosystem on Android 4.x as of August, 2014).
Here at BlueFletch, though, we believe that it’s always important to know what’s on the horizon. In this case, L is purported to be the next big version increment for the OS, serving as the baseline for Android 5.x. Along with the version bump come a slew of new features that will most certainly impact you and your organization.
As has been the norm with the press around each release, Google’s communications carry a consumer slant, with a strong focus on Material Design and the user experience changes inherently with the upgrade. However, Google continues to add enterprise features to their offering, and several improvements in L bring yet more maturity to the platform.
Here are the 5 enterprise features in Android L that we at BlueFletch are most excited about:
How to convince your organization to embrace the droid.
Since its inception, Android has had a reputation in some circles as a cowboy platform call it the Wild Wild West of the mobile space. It was customizable, diverse, fragmented, hack-able, new and novel. A lot of consumers loved these characteristics. Most enterprises did not.
To be fair, neither Google nor Apple cared much for the enterprise in the beginning. Android actually went a long way in protecting the user, as a consumer, from some of the controls that an IT department might want to impose on an enterprise platform. This tune started to change, though, as far back as Android 2.2 with the introduction of the Device Administrator APIs and Google’s focus has continued to shift in recent revisions to better security, extended device admin APIs and cloud-based mobile device management features.