Thoughts on Moto X

My initial thoughts with the Moto X are that it's a great device, easily one of the best feeling, sized, and shaped devices of this year. The screen is big enough without the device being bulky, and Motorola says that over 70 percent of the front surface of the Moto X is display. I'm still not a fan of AMOLED, but in this case a lot of the features (active display) do need it to be power efficient. The customization options are novel and unique, even if they're limited to AT&T in the USA for the time being. The idea of a wood-backed phone excites me since it means each device will be unique and have different wood grain, and having some way to differentiate one's handset from all the other black squares out there would be awesome. Having the same device available on all the US operators is also a huge win for Motorola, who has been otherwise stuck to endless Verizon exclusives that dramatically limit the reach of its flagships, even if the Moto X isn't a single SKU solution for all the operators (I do not have cellular banding information for each variant). Even now though, we saw the announcement of some Verizon Motorola Droids that basically include the same hardware platform and a number of features from the X. 

The fruits of Google's interaction with Motorola are a bit more unclear. The Moto X runs a primarily stock UI, but it isn't entirely free of operator interaction – there's operator branding and light preloading, of course nowhere near the level that you'd get on a phone that goes through the normal interaction, but calling this "unadulterated android" still isn't factually correct, and it's definitely not Nexus with all that operator branding. I find myself puzzled as well that the Moto X isn't running Android 4.3. For other OEM partners, I can understand not having the absolute latest version of the platform running because of UI skinning and features, with a stock UI and operating under Google's umbrella, it's just a bit harder for me to explain away, especially given how far along Samsung and HTC allegedly are with 4.3 builds.

The last bit is pricing. The rumor and buildup led me to believe that Moto X would be priced like the midrange device the silicon inside misgives it for, but at $199 on contract it's priced just like a flagship halo phone with a quad core SoC. I realize specs aren't the be all end all for everyone, but I was hoping the Moto X would be the realization of an Android for the masses movement and platform direction from Google with the price to back it up, which would've been $199 with no contract. I have no doubt we'll see the Moto X move down in cost quickly, and it's premium, it's just surprising to see $199 out of the gate for what is a midrange platform (8960Pro) right now. 

I need to spend more time with the Moto X to really pass judgment. I've popped my personal SIM in and will use it as my daily driver for a while and give it the full review treatment. 

Touchless Control & Contextual Processor
POST A COMMENT

162 Comments

View All Comments

  • DigitalFreak - Thursday, August 1, 2013 - link

    This is Moto's "flagship" phone? LMAO Reply
  • prophet001 - Thursday, August 1, 2013 - link

    What armchairs do to quarterbacks amazes me. Reply
  • Jumangi - Thursday, August 1, 2013 - link

    Its got a duel core CPU and a 720p display. That's not what you pay $199 + 2 years for. Its 2013 not 2011. Reply
  • Dentons - Thursday, August 1, 2013 - link

    Sad to say, but you're right.

    Even though almost no one can truly tell the difference between 720 and 1080 on such a tiny screen, the dated processor, lack of microSD expandability, lack of spare battery, and small screen size mean I won't be able to recommend this to anyone.

    There are far better options available at the same price point. Tentatively, this looks to be a failure of imagination. Compared to the amount of hype, it's likely to be an outright failure.
    Reply
  • pseudo7 - Thursday, August 1, 2013 - link

    No microSD and no spare battery isn't a huge deal - i'd say most people don't need it, they just think they do. Reply
  • Reflex - Thursday, August 1, 2013 - link

    Yup, I thought I needed it, turns out I don't. Moved to a phone without it last October and I just don't miss either feature despite my earlier misgivings.

    I'd be more concerned with the out of date silicon and low res screen than with expandability options hardly anyone uses.
    Reply
  • Zink - Thursday, August 1, 2013 - link

    I have no problem with 720p at 4.7", it is the same DPI as an iPhone and Galaxy Note II users say 720p, even at 5.5", is good enough for the best phone available. Personally I care more about how the phone looks and the software than if I can detect perfect sharpness from 6" away. The SOC also isn't completely last gen, it is faster than a what the GSIII and Nexus 4 have for most task hopefully. Reply
  • jt122333221 - Thursday, August 1, 2013 - link

    The silicon isn't "out of date" though - it's using two Krait 300 cores, which is the same core the 600 uses. While it's only two cores instead of four, it's still got a lot of power behind it. If it were made up with Krait 200 cores, that would be last year's silicon (your standard S4, found in the US versions of the One X and SIII). Reply
  • Gigaplex - Friday, August 2, 2013 - link

    The S4 doesn't use Krait 200. The quad variant uses Krait 300 and the "octa" uses a mix of Cortex A15 and Cortex A7. Reply
  • ParkNation - Friday, August 2, 2013 - link

    The S4 certainly does use Krait 200 - see http://en.wikipedia.org/wiki/Snapdragon_S4 - the new chip in the only one in the entire S4 family to have Krait 300 CPUs. Methinks you've got Samsung on the brain and thought ppl were talking about the SGS4 phone, not the Snapdragon S4 SoC (these acronyms can get confusing). Reply

Log in

Don't have an account? Sign up now