organicmaps/organicmaps-tmp

Archived

Fork 1

[android] Investigate how to split API21-22 into a separate bundle #3886

New issue

Closed

opened 2022-11-15 07:20:35 +00:00 by rtsisyk · 8 comments

rtsisyk commented

2022-11-15 07:20:35 +00:00

Owner

Needed for #3806

biodranik commented

2022-11-15 08:50:46 +00:00

(Migrated from github.com)

That's not a good solution. It means that we should to choose from one of the two options:

Leave old API levels apk only in Google Play, and increase min API everywhere else to support AA in all markets.
Leave old API levels everywhere and have AA support ONLY in Google Play, where APKs are split.

That's not a good solution. It means that we should to choose from one of the two options: 1. Leave old API levels apk only in Google Play, and increase min API everywhere else to support AA in all markets. 2. Leave old API levels everywhere and have AA support ONLY in Google Play, where APKs are split.

AndrewShkrob commented

2022-11-18 14:15:07 +00:00

Member

I see another approach. But I'm not sure if there is at least one company/product that uses it as it has significant cons.

Use Dynamic Feature Delivery for Google Play. Everything is good - single bundle, old API support, AA for API 23+ devices, AAOS support

For other stores:

increase the minimum API level for AA support
create another application for old API 21-22, name it "Organic Maps Legacy"

I see another approach. But I'm not sure if there is at least one company/product that uses it as it has significant cons. Use Dynamic Feature Delivery for Google Play. Everything is good - single bundle, old API support, AA for API 23+ devices, AAOS support For other stores: 1. increase the minimum API level for AA support 2. create another application for old API 21-22, name it "Organic Maps Legacy"

biodranik commented

2022-11-18 15:38:38 +00:00

(Migrated from github.com)

There are Huawei, Samsung, Amazon, and other marketplaces too )

rtsisyk commented

2022-11-19 07:18:18 +00:00

Author

Owner

Use Dynamic Feature Delivery for Google Play. Everything is good - single bundle

We already use AAB bundles.

Google told me that two separate bundle for different APIs are not supported. It looks like that we will have to drop API21-22.

> Use Dynamic Feature Delivery for Google Play. Everything is good - single bundle We already use AAB bundles. Google told me that two separate bundle for different APIs are not supported. It looks like that we will have to drop API21-22.

AndrewShkrob commented

2022-11-20 16:15:44 +00:00

Member

It looks like that we will have to drop API21-22.

No. We don't have to. At least for google play. Check this: https://developer.android.com/training/cars/apps/automotive-os
AAOS code is in a separate module. I think the same can be done for AA. We'll have three modules:

Base app
AA for API 23+
AAOS

And it should be possible to configure it in the way to download AA module if a user has an API 23+ device. Check the Conditional delivery section here: https://developer.android.com/guide/playcore/feature-delivery

>It looks like that we will have to drop API21-22. No. We don't have to. At least for google play. Check this: https://developer.android.com/training/cars/apps/automotive-os AAOS code is in a separate module. I think the same can be done for AA. We'll have three modules: * Base app * AA for API 23+ * AAOS And it should be possible to configure it in the way to download AA module if a user has an API 23+ device. Check the `Conditional delivery` section here: https://developer.android.com/guide/playcore/feature-delivery

biodranik commented

2022-11-20 17:27:54 +00:00

(Migrated from github.com)

Considering AAOS approach, is it feasible to easily support:

API 21-22 APK (or API 21-31+ APK)
AA APK (API 23+)
AAOS APK (API 29+)
so we can build all these APKs and distribute all of them either in separate apps in stores, or publish them on Github/our website, and distribute only (2) in stores?

What are the pros and cons of this approach?

Considering AAOS approach, is it feasible to easily support: 1. API 21-22 APK (or API 21-31+ APK) 2. AA APK (API 23+) 3. AAOS APK (API 29+) so we can build all these APKs and distribute all of them either in separate apps in stores, or publish them on Github/our website, and distribute only (2) in stores? What are the pros and cons of this approach?

AndrewShkrob commented

2022-11-30 18:50:01 +00:00

Member

Regarding AA and other stores:

We also can separate AA into a module like for AAOS for Google Play.
We will have to distribute 2 separate apps for other stores. The disadvantages are:
- New page in stores for a legacy version without rating and reviews
- We'll have to notify users with old API devices that they must download a new app if they wish to get updates

The easiest way is to drop old API support. We won't have any problems until the AAOS support which requires refactoring as described above.

Regarding AAOS: I'm not sure if there is a sense in publishing this version for other stores. AAOS seems to be a "closed" platform. I guess there is no possibility to install 3rd party apks. So, it should be distributed only for Google Play. And it can be distributed for Google Play only after refactoring of `android` folder to enable modules support Regarding AA and other stores: * We also can separate AA into a module like for AAOS for Google Play. * We will have to distribute 2 separate apps for other stores. The disadvantages are: * New page in stores for a legacy version without rating and reviews * We'll have to notify users with old API devices that they must download a new app if they wish to get updates The easiest way is to drop old API support. We won't have any problems until the AAOS support which requires refactoring as described above.

rtsisyk commented

2022-12-17 08:02:24 +00:00

Author

Owner

Conclusion here is to bump API level to 23 as soon as Android Auto is ready.

This repo is archived. You cannot comment on issues.