Comment by izacus
1 day ago
Ehm, that's EXACTLY what happens now.
Noone is being banned because of this. You can't publish an update if it targets old Sdk and old sdk targeting apps don't appear to users (unless the user has already installed that app before).
That's it. Google is directly following your recommendation. Developers have usually more than a full year to comply (e.g. Android 16 has just released, developers will have to target Android 15 at the end of August. Android 15 beta was released around march 2024 giving developers ability to prepare and test).
What part of what I said suggested "old sdk targeting apps don't appear to users (unless the user has already installed that app before)" would be fine?
If the app works and doesn't do anything bad, there's no reason to delist it.
But the app is doing something bad - it has access to data it shouldn't have.
Unless you're saying that you solved the halting problem and can guarantee and verify that apps that still have all access to your data (because permissions aren't enforced) will NEVER in ANY codepath read data they don't need - you can sell that solution to Google Play then.