Post AR4cs7vYvnCZYywSPI by Billie@social.tchncs.de
(DIR) More posts by Billie@social.tchncs.de
(DIR) Post #AR4cs7vYvnCZYywSPI by Billie@social.tchncs.de
2022-12-27T20:10:14Z
0 likes, 2 repeats
When you do NOT publish your #android #app in the Play Store (e.g. #gadgetbridge, #fdroidapp , #imagepipe), is there a good reason to increase the #targetSdk ?Does it matter at all?The last sdk updates mainly impose restrictions without much benefit for developers and make development harder.Why upgrade targetSdk when you can completely ignore G***le's rules about minimum targetSdk?What are your thoughts?
(DIR) Post #AR4cs8WQiigzPKBts8 by eighthave@social.librem.one
2022-12-28T18:23:54Z
0 likes, 0 repeats
@Billie For apps that don't have features broken by #targetSdkVersion, you might as well up it. If your app is in a memory safe language e.g. Java, Kotlin then the targetSdkVersion does not help you much while restricting features. If the app uses C/native code and you don't want to think too much about security vulns, then upping it could help you. My understanding is that #Google thinks of it as a way to protect private data from unknown apps, so they don't have to review uploads to Play.
(DIR) Post #AR4dAhsY0HHwHEOJe4 by eighthave@social.librem.one
2022-12-28T18:27:16Z
0 likes, 0 repeats
@Billie One thing is clear: if bumping #targetSdkVersion breaks key features, then it is not worth doing it, especially if the app is shipped via #FDroid from the f-droid.org repo.
(DIR) Post #AR6s63FwNd57KVS1wW by Billie@social.tchncs.de
2022-12-29T20:23:54Z
0 likes, 0 repeats
@eighthave True, but the big boss G***le will try to cut functionality even when your app has a lower targetSdk by updating the system with some (anti-)features using the Play Store.'app hipernation'See here: https://developer.android.com/topic/performance/app-hibernationUnfortunately, this will also hit apps not at the Play Store.