Open ArchBlood opened 5 months ago
Very good idea to avoid that mess that happened with PHP years ago where 5.6 was a headache even 7.2 was out.
Honestly hosting companies and users both should be forced to regular update their applications also for improvement and security reasons. And it is even more important on mobile applications as otherwise this backward compatibility is harming the future development. Android 14 is out and 12 runs still on most phones while 10 is often used in cars and those care suppliers seem to be as reluctant to update as those hosting companies that used php5.6 and did not get rid of it.
On Thu, Jun 6, 2024, 02:13 ArchBlood @.***> wrote:
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
— Reply to this email directly, view it on GitHub https://github.com/humhub/app/issues/189, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAPD4O7FBV4WXEETXAYQR73ZF5PMTAVCNFSM6AAAAABI3KK3GKVHI2DSMVQWIX3LMV43ASLTON2WKOZSGMZTMNRUHAYDENY . You are receiving this because you are subscribed to this thread.Message ID: @.***>
@PrimozRatej Do you have an overview here?
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.
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".
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.
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