Bot releases are visible (Hide)
Published by willmorgan almost 4 years ago
Published by willmorgan almost 4 years ago
Published by willmorgan almost 4 years ago
iProovSupport
is a separate export to facilitate a smaller critical bundle size for integrators.
import { iProovSupport } from "@iproov/web/iProovSupport"
window.IProov.IProovSupport
for the time being.version
property on the iProovMe
component.
window.IProov.version
.csp_nonce
option. See Content Security Policy.<link rel=preload>
for non-blocking parallel loading.Published by willmorgan almost 4 years ago
csp_nonce
option. See Content Security Policy.Published by willmorgan almost 4 years ago
iProovSupport
is a separate export to facilitate a smaller critical bundle size for integrators.
import { iProovSupport } from "@iproov/web/iProovSupport"
window.IProov.IProovSupport
for the time being.version
property on the iProovMe
component.
window.IProov.version
.<link rel=preload>
for non-blocking parallel loading.assets_url
's meaning is changing again, we're afraid...iProovMe.js
.Published by willmorgan almost 4 years ago
iProovSupport
is a separate export to facilitate a smaller critical bundle size for integrators.
import { iProovSupport } from "@iproov/web/iProovSupport"
window.IProov.IProovSupport
for the time being.version
property on the iProovMe
component.
window.IProov.version
.<link rel=preload>
for non-blocking parallel loading.assets_url
's meaning is changing again, we're afraid...iProovMe.js
.Published by willmorgan almost 4 years ago
iProovSupport
is a separate export to facilitate a smaller critical bundle size for integrators.
import { iProovSupport } from "@iproov/web/iProovSupport"
window.IProov.IProovSupport
for the time being.version
property on the iProovMe
component.
window.IProov.version
.<link rel=preload>
for non-blocking parallel loading.assets_url
's meaning is changing again, we're afraid...iProovMe.js
..browserslistrc
for the current targeted browsers.iProovSupport.js
checker as needed.Published by willmorgan almost 4 years ago
Published by willmorgan about 4 years ago
iProovSupport
is a separate export to facilitate a smaller critical bundle size for integrators.
import { iProovSupport } from "@iproov/web/iProovSupport"
window.IProov.IProovSupport
for the time being.version
property on the iProovMe
component.
window.IProov.version
.<link rel=preload>
for non-blocking parallel loading.sideEffects
and type
props have been added to the distribution's package.json
.
assets_url
's meaning is changing again, we're afraid...iProovMe.js
..browserslistrc
for the current targeted browsers.iProovSupport.js
checker as needed.Published by willmorgan about 4 years ago
Published by willmorgan about 4 years ago
progress_assessing_liveness
prompt_liveness_align_face
prompt_liveness_no_face
prompt_liveness_scan_completed
Published by GlenHughes about 4 years ago
client_error
key to the language file.prompt_kiosk_align_face
and prompt_kiosk_keep_still
have been added. See iproov-en.json for English translations.Published by GlenHughes over 4 years ago
Published by willmorgan over 4 years ago
base_url
option now requires a URL using https://
; the deprecated functionality of prepending the secure protocol has been removed.prefer_app
has been removed in favour of this automatic integration.prefer_app_options
has been renamed to native_sdk_options
sdk_unsupported
errors to be gracefully displayed to users, should a particular version of the Web SDK remain in production past its EOL.Published by Joe-Palmer over 4 years ago
The iProov Web SDK is now generally available, which officially brings the power of iProov Genuine Presence Assurance to web browsers on desktop, laptops, tablets, mobile devices, and kiosk environments.
The SDK is available as a JavaScript package on NPM which which is detailed on the GitHub page.
iProov Web can be integrated as part of a user journey on any modern browser. The iProov Android and iOS SDKs can be used within WebView based mobile apps, ensuring a consistent user experience with minimal additional integration effort.
The iProov Web SDK is shipped as a standards-based Web Component, which means that it can be integrated in virtually any frontend framework. Integrators can set options using the standard DOM attribute scheme, either through the tag itself or programmatically with JavaScript.
The web component emits its lifecycle events using the standards based CustomEvent model.
In terms of frameworks, iProov provides integration guides which are available for various modern frontend frameworks, as well as for ‘vanilla’ Javascript:
Full integration documentation is available on GitHub.
iProov Web maintains a close alignment with the iProov native SDKs, allowing a wide range of control for integrators who want to move beyond the default configuration.
Every effort has been made to ensure an optimised user experience across the wide range of devices and browsers that iProov supports.
The minimum base requirements for hardware are:
The minimum base requirements for browsers are:
If the web SDK is unable to detect a supported platform, the SDK emits an event which details the reason for lack of support, this can be used by the integrator to display a relevant message to the user.
If the user’s device is unable to complete the iProov process, our lightweight support check component can be used to guide them to a different journey.
iProov will maintain a full view of the system compatibility for each version of the client in the GitHub repository.
Published by Joe-Palmer almost 6 years ago
Published by Joe-Palmer over 6 years ago