01-03-2020 06:22 PM
52 123
tools
  1. ricflairwoo2's Avatar
    https://chromeunboxed.com/pixel-4-xl-reasons-to-buy/

    Lack of a fingerprint reader was a concern as well. With many of the apps I use leveraging this form of biometric authentication, I thought it would be months before Android app developers actually got around to adding face unlock since there’s only one Android phone on the market with it. Google surprised me here, too, and said that as of Nov. 1 all app that utilize biometric authentication must include face unlock in their next update. So that won’t be a concern for long either.

    Google laying down the law.
    11-03-2019 03:34 PM
  2. Kirstein Gourlay's Avatar
    I hope the upgrades don't take too long then.
    xzell likes this.
    11-03-2019 05:25 PM
  3. Mooncatt's Avatar
    I still don't plan to register my face on any device with that option.
    11-03-2019 05:41 PM
  4. benj0219's Avatar
    Sounds perfect. Link to more information? I couldn't verify the information anywhere.
    11-03-2019 05:52 PM
  5. beaner b's Avatar
    So when B of A or Starbucks don't include it in their next update, what's google gonna do?
    strikeIII likes this.
    11-03-2019 05:53 PM
  6. Lobwedgephil's Avatar
    Hopefully this is a big push for more support, which is badly needed. But it is very easy for developers to get around this without adding support.
    11-03-2019 05:54 PM
  7. benj0219's Avatar
    So when B of A or Starbucks don't include it in their next update, what's google gonna do?
    Exactly...
    11-03-2019 06:25 PM
  8. strikeIII's Avatar
    Guess what, it's November 3rd and I've gotten plenty of updates since the 1st from big name apps with no Face Unlock support. Hope it starts to ramp up soon.
    11-03-2019 07:00 PM
  9. ricflairwoo2's Avatar
    Guess what, it's November 3rd and I've gotten plenty of updates since the 1st from big name apps with no Face Unlock support. Hope it starts to ramp up soon.
    Not sure what apps you are referencing. I checked all of my credit card (Citibank, Chase, USAA) apps and banking app that used the fingerprint reader which equates to 4 total. None of them have been updated since either 20 September or 12 October. I think the updates will roll out together in the next few weeks.
    11-03-2019 07:27 PM
  10. PaulQ's Avatar
    Not sure what apps you are referencing. I checked all of my credit card (Citibank, Chase, USAA) apps and banking app that used the fingerprint reader which equates to 4 total. None of them have been updated since either 20 September or 12 October. I think the updates will roll out together in the next few weeks.
    Citi app has had face unlock since soon after the Pixel 4 release. It's a little odd because it tells you to use your fingerprint even though it scans your face but it works.
    RSchaad likes this.
    11-04-2019 03:15 AM
  11. cert15z's Avatar
    Citi app has had face unlock since soon after the Pixel 4 release. It's a little odd because it tells you to use your fingerprint even though it scans your face but it works.
    I just tried it. Works great, but it does say fingerprint.
    RSchaad likes this.
    11-04-2019 05:44 AM
  12. Lepa79's Avatar
    Google is losing its way. Android has always been about OPTIONS, not forcing users or app developers to do it "My way or the Highway". They should have kept fingerprint scanning and added face unlock. Not take that away and force everyone else to face unlock.
    11-04-2019 07:09 AM
  13. Jeremy8000's Avatar
    Google is losing its way. Android has always been about OPTIONS, not forcing users or app developers to do it "My way or the Highway". They should have kept fingerprint scanning and added face unlock. Not take that away and force everyone else to face unlock.
    I think you're mixing up Google's hardware and software decisions. Android IS still about options - and in this case, about adding the option for users for face unlock which provides more options, not less. FPS support isn't in any way being removed from Android, though the specific OEM hardware of the Pixel doesn't include it (much to my and many others' disappointment).

    As to the developers, Google has always had a catalog of evolving rules and mandates concerning apps that developers must meet to allow publication on Play Store, so this is nothing new in that sense.
    bhatech likes this.
    11-04-2019 09:24 AM
  14. mustang7757's Avatar
    I think you're mixing up Google's hardware and software decisions. Android IS still about options - and in this case, about adding the option for users for face unlock which provides more options, not less. FPS support isn't in any way being removed from Android, though the specific OEM hardware of the Pixel doesn't include it (much to my and many others' disappointment).

    As to the developers, Google has always had a catalog of evolving rules and mandates concerning apps that developers must meet to allow publication on Play Store, so this is nothing new in that sense.
    I think he really has it in for Google this year lol
    11-04-2019 09:29 AM
  15. Jeremy8000's Avatar
    I think he really has it in for Google this year lol
    I think I'm scheduled to board the bashing train in either 2023 or 2024, but can't find the email with the reservation details. Meanwhile I'll just go with what my opinion tells me instead of everyone else's.
    mustang7757, bhatech and VidJunky like this.
    11-04-2019 09:38 AM
  16. bhatech's Avatar
    I think you're mixing up Google's hardware and software decisions. Android IS still about options - and in this case, about adding the option for users for face unlock which provides more options, not less. FPS support isn't in any way being removed from Android, though the specific OEM hardware of the Pixel doesn't include it (much to my and many others' disappointment).

    As to the developers, Google has always had a catalog of evolving rules and mandates concerning apps that developers must meet to allow publication on Play Store, so this is nothing new in that sense.
    Well said, I was puzzled by the removing options part in Android. All they are doing is streamlining the API so that irrespective of what biometric authentication you have fingerprint or face or both, it'll work. What biometric are present depends on the hardware but they want to make sure apps are developed against the biometric API so that the actual hardware is abstracted from the app.
    11-04-2019 09:53 AM
  17. davidnc's Avatar
    https://chromeunboxed.com/pixel-4-xl-reasons-to-buy/

    Lack of a fingerprint reader was a concern as well. With many of the apps I use leveraging this form of biometric authentication, I thought it would be months before Android app developers actually got around to adding face unlock since there’s only one Android phone on the market with it. Google surprised me here, too, and said that as of Nov. 1 all app that utilize biometric authentication must include face unlock in their next update. So that won’t be a concern for long either.

    Google laying down the law.
    Yeah I heard that as well. That's great news
    11-04-2019 10:49 AM
  18. ricflairwoo2's Avatar
    Citi app has had face unlock since soon after the Pixel 4 release. It's a little odd because it tells you to use your fingerprint even though it scans your face but it works.
    I don't have a normal Citi card. It's for government travel use only. The app and services are completely different.
    11-04-2019 01:35 PM
  19. sulla1965's Avatar
    I believe I read Chase will accept face unlock 4 sometime in 4th quarter 2019
    11-04-2019 07:49 PM
  20. LeoRex's Avatar
    Google is losing its way. Android has always been about OPTIONS, not forcing users or app developers to do it "My way or the Highway". They should have kept fingerprint scanning and added face unlock. Not take that away and force everyone else to face unlock.
    That's not what is happening. They've deprecated the old API that print sensors used, replacing it with a far more robust API that eliminates a lot of the development effort to implement. It INCLUDES finger print scanning along with face unlock (and other biometrics based systems)....

    So they are replacing a limited, difficult to use and develop API with one that is flexible, standardized and extremely easy to implement.

    There is zero downside here... None.
    bhatech, xzell, Trees and 1 others like this.
    11-04-2019 08:16 PM
  21. Lepa79's Avatar
    That's not what is happening. They've deprecated the old API that print sensors used, replacing it with a far more robust API that eliminates a lot of the development effort to implement. It INCLUDES finger print scanning along with face unlock (and other biometrics based systems)....

    So they are replacing a limited, difficult to use and develop API with one that is flexible, standardized and extremely easy to implement.

    There is zero downside here... None.
    My bad then. I thought apps are being forced to use face unlock and away from finger print scanning. If it includes both and Google asking developers to migrate to the new API version, then I got nothing to be upset about hahahah. Thanks for the clarification.
    11-04-2019 08:32 PM
  22. hpilot's Avatar
    https://chromeunboxed.com/pixel-4-xl-reasons-to-buy/

    Lack of a fingerprint reader was a concern as well. With many of the apps I use leveraging this form of biometric authentication, I thought it would be months before Android app developers actually got around to adding face unlock since there’s only one Android phone on the market with it. Google surprised me here, too, and said that as of Nov. 1 all app that utilize biometric authentication must include face unlock in their next update. So that won’t be a concern for long either.

    Google laying down the law.
    Not true. My Evernote app was updated Nov. 5th, and no face unlock.
    11-06-2019 10:38 AM
  23. Jeremy8000's Avatar
    Not true. My Evernote app was updated Nov. 5th, and no face unlock.
    One explanation I would suggest is that perhaps this is for updates submitted as of November 1, with some updates that might have been submitted prior to that date taking time to go through the process of approval and publication.
    11-06-2019 10:54 AM
  24. Lobwedgephil's Avatar
    One explanation I would suggest is that perhaps this is for updates submitted as of November 1, with some updates that might have been submitted prior to that date taking time to go through the process of approval and publication.
    The issue is it is not really a "requirement". Developers are just warned that the app should meet the requirements, and get a warning if it doesn't, but they can just click that away and still submit the app for updates without updating the Biometrics. So this date will help, but it is really still up to the developer to update when they want to.
    11-06-2019 11:03 AM
  25. PaulQ's Avatar
    Maybe it does nothing but I have emailed/tweeted developers of some apps to ask and express my interest in the biometric update. Takes just a minute and it might give them a little nudge.
    xzell likes this.
    11-06-2019 01:02 PM
52 123

Similar Threads

  1. S9 "Hey Google" isn't responding at all
    By classact in forum Samsung Galaxy S9 & S9+
    Replies: 9
    Last Post: 11-15-2019, 12:29 PM
  2. [Game] Angry Face
    By DHSimple in forum Android Games
    Replies: 0
    Last Post: 11-02-2019, 09:58 PM
  3. Samsung gt-s6802 - EAP authentication
    By whitekoala78 in forum Samsung Galaxy Ace
    Replies: 2
    Last Post: 11-02-2019, 07:24 AM
  4. S9 "Hey Google" isn't responding at all
    By classact in forum Ask a Question
    Replies: 0
    Last Post: 11-02-2019, 04:58 AM
  5. how do i unlock my phone from a sd perm lock
    By Android Central Question in forum Ask a Question
    Replies: 4
    Last Post: 11-01-2019, 01:56 PM
LINK TO POST COPIED TO CLIPBOARD