Sorry, nothing in cart.
According to several reports and images that have surfaced online, it appears that WhatsApp is testing fingerprint authentication on the instant messaging app for Android, as confirmed by WABetaInfo on its social media page and a blog post.
There’s no arguing that WhatsApp is the biggest instant messaging application. This feat can be attributed to the many standout features of the platform, one of which is security. End-to-end encryption debuted on WhatsApp two years ago to ensure secure communication and make messages more private (like a face-to-face conversation) and now, Fingerprint authentication is coming to further up the security and privacy of messages and data on the app.
WhatsApp has reportedly introduced a new feature that will let users add their fingerprints to WhatsApp and make their chats remain safer. The information was spotted by the WABetaInfo. As per them the feature has been added to the latest beta update for Android devices and is present in WhatsApp beta v2.19.83. With this update, users can add their fingerprint as a secondary layer of biometric authentication, beyond the standard security lock of a smartphone.
The feature was already available for iPhones but for Android, it has only been introduced in the beta code now. This feature will be present under the ‘Privacy’ tab of WhatsApp’s account settings and choose to enable it will show a second pop-up that lets users decide an auto-lock frequency. Enabling this will automatically lock your WhatsApp account after one minute, 10 minutes or 30 minutes, depending on what you set as per your preference. This is meant to make it convenient and secure for individuals, who frequently use this chat application.
Image Source: wabetainfo
However, the feature is disabled for now, so users of the present beta app on Android devices will still not be able to use it. WhatsApp is possibly fixing the final bugs related to the fingerprint authentication, as a result of which the update will possibly be enabled in the subsequent beta updates. This suggests the feature is still some time away from seeing use in the stable build.