View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0013167 | MMA | General | public | 2016-03-04 15:15 | 2016-09-13 02:34 |
| Reporter | rusty | Assigned To | |||
| Priority | high | Severity | feature | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Product Version | 1.2.0 | ||||
| Target Version | 1.2.0 | Fixed in Version | 1.2.0 | ||
| Summary | 0013167: Support Gingerbread via Multiple APK support | ||||
| Description | We can continue to support Gingerbread devices even as we remove support for them MMA 1.2+ via the Play store's 'Multiple APK Support': i.e. one APK for Gingerbread devices, and another for Kitkat+, but expose only a single version. See: http://developer.android.com/google/play/publishing/multiple-apks.html In addition (and these are both lower priority items): b) if we want (though I think it is _not_ recommended by Google's best practices), we can use different APKs for different CPU architecture in order to reduce APK size. c) we can use set max SDK directly in app and it is used by Google play store filter. This we can use for ringtone app that can be part of MMA APK in Marshmallow+, so it should be hidden for Marshmallow users. i.e. a new MediaMonkey Ringtone addon 1.1.00005 would only be used for pre-Marshmallow devices. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 581 | ||||
|
|
About Gingerbread support via Multiple APK, there should be no issue. Just enable Multiple APK in Android development console and publish new stable for api >= 15. All conditions should be already satisfied. a) unnecessary yet b) already included in 1.2.0.0581. We can publish Ringtone addon 1.1.00005 (with max api 22) after 1.2.0 will be released (as stable). The Rigntone 1.1.00005 build is already on FTP. |
