poor FaceID implementation choices

[cap7ainclu7ch]

I've been having some issues with some of the choices that Apple has made regarding the implementation of faceid. I think its crazy that if it fails to authenticate once, it requires the user to manual swipe up again to get it to make another attempt. Wouldn't it be far superior to have it constantly be trying to authenticate while it sees a face (or at least until it fully confirms that it isn't the correct user). I've been finding that it is ridiculously easy to have it fail and then ask for my passcode.

It seems like some substantial software tweaks could make this a FAR superior experience, especially if they have users the option to bypass the lock screen once it authenticates. It just feels so damn clunky right now. I'm not saying it's awful, but its definitely not up to the standard that touchid set, and I'm finding myself getting more and more frustrated with it, especially with these absurd (IMO) decisions that they decided to implement on the software side. I get that battery life might be part of it, but I don't see why it has to go to the passcode screen so quickly after a failed read, especially with how many situations can lead to fails (lying in bed, jacket covering face, too far away, ect). It should be a more fluid process, as its very different than just placing your finger on the home button.

 

[thesaint024]

I've been having some issues with some of the choices that Apple has made regarding the implementation of faceid. I think its crazy that if it fails to authenticate once, it requires the user to manual swipe up again to get it to make another attempt. Wouldn't it be far superior to have it constantly be trying to authenticate while it sees a face (or at least until it fully confirms that it isn't the correct user). I've been finding that it is ridiculously easy to have it fail and then ask for my passcode.

It seems like some substantial software tweaks could make this a FAR superior experience, especially if they have users the option to bypass the lock screen once it authenticates. It just feels so damn clunky right now. I'm not saying it's awful, but its definitely not up to the standard that touchid set, and I'm finding myself getting more and more frustrated with it, especially with these absurd (IMO) decisions that they decided to implement on the software side. I get that battery life might be part of it, but I don't see why it has to go to the passcode screen so quickly after a failed read, especially with how many situations can lead to fails (lying in bed, jacket covering face, too far away, ect). It should be a more fluid process, as its very different than just placing your finger on the home button.

I don't disagree, but your suggestion has a big tradeoff. If the phone really is adapting each time you enter a passcode after a FaceID fail, then your phone would never get better at FaceID. I agree that the trigger is short though. Maybe it should try for a few seconds before giving up. But then those who are trying to get FaceID to learn would be really annoyed at how slow it is to get to passcode. So to answer, it's not "crazy", just a tradeoff. Not sure which I'd prefer more.

 

[RodThePlod]

Send your feedback/suggestions to Apple, here: https://www.apple.com/feedback/iphone.html

 

[cap7ainclu7ch]

I don't disagree, but your suggestion has a big tradeoff. If the phone really is adapting each time you enter a passcode after a FaceID fail, then your phone would never get better at FaceID. I agree that the trigger is short though. Maybe it should try for a few seconds before giving up. But then those who are trying to get FaceID to learn would be really annoyed at how slow it is to get to passcode. So to answer, it's not "crazy", just a tradeoff. Not sure which I'd prefer more.

I thought the same thing, but then I started to get additional failures and it just doesn't feel like its getting any better. Not sure if its my screen protector or what, but its definitely not improving for me and I'm constantly entering in my code to unlock.

 

[thesaint024]

I thought the same thing, but then I started to get additional failures and it just doesn't feel like its getting any better. Not sure if its my screen protector or what, but its definitely not improving for me and I'm constantly entering in my code to unlock.

Maybe a bit of a tangent, and I'm not doubting you on the failures, but I have to believe that the failures that some people are claiming happening so frequently means that the device is defective. I've heard about FaceID sensors not working after hard drops so misalignment or simple defects are quite possible. I can make my FaceID fail by not doing as instructed and keeping the phone between the distance thresholds or covering up parts of my face. If you're not doing that, I'd consider taking the thing back. It's not supposed to work like that. The people who say it works 95-99% of the time THEY DO IT CORRECTLY, aren't lying. I get the same results. You should expect/demand the same results.

 

[JPack]

I get that battery life might be part of it, but I don't see why it has to go to the passcode screen so quickly after a failed read, especially with how many situations can lead to fails (lying in bed, jacket covering face, too far away, ect). It should be a more fluid process, as its very different than just placing your finger on the home button.

Face ID can be defeated with a $200 mask. Within 6 months, I would not be surprised if it were defeated with a $20 mask.

I don't think battery life has anything to do with it. iPhone X is a 1st gen product and I think Apple is straddling the line between ease of use and Face ID security. They would rather be cautious than end up on the nightly news due to lax security.

 

[Newtons Apple]

I consider FaceID good for “casual security”. If someone what to defeat it, it looks like it could be done. Still like TouchID but it is gone now.