Google appears to be developing a native App Lock feature for Android 17, according to code discovered in recent Canary builds. The system would let Pixel users secure individual applications behind Face Unlock, fingerprint authentication, or passcode protection.
Android Authority and Android Headlines both report finding evidence of the feature in testing versions of Android. This would build upon Android 15's Private Space feature, which already offers app isolation through separate user profiles, but lacks the convenience of simple biometric unlocking for individual apps.
Currently, Pixel device owners must use third-party applications to lock sensitive apps like banking, messaging, or photo applications. Competing Android manufacturers including Samsung, OnePlus, and Xiaomi have offered similar functionality for years through their custom interfaces.
The new API would enable default launchers to manage app locking, eliminating dependency on external security tools. Google's existing Private Space feature offers app isolation but operates through separate user profiles. This approach silos applications completely, making daily use inconvenient compared to simple biometric unlocking.
Android 17 development follows Google's revised release schedule that began with Android 16 Developer Preview 1 in November 2024. The company typically announces major Android versions in April or May, with public releases following in August or September, according to historical release patterns.
Code presence in Canary builds doesn't guarantee feature delivery. Google could postpone implementation to Android 17 Quarterly Platform Release 1 or defer entirely to Android 18. The company has previously abandoned planned features discovered in early testing.
If implemented, native App Lock would address a longstanding privacy gap in Google's Pixel software strategy. The feature would bring Pixel devices in line with security options already standard across most Android manufacturers and Apple's iOS platform.
