Upcoming Google Chrome release is eliminating the need for manually entering or copy-pasting OTP onto a web page. OTP authentication is highly common these days. But difficulties with the manual user flow requiring users to switch between their SMS app and a web page to retrieve and enter the SMS code often lead to inconvenience. This is something Google wants to fix in the Chrome 84 update.
Google Chrome supports Web OTP API
Google Chrome 84 beta now supports Web OTP API, Web Animation API improvements, New Origin Trials, among other things. Describing the most-awaited integration of Web OTP API, Google wrote:
“The Web OTP API (formerly called the SMS Receiver API) helps users enter an OTP on a web page when a specially-crafted SMS message is delivered to the user’s Android phone.”
“With the Web OTP API, developers can help users enter the code with one tap.”
Microsoft has observed a noticeable increase in consumption of passwordless authentication methods like two-factor authentication (2FA) and One-time-password (OTP) authentication see massive adoption.
Google is also bringing certain Web Animations API improvements in Chromium 84. These changes enable developers to exercise greater control over web animations thanks to the Web Animations API.
Web animations partly exist in Google Chrome for some time, however, the newly-added changes significantly speed up the process while developers can control how effects are combined and how animations interact with other app features.
Google Chrome 84 also introduces new origin trials allowing users to try new features and share feedback on “usability, practicality, and effectiveness” to the web standards community. Developers are free to register for any of the origin trials supported in Chrome, as follows:
- Cookie Store API
- Idle Detection
- Origin Isolation
- WebAssemply SIMD
- Content Indexing API
- Wake Lock API Based on Promises
Google Chrome 84 beta is out for Windows, Linux, macOS, Android, and ChromeOS.