Several months have passed since Google released its long-awaited Android Lollipop OS. Since its initial beta release, dev teams all over the world, including our own, have been anxious to get their hands dirty and explore what Lollipop has to offer.
Android’s new OS is packed with new features and capabilities, like a completely new runtime (ART, which replaces Dalvik in earlier OSs), a whole new approach to UI and UX called Material Design, new connectivity, sharing, and security options, plus several more features too numerous to mention here.
Obviously, such dramatic changes to an OS must inevitably effect backward compatibility. Just as app migration problems plagued previous Android upgrades (most notably between 4.1.x/4.2.x, and Gingerbread), our QA experts anticipate that major challenges will accompany the full-scale adoption of Lollipop in 2015.
Tests performed by Archer Software suggest that problems related to upgrading to Lollipop will effect between 50% and 60% of all Android mobile applications. In most cases, these problems can be resolved with a few calculated adjustments. In some cases, however, mobile application components will have to be completely rebuilt.
Google Nexus devices have already integrated Android’s new OS, and major vendors like HTC, Samsung and Sony are planning to roll out new Android devices between December 2014 and February 2015.
If your mobile users are experiencing upgrade-related problems, or if you’d like to take a proactive step to make sure your app is ready when Android L hits all devices in February 2015, feel free to reach out to our QA team at email@example.com for a consultation.