I feel that the only way out is gonna be using the debug account (ie. the one with the public “androiddebugkey” keyAlias, which the SDK uses for development builds), as this seems to be the only possibility Google is still allowing.
This has the side effect that devs that want to remain Google-independent can no longer rely on the built-in protections in Android which prevents an app from being updated if it hasn’t been signed with the same credentials… but well, that seems to be the only road Google is allowing for anyone who does not wanna register with them.
I mean… the other alternative would be to, essentially, fork Android / expect a custom AOSP to be installed… which might not be an option for all hardware out there.
I feel that the only way out is gonna be using the debug account (ie. the one with the public “androiddebugkey”
keyAlias, which the SDK uses for development builds), as this seems to be the only possibility Google is still allowing.This has the side effect that devs that want to remain Google-independent can no longer rely on the built-in protections in Android which prevents an app from being updated if it hasn’t been signed with the same credentials… but well, that seems to be the only road Google is allowing for anyone who does not wanna register with them.
I mean… the other alternative would be to, essentially, fork Android / expect a custom AOSP to be installed… which might not be an option for all hardware out there.