You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm curious to know, is there any reasons for this or is just some internal decision? currently 84% of the users are on SDK 19 and above. 12% of that remaining 16% are on SDK 16-18. I know 12% doesn't seem like much, but given the android adoption (~1.6 Billion active devices as per Google) that translates to quite some users (~192 millions) which will not be able to use an app targeting SDK 19 and above...
The text was updated successfully, but these errors were encountered:
I'm curious to know, is there any reasons for this or is just some internal decision? currently 84% of the users are on SDK 19 and above. 12% of that remaining 16% are on SDK 16-18. I know 12% doesn't seem like much, but given the android adoption (~1.6 Billion active devices as per Google) that translates to quite some users (~192 millions) which will not be able to use an app targeting SDK 19 and above...
The text was updated successfully, but these errors were encountered: