Google confirms Android 17 will enforce system-level Post-Quantum Cryptography (PQC). Analysis of ML-DSA digital signatures and the Q-Day 2029 timeline.
What Android 17’s PQC Mandate Changes
Android 17 is set to enforce post-quantum cryptography at the system level. That is not a library suggestion or an optional flag for apps that care about cryptography. System-level enforcement means the platform itself expects quantum-resistant primitives for the trust paths it controls: package integrity, system updates, and other signatures the OS must verify before it trusts code or configuration.
For app and platform teams, the practical shift is simple. Anything that still assumes classical public-key signatures as the only standard will eventually sit outside the default trust model. You do not need a quantum computer on a desk for that pressure to matter. The OS will start treating PQC as part of normal security posture, the same way it already treats modern TLS, keystore isolation, and verified boot as non-optional baseline behavior.
ML-DSA Signatures in Plain Terms
ML-DSA is a post-quantum digital signature scheme. Its job is the same as classical signatures: prove who signed a payload and detect tampering. The difference is the hardness assumption. Classical schemes rest on problems that large-scale quantum computers are expected to weaken. ML-DSA is built for the case where those attacks become practical, so verifiers can keep accepting signatures without relying on algorithms that age poorly under quantum cryptanalysis.
Operationally, ML-DSA usually means larger keys and larger signatures than many teams are used to. That tradeoff shows up in storage, bandwidth, parsing, and update packaging more than in “is the math sound.” Teams should plan for signature blobs that do not fit old size budgets, for dual-support periods where both classical and PQC signatures may coexist, and for tooling that can generate, store, and verify the new format without ad-hoc hacks.
Why the Q-Day 2029 Timeline Matters
Q-Day 2029 is the planning horizon attached to this mandate: a target window by which systems should be ready for a world where quantum-capable attacks against classical public-key crypto are treated as a realistic risk, not a distant research topic. Whether the exact day arrives early or late is less important than the engineering reality behind the date. Cryptographic migration is slow because trust roots, signing pipelines, offline devices, and long-lived artifacts all lag behind algorithm choice.
Harvest-now-decrypt-later risk also makes early movement rational. Adversaries can store signed or encrypted traffic today and attempt to break it later. Digital signatures used for software authenticity have a different failure mode—forged updates or impersonated publishers—but the fix still has a long lead time. Waiting until quantum hardware is routine leaves no room to re-sign firmware, rotate roots, retrain release tooling, and validate that every path that verifies a signature understands ML-DSA.
What Engineering Teams Should Do Now
- Inventory every place you produce or verify digital signatures: app signing, OTA packages, SDK releases, CI artifacts, and any custom trust chains.
- Budget for larger signature and key material in packaging, storage, and network paths; size regressions are expected with PQC signatures.
- Design dual-stack verification so classical and ML-DSA can coexist during migration without breaking older clients that still need support.
- Treat Android 17’s system-level enforcement as a hard deadline for platform-adjacent code, not as a soft “when we get to crypto” backlog item.
The useful mindset is migration engineering, not algorithm worship. Confirm which trust boundaries Android will own, which ones your app still owns, and which third-party SDKs still ship classical-only signing assumptions. Then stage the change: generate ML-DSA-capable keys in non-production first, measure signature size and verify latency on real devices, and only then cut production release paths over. Teams that treat Q-Day 2029 as a calendar reminder rather than a multi-year cutover will be the ones still patching signing failures after Android 17 makes PQC the default expectation.