Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Targeted Android Versions #189

Open
ArchBlood opened this issue Jun 5, 2024 · 5 comments
Open

Targeted Android Versions #189

ArchBlood opened this issue Jun 5, 2024 · 5 comments
Assignees

Comments

@ArchBlood
Copy link

I believe we should be transparent about what versions of Android are or should be supported for the app, after running some personal tests for older versions of Android (i.e KitKat, Lollipop, Marshmallow) these versions do not seem to work correctly with the current version of the HumHub app, nor do I think we should as even Google no longer support these versions.

https://community.humhub.com/comment/perma?id=49194

@lisandi
Copy link

lisandi commented Jun 6, 2024 via email

@luke-
Copy link
Collaborator

luke- commented Jun 6, 2024

@PrimozRatej Do you have an overview here?

@PrimozRatej
Copy link
Collaborator

PrimozRatej commented Jun 19, 2024

It's good to note that support for versions below API 26 (Android 8.0) is becoming rare. Developers might still accommodate older versions if there's a substantial user base on those versions. As of today everything lower than 9.0 Pie has less than 3% market share. (source: https://gs.statcounter.com/os-version-market-share/android)

For our case numbers look like this:

Newer Android versions generally provide better tools and improved functionality. Supporting older versions often means writing more code to achieve similar features available in newer versions. Moreover, ensuring that the app works across multiple Android versions requires more testing, adding to the development effort.

In theory, we could go as low as Android 5.0, but that would mean using older versions of libraries and most importantly older version of Android WebView. This could lead to issues because we are already using features on the web that are not yet implemented in the library. I would not recommend going lower than 8.0.

@ArchBlood
Copy link
Author

It's good to note that support for versions below API 26 (Android 8.0) is becoming rare. Developers might still accommodate older versions if there's a substantial user base on those versions. As of today everything lower than 9.0 Pie has less than 3% market share. (source: https://gs.statcounter.com/os-version-market-share/android)

For our case numbers look like this:

Newer Android versions generally provide better tools and improved functionality. Supporting older versions often means writing more code to achieve similar features available in newer versions. Moreover, ensuring that the app works across multiple Android versions requires more testing, adding to the development effort.

In theory, we could go as low as Android 5.0, but that would mean using older versions of libraries and most importantly older version of Android WebView. This could lead to issues because we are already using features on the web that are not yet implemented in the library. I would not recommend going lower than 8.0.

I agree, older versions of Android shouldn't be supported in this case, I'm not sure we should official support Android 8.x either, namely because we can't account for custom Android versions or versions that are maintained by other manufacturers. So in this case I would officially support Android 9 to 14, and unofficially support Android 8.x under a tag "Not recommended".

@PrimozRatej
Copy link
Collaborator

PrimozRatej commented Jul 6, 2024

I created a simple test on Firebase Test Lab. It confirms that our app works with Android 8 (API level 26) and up.

Test results:

Maybe we could automate this process for every production release within the deployment process.

@PrimozRatej PrimozRatej self-assigned this Aug 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

4 participants