How does this affect “second-party” apps (i.e. apps you have created yourself)? Are you still allowed to go to Android studio, make an APK, transfer it to your own phone, and install that app? If no, this spells the death of experimental indie developers on Android.
yes. from what I understand, you will get a developer key from Google, and then you will sign your APK with your key.
you’ll still be able to sideload apps that have been signed with developer keys. the main point here is that Google is forcing the developer to identify themselves.
How does this affect “second-party” apps (i.e. apps you have created yourself)? Are you still allowed to go to Android studio, make an APK, transfer it to your own phone, and install that app? If no, this spells the death of experimental indie developers on Android.
yes. from what I understand, you will get a developer key from Google, and then you will sign your APK with your key.
you’ll still be able to sideload apps that have been signed with developer keys. the main point here is that Google is forcing the developer to identify themselves.
You don’t need to sign anything just turn off play protect with 1 adb command:
adb shell settings get global package_verifier_user_consent adb shell settings put global package_verifier_user_consent -1 # disable Play ProtectNot a solution to our problem, but this is a crumb in our favor.
Even Apple lets you do that… one imagines Google being less restrictive than Apple