Lol, so after all those raging debates and flames, it turns out that F-Droid was a pioneer and innovator, years ahead of Google. “With Google Play App Signing, you can securely manage your app signing keys for new or existing apps. Keys are stored on the same secure infrastructure Google uses to store its own keys.”
Anyone hear anything about Google’s motivations for doing this?
From the article on Android Police (on mobile so no link), this is just to make things easier for developers. And also make it less likely that developers accidently lose their signing key.
That’s one consideration. But I’m guessing that’s just their public reason. I’ll bet they did it for very different reasons. It basically is a reversal of the driving idea behind APK signatures since the beginning of Android: decentralized cryptography and Google Play never modifying the binaries.
Probably for pragmatic, data-based reasons. Originally, being minimally centralised was better, but in fact developers and users are in general better served by having to do less, and the legal viewpoint is still that the key belongs to the developer, not Google, so they don’t have to “sign off” on that any Play store app is not complete crap or that it won’t kill kittens.
“This means that developers switching from APK to App Bundles can no longer provide the exact same package or experience on other app sources unless they opt to maintain a separate APK version. This naturally puts third-party app stores at a disadvantage, but Google will most likely play up the Play Store’s security…”
Come on Hans, this is obviously to inject apps with binary code after compiling. Do you remember the viruses in the 80’s? the cascade virus for example … something like that…