-
Notifications
You must be signed in to change notification settings - Fork 116
What version of the minSdk in the end? #16
Comments
Well, their reference app works with EN and it still uses minSdk 21 so we could say it works for API 21 :) |
Unfortunately it seems to be impossible to actually test this unless you are a whitelisted developer, which I am sadly not. I'm a bit surprised that Google doesn't answer questions here. Wouldn't it help all the developers around the world trying to implement their versions? |
They are not very responsive indeed. I assume, the API is still not stable so it's hard for them to say if it will work with API 21 in a week or a month. |
We're using 23: https://github.com/austrianredcross/stopp-corona-android/blob/develop/app/build.gradle#L20 Does this help? That's a lot of reference now 😁 |
@falkorichter I figured from the repo that "we" means Austria. In the media and in response to questions, the German project has emphasised heavily that the decision to support only 23+ was Gapple's, not theirs! So I don't think it's very helpful to know what Germany/Austria are using. In fact, the motivation for this question is whether API 23+ is a necessity, or whether it is a choice that could be changed by implementers. What would be very useful to know from @falkorichter is (I assume that saying "we" he is one of the few whitelisted devs) whether Austria tested API 21/22 with the exposure notification API and what the results were. If they haven't tested that yet, wouldn't it be a great experiment that could benefit a lot of people? Dropping from 23+ to 21+ may increase penetration by ~10%, causing an increase in benefit of ~20% (benefit is quadratic in adoption). |
exposure-notifications-feedback@google.com 寫郵件到這個信箱,較快得到回覆 |
I don't know about the reasoning behind choosing 23. I'm contributing to the 🇦🇹 app, yes. But the information I provided might as well just from my observations of public repos as a curious developer 😏 |
@falkorichter I also tried today our app with It was a wild and seems to be completely wrong because their preview of Nearby library doesn't force the That being said, I believe it's safer to play by the documentation for now i.e. set minSdk to 23 even if EN works with API 21 🤷♂️ |
Latvia uses minSdk=21 https://play.google.com/store/apps/details?id=lv.spkc.gov.apturicovid |
on https://developers.google.com/android/exposure-notifications/exposure-notifications-api#architecture it now states:
|
Their website is essentially a copy of the last pdf file they have, so the question is still not answered because the evidence shows a different thing - it works with API 21. But I agree that it's safer to use 23 now, however, it will be sad to switch back to 21 if you used some features from 23 already :) |
One feature I see is individual permissions. However, I still haven't understand what's the difference between minSdk and targetSdk (or whatever this is called exactly). |
Starting from
v1.3
the documentation says the min is 23:But after a few updates in this repo to
v1.3
and higher it still uses 21 as the minSdk. Is this a mistake in the documentation or here?Thank you
The text was updated successfully, but these errors were encountered: