View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0012187 | MMA | General | public | 2014-09-18 18:19 | 2016-09-13 02:34 |
| Reporter | rusty | Assigned To | |||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Product Version | 1.2.0 | ||||
| Target Version | 1.2.0 | Fixed in Version | 1.2.0 | ||
| Summary | 0012187: Remove support for Gingerbread | ||||
| Description | As discussed today, the number of users on GB is ~12% https://developer.android.com/about/dashboards/index.html On MMA, the number is actually ~5.5% on GB, and ~.05 on Froyo. ==> for the next major release, support for GB can be removed if including it is incompatible with some of the new planned features. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 540 | ||||
|
|
As of today, ~2% of users are on Gingerbread. So if the migration to Material Design is complicated by support for GB devices, we can remove it. |
|
|
It is not only about Material Design. It is a huge simplification for everything. Currently Chormecast support requires build with min API 14 so we should remove Gingerbread support for 1.1.4. We can leave 1.1.3 as separate application in Play store, so users with older devices can install this older application that will support theirs device. |
|
|
I don't think that there are many _new_ Gingerbread users, so we can just make the change in 1.1.4 if it's a requirement. Existing GB users just won't update to the new version. |
|
|
Some apps do this, ES file explorer exists in two versions. I.e. when user uninstalls the app on GB, he won't be able to reinstall it. But it probably doesn't matter. Implemented in build 1.1.4.540 |
