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

  • jjj - Tuesday, March 8, 2016 - link

    Oh wow, you had 1 must do here, run GFXBench long time perf and you fail to do so, keeping everybody in the dark about the 1 thing we don't know.
    That 1 key result has 10 time more value today than this article...
  • Ryan Smith - Tuesday, March 8, 2016 - link

    There was enough time to run one battery life benchmark or the other one. We picked the web benchmark, as that's the more useful of the two.
  • hans_ober - Tuesday, March 8, 2016 - link

    Add it for the full review.

    Hoping for a deepdive on S820/ Exynos/Kirin950/A9? like the E7420 deepdive you guys did.
  • Ryan Smith - Tuesday, March 8, 2016 - link

    You'll see a GFXBench rundown in part 2.

    As for a deep-dive, we'll be doing some architectural information, though power logging ala the E7420 review will be a separate, larger writeup.
  • hans_ober - Tuesday, March 8, 2016 - link

    You've made my day :)
  • jjj - Tuesday, March 8, 2016 - link

    If true that's a bad business decision especially when you did run 2 different battery tests.The fact that the article tries to dismiss the GPU throttling by claiming that mobile gaming is short sessions does seem to suggest a lack of understanding. Sure casual gamers that dgame just to waste time will go for short sessions and less demanding games but for them the perf is also of little to no relevance. Users that should care about the GPU perf are the ones that play longer sessions.
    It's also of dubious ethics to label the GPU perf in any way without knowing this key metric and not doing so is essential in differentiating AT from others.
  • Cygni - Tuesday, March 8, 2016 - link

    Mad about telephone reviews.
  • Kepe - Tuesday, March 8, 2016 - link

    Why don't you just start your own tech-related website and write your own reviews, "jjj". You don't seem to do anything other than bitch and moan about every single conceivable thing you can come up with. Just gtfo and do things better by yourself, as you seem to know how everything should be done. If you write some good stuff, maybe you'll earn a buck or two, too.
  • maximumGPU - Wednesday, March 9, 2016 - link

    Second that. Never read anything except criticism from that guy on every post. Gets old very quickly.
  • retrospooty - Thursday, March 10, 2016 - link

    3rd it... I was on with him on a separate thread. Seriously hard headed, and overthinking it.

Log in

Don't have an account? Sign up now