Best Practice

• Add a cancel button
• Allow users to see all their credentials
• Authenticate the user if needed

Step3: Show credentials in the QuickType bar

What you need to do

• Provide credential identities to AutoFill
• Return passwords from extension
• Show custom authentication UI (optional)

Provide credential identities to AutoFill

Use the credential identity store

• Secure, never leaves device
• Writable only by your app and extension
• Read only by AutoFill
• Modifiable only when extension is enabled
• Update the store as needed
  - New credentials are available
  - Credentials are modified
  - Credentials are no longer available

• The store may be unexpectedly deleted
  - Extension is disabled, re-enabled
  - App provides stale credential identities
  - User restores from backup
• ASCredentialIdentityStore can help

Provide passwords from your extension

• Respond to the initial request quickly
• Users don’t see your UI yet
• AutoFill will cancel the request after a timeout
  - Except simulator and debug builds

Best practices

• Keep the credential identity store up-to-date
• Use ASCredentialIdentityStore incremental update APIs
• Keep extension UI to a minimum
• Avoid expensive setup in every viewDidLoad()

Step4: Allow Users to Configure Your Extension in Settings

• Your extension may require additional setup after being enabled
  - Provide credential identities for QuickType
  - Sign user into online service
  - Get user authentication or confirmation for QuickType
• AuthenticationServices provides API for this

Extension Development ⚠️

Best practices

• User separate view controllers
• Present or user view controller containment

• Extensions should be lightweight
• Use App Groups, shared keychains