by Jason Wong | December 1, 2014 | Comments Off on What enterprise mobile app teams need to know about Android Lollipop
A couple of weeks ago, I wrote about the impact of iOS 8, iPhone 6 and Swift on mobile app development teams. Now I take a look at Android Lollipop’s impact.
The most obvious change with Android Lollipop is the new look of material design, and that it’s applied beyond the mobile phone and tablet to Android-based TVs, watches and even cars with the upcoming Android Auto infotainment system. Google’s material design language follows a shift in design trends that favors flat design, but it also heavily uses animation and shadows to add dynamism.
Google also announced the beta release of Android Studio, a new Android development environment that provides new features and improvements over Eclipse with Android Developer Tools (ADT), and will be the official Android IDE once it’s ready (which could be longer than expected given Google’s history of beta products).
The Android 4.4 release in October 2013 introduced the new, experimental Android Runtime (ART), which was optional to use, instead of the default runtime Dalvik. However, with Android Lollipop, ART is now the default runtime, which could impact existing apps. Apps in Android Lollipop will also be able to take advantage of APIs in other apps. This interlocking app concept means that apps can talk to each other, and connected apps can extend the workflow and functionality of each other.
On the management and security front, Android Lollipop makes some important strides, such as decoupling the WebView component from the OS and turning on data encryption by default to ensure better data security with fewer steps for users. But the most anticipated security updates are the inclusion of new security and management technology in the OS.
To find out the details of all these new enhancements and their impact on enterprise mobile teams, check out my note: Key Impacts of Google Android Lollipop on Enterprise Mobile App Development.
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.