September 15, +Marques Brownlee
posted a great review of the Moto 360 smartwatch. For those who are curious about some of his statements, here's the technical take.
In the review, he notes that not everything is optimized for circles, and questions whether Google might consider splitting into Square/Circle branches of Wear. You almost certainly won't see a split in Android Wear because Google has specifically created that split for applications. An Android Wear app contains two possible sets of layouts, one for circular displays, and one for round displays. If you only include a generic layout, the app can't determine the difference, and my apps are currently made that way. If you supply an alternative, however, Android will automatically select the appropriate layout based on your watch face shape.
He also discusses processor throttling, and is right on the mark. The OMAP3 is a very tested chip, and idles extremely well. (The OG Droid had a nearly identical chip down to the processor speed.) The part of Android that determines how the chip spins up and slows down is the governor. By default, Android uses a governor called "OnDemand". It's the same governor used by most desktop Linux distributions. It's basically a split between "userspace/interactive" which is optimized for apps, and "powersave" which waits a lot longer to spin up and keeps the processor clocked below its max. Chances are, Motorola tweaked the spin-up threshold on the ondemand governor to be weighted closer to powersave.