Galaxy S6’s improved fingerprint scanner lets you log into websites with one touch [VIDEO]

The Samsung Galaxy S6 features improved finger scanning hardware that gives us something functionally identical to Apple’s highly-touted Touch ID, but its software-side enhancements build a case for the S6 as the benchmark for fingerprint authentication. Take for example the newly added ability to login to your favorite websites with just the touch of your finger.

While not a full-fledged password manager, Samsung’s finger scanner now sports the ability to securely store login credentials for use in the phone’s web browser. Find the site you want to login to, scan your finger, and the phone’s software will autofill the form. No more typing in usernames or fumbling over your super secure passwords (they are super secure, right?).

The first time you log into a site, the Galaxy S6 will ask you if you want to store the credentials and use the finger scanner to authenticate website sign ins in the future (provided you have already set up the fingerprint reader). You’ll have to do this individually at first for each login, so you can choose which sites require authentication.

While Apple has done a lot to improve the Touch ID experience and open it up to third-party developers, it has been slow to roll out core functionality in the same way that Samsung has with their Galaxy line. Before, we could say Samsung’s hardware lagged behind, but now it seems Apple may be the one with some catching up to do.

The latest Chrome Beta adds support for push notifications from websites

Google loves the web. They want everyone to do everything inside of the Chrome browser. We’ve seen them add more and more features to Chrome that allow websites to act like apps. Chrome in Android 5.0 treats tabs like apps when you press the “Recents” button. Websites can even change the color of the status bar. Google’s next step is to allow websites to send notifications through Chrome.

In the latest build of Chrome Beta (42) they’ve including two new APIs that allow sites to push native notifications to users even if the website is not currently opened. Here’s the tech-speak behind how it works:

After the user has granted permission, a developer can use the new Push API to remotely wake up their service worker using Google Cloud Messaging. Once awake, the service worker may run JavaScript for a short period but in this release it is required at minimum to show a user-visible notification. Each notification includes a ‘Site Settings’ button, allowing users to easily disable notifications for a site.

This is a really big deal. As mobile sites and browsers get better there is less reason to download apps. Some mobile sites are already better than their app counterparts (*ahem* Facebook), but we stick with apps because they offer a native experience. If websites start adopting these new APIs it could change the way we use apps.

Another notable feature in Chrome Beta 42 is promoted home screen shortcuts. If Chrome detects you visit the same site a lot you will see a pop-up suggesting you add a shortcut to the site to your home screen. Once again, this is a direct shot at apps. Google will be actively urging users to treat websites like apps by placing them on the home screen. More info about Chrome Beta 42 can be found on the Chromium Blog.