Software & Sense

The HTC One runs Android 4.1.2, a choice which might seem alarming, but was done for stability and quality reasons, although 4.2 is coming. I think it might sound bad to ship with 4.1, but even Google acknowledged that 4.2 was primarily a release with more tablet features than something for smartphones, after all both are still Jelly Bean. Sense 5 replaces Sense 4 or 4+ which shipped on the One X and X+, and brings a radically different themed UI this time. I was able to survive with Sense 4, and Sense 4+ brought a lot of improvements, what we’ve seen of the new Sense 5 looks like it follows more Holo design rules than any of the other OEM skins I’ve seen so far. All of the Sense UI fonts and system fonts are Roboto, the font Google made for Android 4.x, though it’s often one of the lighter condensed weights. In Sense 5, all the first party HTC applications now also use the pivot bar, which was a key design element introduced as part of the Holo guidelines. Icons and menus are now very flat in Sense 5, giving it a much more modern look, though there are still some gradients if you hunt around for them.

Probably the only huge deviation from Android is the inclusion of a completely new homescreen. Instead of having a grid of icons, the leftmost pane is home to a new feature called the Blinkfeed, which aggregates together content from a variety of online sources, media on the device (photos, videos, events), calendar events, and social media from linked accounts. The idea is to provide a quickly parsed visual menu of information to consume while glancing at the device. There are still widget panel homescreens, and the menus are sticky so that pressing home returns to the homescreen you were last on, in case you want to primarily use a widget panel as home instead of Blink.

The launcher also gets changed around in Sense 5. By default applications come sorted into logical folders, both to hint to users this is possible, and also to reduce anxiety for new users first diving into the launcher. The default view is a 3x4 grid which actually looks very refreshing, there’s still an option for a 4x5 grid for those wanting more density. Perhaps the biggest, most welcome improvement is that by default all operator applications will ship inside of a folder, rather than scattered all about the grid.

Another interesting choice is the decision to go with two capacitive buttons at the bottom of the HTC One instead of three. Last cycle, HTC got burned by following the Google guidance and doing away with the menu, err, “action overflow” button, leaving an on-screen action button in the overwhelming majority of Android applications that have yet to move away from this model. As a result, other players who included the menu button saw no black bar at the bottom. There’s also no app switcher button on the HTC One. Instead, just back and home. To get to an application switcher (which is now a 3x3 grid of thumbnails), one has to double tap the home button. Menu can be optionally enabled as a long press on the back button in a menu similar to what was added later in the One X. I think getting rid of a button is potentially risky, but probably simplifies things for new users.

Final Words

The HTC One industrial design is without a doubt the most striking I’ve seen from an Android phone to date. Unibody metal construction is something that at the high end we’ve only really seen out of Apple, and with the One, HTC has a major opportunity to set itself apart with a dramatically different in hand feel. Actively tuned antennas to make this possible without unintended attenuation, as well as improved CNC manufacturing volume are really the two enablers here.

Second only to the aluminum unibody story that is of the camera on the HTC One. HTC is taking perhaps the biggest risk of all with the camera, by choosing what is almost undeniably the right course of action and going against the prevailing trend of increasingly smaller and smaller pixels to drive the number of megapixels up. Megapixels is really the only number that has been sold to consumers, and with a 4.0 MP sensor, it’s instantly easy to see how the messaging will have to be set right for average consumers to appreciate that they’re getting around the same approximate size sensor as ship in other smartphones, if not slightly larger, but with dramatically bigger pixels. The result is, from my short time holding the HTC One next to a One X+, a dramatic difference in low light sensitivity, noise, and dynamic range indoors. The inclusion of optical image stabilization further improves things, and from a camera point of view the HTC One appears to be without a doubt the most serious Android smartphone camera experience.

