App Lock (Biometrics/PIN Code)

(#4629) Feature Open: In progress mobile privacy security

Thread

Comment by Jiralite
Jiralite 1 vote 1 reply
On iOS, you can put any app behind Face ID, is this not the same for Android? Or is there something further you would like to be done?
Comment by sodiboo
sodiboo 2 votes
To my understanding, this is not a feature in AOSP, but it is a very common extension that many OEMs and "custom ROMs" provide (i think including LineageOS? very unsure though). an example of an Android that doesn't provide this is GrapheneOS. it supports "private spaces", which is a separate OS user nested within your main one, that can be locked behind additional authentication. But it is not quite the same as the basic app locking functionality. Instead, apps like Bitwarden, Steam, Molly, Element, ente, GitHub, Fastmail, and more, all implement this "client-side". In a lot of these cases, the lock actually wraps an account, and technically don't prevent you from using the app (even though the app might require an account always). For example, if you fail the Bitwarden biometrics you can provide your bitwarden master password instead (or log out, if you feel like it). the device PIN (which a sneaky onlooker might have glanced more easily) does not grant access to the app; only the app's password or specifically biometrics that the app authorized. if an onlooker knows the device PIN and adds a fingerprint, all of the app locks i mentioned will reject the new fingerprint until it is authorized by the app's preferred password. Also, notably, besides providing different semantics from what the operating system can provide (in the case where the app lock wraps everything useful within the app), doing it "client-side" is also more flexible because you can have certain accounts locked and others not. For instance, you might have a "more private" Fluxer account that you REALLY don't want to accidentally open in public, or want to prevent a nosy family member from looking at. It would make sense to lock just that account, instead of the whole app. You could of course achieve a very similar result by using the "private spaces" (not universally supported in all Androids!), but that would also mean the private account can't receive push notifications when that space is locked (which may be preferable! but it's also annoying if that's not what you'd prefer!).