Member-only story
Your Signing Key Will Outlive Its Cryptography: Hybrid APK Signing on Android 17
Not a Medium Member? “Read For Free”
Most Android teams treat the release keystore like a fire extinguisher. It hangs on the wall, everyone knows where it is, and nobody thinks about it until something is burning.
That habit has a hidden cost. The RSA or ECDSA key that signs your app today is not a short-lived credential. It is the identity every installed copy of your app uses to decide whether the next update is really from you. Keys like that routinely stay in service for twenty years or more.
Android 17 (API 37) is the first release that lets you start protecting that identity against a future quantum computer. It ships a new signing scheme, APK Signature Scheme v3.2, which pairs a classical key with a post-quantum ML-DSA key. Almost nobody is writing about it from the app developer’s side, so this post does. We will cover:
- how Android’s signing schemes got here, and why each one exists
- what a quantum computer does and does not threaten
- what is actually inside a v3.2 APK
- how hybrid key rotation works, with a concrete
apksignerflow - Kotlin you can use today to inspect, pin, and prepare
