Skip to main content

​
In-App Nudge: After Unlock (Post-Authentication)

This In-App Nudge appears immediately after users unlock the app with local biometrics, offering them the opportunity to create a passkey for enhanced future authentication. This approach maximizes visibility but triggers two consecutive biometric prompts.
Local Biometrics vs. Passkeys: Local biometrics (Touch ID, Face ID, fingerprint) re-verify your identity WITHIN an already authenticated session to protect app access. Passkeys, on the other hand, perform INITIAL remote authentication to establish your identity with the backend server. They serve complementary purposes: local biometrics protect the app session, while passkeys enable secure, phishing-resistant login. By creating a passkey after local biometric login, users gain a superior authentication method for future logins while still benefiting from local biometric protection for app access.
  • iOS
  • Android
append-after-local-biometric-ios-native.png

Native: iOS In-App Nudge after unlock

1

App unlock using local biometric

  • User unlocks the app using local biometrics (e.g., Touch ID, Face ID or PIN).
  • User is now authenticated within the app session.
2

In-App Nudge appears immediately after unlock

  • Smart display logic: Passkey Intelligence first determines if the nudge should appear by checking:
    • User doesn’t already have a passkey on this ecosystem/OS
    • Device is passkey-ready (has screen lock/PIN configured)
    • Context is appropriate
  • If conditions are met, the In-App Nudge appears immediately offering passkey creation.
  • This approach maximizes visibility but results in two consecutive biometric prompts (unlock + passkey creation). Some developers prefer the After CTA approach to avoid this, though immediate triggering ensures higher exposure.
3

User chooses to create passkey

  • If user accepts, OS-native biometric modal appears for passkey creation.
  • User authenticates via biometrics (this is the second biometric prompt in sequence).
4

Passkey creation successful

  • User successfully creates a passkey and it is now linked with the user account for the respective native app.
  • Future logins will use the passkey for superior security.
⌘I