Skip to main content

In-display sensors or facial scanners: which will take off?

The fingerprint sensor may be moving back to the front...under the screen. Could this be the next big trend in mobile technology (see previous entry about current trend)? Or, will companies move the Apple way and opt for facial recognition for security?

With the debut of the iPhone X, Apple shifted away from the fingerprint sensor and debuted FaceID. Utilizing (arguably) some of the most advanced cameras and sensors, the iPhone X negated the need for fingerprint, bio-metric security by using 3D facial recognition to verify identity. In doing so, the home button vanished from the iPhone along with the ability to scan fingerprints.

Several months later, at CES, Vivo demoed the first phone using in-display fingerprint scanner technology; the idea being to remove bezels on the front as well remove the sensor from the back of the body. Prior to CES, many believed that Samsung would be the first to debut the technology, but they were held back by mass-producing and technological restraints.

While Vivo is significantly less significant than Apple, the announcement of the bio-metric technology now created a large decision for phone manufacturers to make: shift toward a new form of identity verification or shift the location of the old verification module. With this in mind, many eyes shifted toward Samsung and the direction they would take with the S9; personally, I found their answer rather safe. With the S9, Samsung debuted new facial recognition software that was not secure enough to be the sole sensor while also holding on to the fingerprint sensor (thankfully in the right spot this time).

In Samsung's defense, maybe the technology was still not ready for in-display recognition, and they did not want to go all out on facial recognition because they do not see that as the future of bio-metric security. However, it now appears that the technology may be ready for them to finally make the move. As reported by CNET, the Galaxy S10 may finally debut an in-display fingerprint sensor as deciphered from a Korean report. If this ends up being true, Samsung would be the first household name in mobile technology to include this technology; I would say utilizing it on their flagship phone would make the inclusion even more significant..

So what is the big deal about in-display sensors? Well, several things. First, fingerprint sensors were originally embedded in to the home button of phones thus finding a nice home on the front of phones. As home buttons from Android manufacturers such as Samsung disappeared, the sensor migrated to the back of the phone thus allowing the slimming of bezels. While many, like myself, find the back to be the ideal location for the sensor, it does cause problems for those who enjoy having their phone lay on a flat surface thus the desire to move it back to the front. The in-display sensor would allow a front facing sensor while also maintaining the progress toward bezel-less devices.

Personally, I prefer the fingerprint sensor on the back. When I pick up my phone, my finger rest perfectly on the sensor, but I am also one that does not commonly use my phone on a flat surface. In addition, I believe moving the sensor to under the screen leaves the phone vulnerable to a host of new problems. For example, I know there a large amount of people that continually use a phone with a cracked screen; will the sensor still work? Also, will the screen effect the effectiveness of the sensor? Also, will screen cleanliness impact the usefulness?

I am not against the new technology, but I do believe that is could be problematic. I have a wait and see attitude about the in-display technology; however, I will happily embrace it if it proves to be just as effective and secure. As it was only Vivo to produce a device with the technology so far, it remained to be seen whether it would ever reach mass adoption. But with Samsung possibly embracing the new sensor, will in-display fingerprint sensors become the next must-have for a flagship device?


Comments

Popular posts from this blog

Where, oh where did all of my wires go?

As I read through the comments on various mobile phone articles, I always see the same complaints: "Where is the headphone jack?" "No headphone jack? No thanks" "If it ain't broken, why fix it?" While I originally shared their contempt, I have since come to question where is all of this hate for less wires coming from? I admit that I am definitely not an audiophile, but in my opinion, Bluetooth headphones have come a long way and sound pretty solid to me. More importantly, looking at the bigger picture, haven't we been in love with the idea of losing wires for decades? As I write this blog from a wireless computer with a wireless keyboard navigated with a wireless mouse, I am reminded that we have been removing wires from everything possible for a very long time, and while there may have been resistance at the time, we have adopted this concept in to the norm. As a young kid, I remember growing up with a clear "house phone" (a rarit...

Where do tablets belong?

Last night, I had a sudden thought: where does my tablet belong in my tech life? I have always loved the thought of having a need and purpose for every piece of technology I own. For instance, my computer does all of my heavy lifting (photo and video editing) while my phone does all of communicating and daily living tasks. My Chromecast ? That is for tossing music and videos to my TV. Google Home Mini ? What a great little assistant for quick information and getting my day started. I use my Xbox for gaming while my Huawei Watch gives me quick updates and almost-hands-free communication. So, where does my Kindle come in? I originally bought my Kindle Fire to be a consumption device and makeshift pseudo-laptop as mine is not very portable. I thought I would use it for all of Netflix watching as I moved about the house as well as for reading plenty of books; I even intended it to be useful to bang out a quick blog post or article. We probably had a great relationship at first...and ...