NFC World

Android Q to let users log into Wi-Fi networks via NFC, QR or Bluetooth LE

Android Q supports ‘Wi-Fi Easy Connect’ for NFC, Bluetooth, QR credential sharing — 9to5Google — “Android Q enables you to use Easy Connect to provision Wi-Fi credentials to a peer device… The calling app can retrieve the URI through various methods, including scanning a QR code from a sticker or display, or through scanning Bluetooth LE or NFC advertisements.”


What's New in Payments

Android Q to add face verification for payments?

Android Q Beta 4: ‘Face authentication’ appears in settings, reveals some features — 9to5Google — “With the added support for face authentication, users will have the option of requiring eyes open to unlock. They will be able to use it to sign-in to applications and use it for payments, as well, according to new strings in the Settings app.”


What's New in Payments

Android Q to let Google Pay users quickly switch between payment cards

Android Q Beta 4: Google Pay cards could live in power menu w/ ‘Cards & Passes’ — 9to5Google — “Cards will apparently appear as soon as the power button is long-pressed and users can then swipe through them, presumably to switch the card being used with NFC payments. Based on the description, this carousel will also be able to show things such as loyalty cards and tickets.”


NFC World

Google to drop support for Android Beam NFC P2P transfers

Android Q won’t have Android Beam — Techradar — “Android Beam, the NFC sharing method where you put two phones back to back to transfer photos, videos, and other files, is nowhere to be found in the ongoing Android Q beta… At Google IO, we found out that it’s not coming back, either, according to the reps we talked to who are working on Android updates.”


Google releases Android Q Beta with added biometric authentication support

Introducing Android Q Beta — Google — “In Android Q we’re extending support for passive authentication methods such as face, and adding implicit and explicit authentication flows. In the explicit flow, the user must explicitly confirm the transaction in the TEE during the authentication. The implicit flow is designed for a lighter-weight alternative for transactions with passive authentication. We’ve also improved the fallback for device credentials when needed.”