Introducing VIDA Identity Stack: All of VIDA, in one place 🎉
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Supported Browsers & Recommendations

The VIDA Web SDK officially supports the browser versions listed in the Supported Browsers matrix below. These are the versions VIDA actively tests against and fixes bugs in. Older versions of the same browsers may continue to function in practice but are outside the scope of active testing and support.

The SDK performs runtime capability checks during the process. If the browser does not meet the technical requirements, the SDK surfaces error code 70003 (browser or device doesn't support this functionality) via the onError callback and displays an "Unable to proceed" screen to the end user.

Supported Browsers

Browser
Minimum Supported Version
Released
Notes

Chrome (desktop and Android )

101 and above

April 2022

Chromium-based; covers the majority of installs

Edge

101 and above

May 2022

Chromium-based; same release cadence as Chrome

Firefox (desktop and Android )

115 and above

July 2023

Firefox 115 is the current Firefox ESR (Extended Support Release), commonly used in enterprise environments.

Safari (iOS and macOS )

16.4 and above

March 2023

Requires iOS 16.4 or macOS 13.3 or later. Safari 16.4 introduced the WebAssembly capabilities required by the face-detection runtime.

WebView - iOS (WKWebView)

16.4 and above

March 2023

Compatible,Requires the host native app to configure WKWebView correctly.

WebView - Android

101 and above

April 2022

Compatible,Requires the host native app to configure the webview correctly.

Secure Storage and API Call Recommendations

Server-Side Storage:

  • Store the client_id and client_secret securely on your server.

  • Do not expose these credentials on the client-side.

Server-to-Server Communication:

  • The API call to obtain the bearer token must be made from your server to Vida's server, ensuring secure communication.

Signing Key:

  • Vida will provide a signing key along with the client_id and client_secret.

  • Store the signing key securely on your server.


When initialising the Vida SDK:

  1. Obtain the Bearer Token

    • Use the provided credentials to obtain a bearer token securely from your server.

  2. Retrieve the Signing Key

    • Retrieve the signing key that was securely stored on your server.

  3. Pass Token and Signing Key to SDK

    • Provide both the bearer token and signing key when initialising the Vida SDK by passing them to the init method.

Last updated