Software UX

As is always the case, there’s a perpetual debate over the role of the OEM when it comes to Android devices. For better or worse, Samsung seems to believe that they need to add their own framework and UI over Android. To some extent, I suspect that most users are going to find stock Android to be rather spartan out of the box, so it does make sense for OEMs like Samsung to continue adding their own custom applications and frameworks to help differentiate themselves from the competition.

With the Galaxy S5, it was evident that Samsung had dramatically changed their design direction for TouchWiz, but I would argue that their design aesthetic still wasn’t quite perfect, and performance wasn’t completely there either. With the Galaxy S6, Samsung had gotten closer to the mark in some ways, but the continued use of excessively neon colors just made parts of the UI feel off at times, and performance still wasn’t perfect.

With the Galaxy S7, performance has improved noticeably, but it’s really hard for me to say whether this is because Samsung has improved their codebase, or if a faster SoC is just making it harder to notice areas in need of optimization. At any rate, while the Galaxy S7 isn’t perfectly smooth - dropping frames now and then - it is sufficiently performant that you’re not going to find distracting lag.

The default theme of the Galaxy S7 continues to feel pretty similar to the Galaxy S6, so for the most part things are acceptable here, but the use of color is still a bit excessive as a number of icons still use neon colors rather than more neutral pastel colors. Of course, the theme store now has a number of Material Design themes, which greatly improve the situation. I installed one pretty much immediately, which helps make the device feel a lot better in everyday use. However, I’m still of the opinion that this is something that a user shouldn’t need to do out of the box, so this is an area where Samsung can improve.

The other features that Samsung touted for the Galaxy S7 are interesting, but I’m not really sure they’re all that well executed. Always-On Display is nice to have, but for some reason it's quite reluctant to turn off the display when the ambient light sensor and proximity sensor are covered. As a result I turned it off as it’s clearly going to be contributing to idle battery drain in situations where it shouldn’t.

I also found that the fingerprint scanner is pretty much identical to the one in the Galaxy S6, which isn’t entirely surprising as both identify themselves as a Synaptics fingerprint scanner. Both still seem to be quite sensitive to the initial training period and in my experience won’t really work all that well if you don’t cover your entire fingerprint effectively during that period.

Other than this, TouchWiz doesn’t really stand out in any way as of now. Of course, Samsung Pay will be interesting for me to try as I still regularly run into terminals that don’t support NFC in any shape or form, but I haven’t really been able to spend much time testing Samsung Pay yet. I don’t really find TouchWiz to be a bad thing at this point, but I’m not really sure it’s a good thing either. With a serious emphasis on optimization and a major aesthetic overhaul, it’s entirely possible that I could find myself saying quite differently in the near future, but for now if you found the Galaxy S6 and Note 5 OEM UIs to be usable you’ll find the Galaxy S7 to be usable as well.

Display Initial Conclusions
Comments Locked

202 Comments

View All Comments

  • hansmuff - Tuesday, March 8, 2016 - link

    I have a question about that. Is Chrome supposed to be an equalizer between the platforms? From a practical standpoint, the browser that Samsung ships is in some ways better optimized so I use that instead. Am I really missing out by not running Chrome on my S6?
  • lilmoe - Tuesday, March 8, 2016 - link

    You're not missing out at all, the stock browser is much better. I use it, and have it synced with my FireFox account (bookmarks and tabs).
  • zeeBomb - Tuesday, March 8, 2016 - link

    I wanna see a test done on RBrowser or a Qualcomm optimized browser with the CAF Aurora files (does make your browsing up to 40% faster, you're welcolme)
  • grayson_carr - Wednesday, March 9, 2016 - link

    Chrome is very poorly optimized for Exynos processors, so you aren't missing out on your S6, but for devices with Qualcomm processors, Chrome typically runs pretty well.
  • Ratman6161 - Tuesday, March 8, 2016 - link

    I'm wondering if the situation has changed any with Android 6. I'm assuming that all the test results for the S7 were with Marshmallow while for the S6 they are with Lollipop. I'm pointing this out because my Note 5 just got the Marshmallow update and after the update, Chrome has improved so much that I'm now using it as my default when I never did before.

    Might be interesting seeing a test that included s6 with Lollipop, S6 with Marshmallow and S7 to see how much of the difference is actually attributable to the OS update???
  • Ryan Smith - Tuesday, March 8, 2016 - link

    Unfortunately Samsung's browser is not available on our Verizon-branded sample phone. The phone only ships with Chrome, and it is not possible to install Samsung's browser at this time.

    The Verge is reporting that this is a Verizon decision, and that all Verizon S7s are like this.
  • id4andrei - Tuesday, March 8, 2016 - link

    What an interesting turn of events. Wonder why would Verizon be irked by Samsung's browser. Any thoughts Ryan? Maybe default adblocking since Verizon is also a media company.
  • Ryan Smith - Tuesday, March 8, 2016 - link

    At this point it's open to speculation. But I believe Verizon pulled the Samsung browser from the S6 as well, in which case this is nothing new.
  • Ratman6161 - Wednesday, March 9, 2016 - link

    I'm assuming my Verizon Note 5 would be the same as the Verizon S6? My note 5 has the browser that just says "Internet". Is that the one you are calling the Samsung Browser? Either way, Chrome is not the only browser on my phone. I got the 6.01 update last friday and still have both browsers avaiolable after the update.
  • tipoo - Tuesday, March 8, 2016 - link

    To me it still feels like Kyro doesn't aim high enough, given A9 has been shipping for months, in volume, and we're likely closer to A10. Even if A10 is a "tick" with a modest 20% performance boost, the cycle of staying behind it continues.

    That's the benefit of large profit margins I guess, and since just about no one but Samsung was making Android handset profits, no one was probably ordering a huge die with high IPC. Kyro comes a long way, and I'm glad they're going 2+2 with higher IPC rather than 4+4, but I guess I would have just liked it to go further and actually leapfrog the A9.

    Samsung does have their own custom core in development, wonder how that compares to Qualcomms Kyro.

Log in

Don't have an account? Sign up now