Chrome 42 will be the last release that officially supports Android 4.0 Ice Cream Sandwich

BY

Published 3 Mar 2015

NSFW AI Why trust Greenbot

We maintain a strict editorial policy dedicated to factual accuracy, relevance, and impartiality. Our content is written and edited by top industry professionals with first-hand experience. The content undergoes thorough review by experienced editors to guarantee and adherence to the highest standards of reporting and publishing.

Disclosure

android-chrome-io-2014

Despite the fact that Chrome for Android debuted on Android 4.0 Ice Cream Sandwich, the aging version of Google’s mobile operating system is getting frozen out soon.

As revealed on a public blog post today on the Chromium Blog, Android 4.0 Ice Cream Sandwich simply no longer has the users to warrant subsequent updates for the platform when it comes to Chrome, which means that here shortly, new features will no longer be in store for that specific version of Android:

The blog post says that they’ve watched Ice Cream Sandwich users decline by 30 percent in just the last year, and this drop, along with the sustained drop prior to this, means that upgrading Chrome for that older software just doesn’t make any sense anymore. They want to sharpen their focus on what’s current, to keep bringing great new features to the app, and so that means the older platform will no longer be getting new features once Chrome 42 launches.

Ice Cream Sandwich users will still be able to use Chrome, but there won’t be any new features coming to the app after Chrome 42 arrives.

In the last year, we’ve seen the number of Chrome users running ICS drop by thirty percent. Developing new features on older phones has become increasingly challenging, and supporting ICS takes time away from building new experiences on the devices owned by the vast majority of our users. So, with Chrome’s 42nd release, we’ll stop updating Chrome on ICS devices. After Chrome 42, users on ICS devices can continue to use Chrome but won’t get further updates.

What do you think of this decision?

[via Chromium Blog]