Title: According to [1], Google is transitioning from APK format to AAB (Android App Bundle) which features Play App Signing [2], which, essentially, requires you to give Google your App&#x27;s existing signing keys, with all the usual implications.<p>Google uses comforting language to portray this as a very convenient feature for &#x27;most&#x27; developers. However, this would also give Google an ability to ship modified apps to users, still signed by perfectly valid App key, and this perspective looks really scary to me.<p><i>&gt; To use Play App Signing today you have to provide a copy of your existing app signing key because Google Play needs a copy of it to sign and deliver updates to your existing users. This suits most developers, over 1M apps are using Play App Signing in production.</i><p>They also promise to have a way of signing up without uploading a key &#x27;soon&#x27;, but it is not clear how it will work from the description:<p><i>&gt;  Soon, we will add an additional option for existing apps to opt in to Play App Signing by performing a key upgrade. Choosing this option means Play App Signing can use a new, unique key for all new installs and their updates. However, for this to work, when you upload an app bundle, you also need to upload a legacy APK signed with your old key so that Google Play can continue to deliver updates to your existing users.</i><p>What&#x27;s your perspective on this?<p>[1]: https:&#x2F;&#x2F;android-developers.googleblog.com&#x2F;2021&#x2F;06&#x2F;the-future-of-android-app-bundles-is.html<p>[2]: https:&#x2F;&#x2F;developer.android.com&#x2F;studio&#x2F;publish&#x2F;app-signing
Upvote: