Android 17 is anticipated to introduce a native AppLock feature, enhancing user privacy by securing individual apps. This change, expected in 2024, allows users to lock specific apps using their default launchers without relying on third-party solutions or the current Private Space setup.
Upcoming Features and Security
Google is reportedly developing an App Lock API, as discovered in an Android Canary build. This API will allow users to manage app security through the LOCK_APPS permission, restricted to system apps and default launchers via the SET_APP_LOCK action. The feature aims to prevent the common issues related to the usability and reliability of third-party app lockers and minimizes the scope of error by avoiding the current dependency on accessibility hacks.
Technical Details and Limitations
The native App Lock will operate only on handheld devices, excluding platforms such as Wear OS, Android Automotive, and Android TV. Signal verification ensures that the app has a launcher entry, and is not opted out of locking before user prompts appear to lock or unlock apps. Although specific implementation details are absent from the Canary build, biometric authentication with a PIN or pattern fallback is likely under consideration, leveraging existing biometric APIs.
Possible Impact and Roadmap
- The feature is not yet live in Canary builds, and flags remain disabled.
- It’s unlikely to appear in near-term Quarterly Platform Releases.
- Expected earliest in the Android 17 update, enhancing device security.
- Addresses uninstall and usability issues of third-party app lockers.
- Clarification is needed on how notifications for locked apps will be handled.
AppLock is set to refine user security and application management on Android devices, ensuring a seamless, integrated experience with less reliance on third-party solutions.