HTC is announcing that in the USA the HTC One will be coming to AT&T, T-Mobile, and Sprint as the HTC One. Notably absent from that list is Verizon, unfortunately. Internationally HTC has an impressive list of operator partners, which I’ll spare going over in excruciating detail. The problem with the HTC One X wasn’t so much hardware as it was marketing and the fact that it only existed on one operator in the USA by that name. This time around, it’s one name, one brand, with no adulteration.

To say that the HTC One takes some bold risks is putting it lightly, but the hardware I’ve seen is impressive and without a doubt the best out of HTC, or any Android handset maker for that matter, to date. It’s too early to call who will be on top after this next cycle, but HTC seems well positioned with the HTC One at the top.

Abandoning the Megapixel Race and Shooting for Quality
Comments Locked

139 Comments

View All Comments

  • aegisofrime - Tuesday, February 19, 2013 - link

    Believe it or not, the HTC One looks strikingly similar to a Chinese phone that was released a few months ago. Take a look:

    http://i.imgur.com/IX3Qqsi.jpg
  • Silenus - Tuesday, February 19, 2013 - link

    For me it is tremendously refreshing to finally see someone other than Nokia focusing heavily on camera quality and features...and NOT on megapixels. Larger pixels, F/2, and optical stabilization is what I've been waiting for in an Android phone!
  • amdwilliam1985 - Tuesday, February 19, 2013 - link

    Yep, waiting for a test of HTC One against Lumia 920.
  • BoloMKXXVIII - Tuesday, February 19, 2013 - link

    As someone who does not use social media, Blinkfeed is useless. Yes, you can move it off the main page, but you cannot turn it off. All those updates to the tiles keep burning battery. As for the battery, it needs to be larger. Phones do not need to be so thin you can shave with them. The DO need to last all day (with all day use). While local storage is very good, I still want the microSD card slot. Transferring large files/large numbers of tiles/viewing photos from my REAL camera is just easier with microSD. All aluminum body is dead sexy, but aluminum is a fairly soft metal and will scratch easily. Must have a case. FINALLY someone (other than Nokia) is doing something about the cameras on cell phones. Low light sensitivity always suck on cell phones. Glad to see this one being addressed. 4 MP is plenty for a phone. Want a picture you can blow up to life size? Use a DSLR. Most people are not talking about the addition of IR. This is big for me! With IR, Bluetooth and Wifi I can control everything in my house! Finally, can the phone be purchased unlocked? If so, how much? I don't think this is "the" phone for me but I hope HTC uses some of these features in future phones (a max battery version would be nice).
  • tomeklutel - Tuesday, February 19, 2013 - link

    No AMOLED, larger and heavier than S2, this phone sucks.
  • bernstein - Tuesday, February 19, 2013 - link

    who the fuck wants amoled? everyone i know who owns a galaxy says the're great except for screen brightness.... go figure.
  • Sm0kes - Tuesday, February 19, 2013 - link

    It's made of metal..... so.... umm.... weight wise, that's not really a surprise.

    Also, the display has yet to be tested. simply stating that it isn't AMOLED is meaningless. I'll reserve judgement until we see test results and more details.
  • bernstein - Tuesday, February 19, 2013 - link

    @anand i really wonder if a 13MP sensor of the same size (amounts to ~1µm per pixel) and using 4 sensor pixels per image pixels in low light wouldn't be the better choice...
    - great big outdoor pictures
    - small but bright indoor pictures...

    at least in theory this 4:1 mapping should result in approx. the same performance, or is this impractical???
  • nerd1 - Tuesday, February 19, 2013 - link

    You don't need large pixels for brighter image, you need long exposure.

    And yes, pixel binning (essentially resizing) will produce almost as good results as larger, fewer pixels. One prime example is Nikon's D800.
  • pshann - Thursday, February 21, 2013 - link

    According to this website (http://lifeinmegapixels.com/blog/2012/01/pixel-bin... Post-process pixel binning doesn't improve the picture quality...

Log in

Don't have an account? Sign up now