Android 17's app lock is welcome, and embarrassingly late

Is it good news when a phone operating system finally offers something people have asked for since forever? Yes. Is it also a little embarrassing? Also yes. That is exactly how we feel about the return of app lock in Android 17 QPR3 Beta 3.

Google released the beta on October 29 for Pixel phones from the 6a onward, and, as Android Authority reports, it is mostly a bug-fix release with 26 fixes. Google's Mishaal Rahman singled out the return of app lock as one of the bigger changes, alongside app bubbles from the recents menu, a camera shortcut in Quick Settings and some restored lock screen blur.

Coverage so far doesn't spell out how the feature works in detail, so we won't pretend to know. What we can do is talk about what it means.

A basic privacy feature should not be a nice surprise

Locking an individual app behind a fingerprint, face or PIN is not exotic. It is the kind of thing you want when you hand your phone to a friend to show a photo, or when a child grabs it to watch videos. In our view, a tool this basic belongs in the core of the operating system, not in a patchwork of whatever each phone maker or third-party app decides to offer.

That is the uncomfortable part. When the platform owner leaves a gap this obvious, someone else fills it, and everyone ends up with a different version of the same idea. A native implementation means the feature is defined once, by the people who control the OS. That is simply better for consistency.

"Brings back" is the phrase that deserves attention

Notice the wording across the coverage: Google "brings back" app lock. Android Police says Beta 3 restores features Google removed in earlier QPR beta builds. So this is not a brand-new idea arriving triumphantly. It is a feature that was taken out of the beta track and has now returned. We would be careful not to read too much into that, since the coverage we have seen doesn't explain why anything was pulled. But it is a fair reminder that betas are betas, and nothing here is final.

It is also a reason not to celebrate too early. Until it lands in a stable build, it is a promise.

The real question is who will actually get it

Here is where our enthusiasm cools. This is a Pixel beta. Android Authority says QPR2 should go stable near the end of the year, with QPR3 to follow in 2027. That is a long wait even for Pixel owners.

For everyone else, the numbers are discouraging. According to Android Authority's distribution report, Android 17 sits at just 1% of active devices despite arriving in June 2026, while Android 11 still runs on 10.5%. The same report says more than 30% of active devices run Android 13 or older. The article does note that Android 17 has had less time to spread than Android 16 had, so the comparison is not entirely fair, but the broader picture of slow adoption is hard to ignore.

Put those together and we think the conclusion is plain: a privacy feature that depends on a 2027 QPR release will probably take a long time to reach most Android users on the phones they actually own. Whether manufacturers ship their own versions sooner is a question for them, but the slow spread of updates is the real bottleneck.

Our verdict

Credit where it is due: Google is doing the right thing, and putting app lock in the core platform is better than leaving it to a patchwork. If you own a Pixel and are comfortable with betas, you can try it, but back up your data first, as Android Authority recommends.

If you are not, don't hold your breath. Use whatever lock your current phone already offers, and treat the stock version as something to look forward to rather than rely on. The lesson for Google is simpler: basic privacy tools should not need a comeback story.