Traditional FIDO Authentication requires that your client app retrieve a challenge from the server as the first step to protect against replay attacks. In high latency networks and on low-bandwidth devices, there could be a noticeable delay between the user opening the app and seeing the biometric prompt to authenticate.
You can avoid this issue by using Quick Authentication. During registration, the Server sends information that the App SDK uses later to generate the challenge for authentication. This information is valid for the lifetime of the registered authenticator and your mobile app stores this information. The App SDK then uses the local time and other data to derive the challenge without interacting with the Server. The Server remembers each challenge until it expires and uses it to prevent replay attacks.