How Apple and Motorola made me freeze my smartwatch purchase plans

This article may contain personal views and opinion from the author.
How Apple and Motorola made me freeze my smartwatch purchase plans
The wearable era has begun in earnest, which means it is now time for us (and you) to take a look at what we know about the devices on the market now, what's on the way, and where the potential lies with these devices. The big news this week has been the release of the long-awaited Moto 360 and the announcement of the long-rumored Apple Watch. Unfortunately, the two have come together to convince me that now is not the time to buy a smartwatch.

As I've mentioned before, I'm an Android user, and as I talked about recently, Android Wear has grabbed my attention despite the fact that I haven't worn a watch on a daily basis for 15 years. I have been looking forward to the Moto 360, but what I've seen so far has soured me a bit on the device. And, while I have no intention of buying an iPhone 6 or an iWatch Apple Watch, Tim Cook's announcement had its intended effect on me and has made me put my plans to buy a smartwatch on hold for now. 

Motorola's slip-up

My issues with the Moto 360 have been covered by many outlets, and it all stems from the fact that Motorola made the terrible decision to use the TI OMAP 3 chip in its smartwatch. While we didn't know exactly which model of OMAP 3 it was at first, the iFixit teardown has shown that it is the same chip that was used in the MOTOACTV, which was released almost 3 years ago. As John mentioned in our review of the Moto 360, the processor choice has had a slight impact on performance, and the 360 isn't as "buttery smooth" as the Android Wear devices from LG and Samsung which use the Snapdragon 400 SoC. 

The performance difference alone is slight enough that it hasn't had a huge impact on my decision, though. The real trouble caused by the processor choice is with battery life. As many outlets have mentioned, the OMAP 3 used a 45-nanometer production method, which was great back in 2010, but doesn't stack up to today's standards. The Snapdragon 400 uses a 28-nanometer production process, meaning transistors are more tightly packed and more energy efficient. 

Ron Amadeo over at Ars Technica ran some benchmarks on the three current Android Wear devices. He found that the Moto 360 was competitive on most of the performance benchmarks, but lagged well behind in battery life (seen above). And, that is exactly what comes through in usage, both because of the processor and the fact that the 360 has a physically smaller battery than the competition. The Moto 360 still looks beautiful, and is a marvel of industrial design. Unfortunately for Motorola, Google has taken control of Android Wear and doesn't allow for any customization, so these watches have to live and die by the hardware. 

The Moto 360 looks beautiful, but the software is the same as every other Android smartwatch; and, I find it hard to justify $249 for a great-looking device with a small battery and a 4 year-old processor. Maybe when the price drops, I'll give in. But, by that time, there may be something much better on the market. 

Apple freezes the market

The other big trouble that I ran into was Apple's announcement on Tuesday. As I mentioned, I'm not going to be buying an Apple device, but I don't think that Tim Cook was really targeting Apple customers with his Watch announcement this week. I believe that Tim Cook had three major aims with announcing the Apple Watch:

  1. Quiet the rumors - we all knew the Apple Watch was coming, and Apple's stock would have taken a hit if it had left the rumors to fester until next year. 
  2. Prep the ecosystem - this is the same reason why the Android Wear SDK was released in March, but devices came in late June. Android Wear doesn't really allow for full apps in the same way that Apple seems to be planning its for its Watch, so Apple wants to get developers working as soon as possible. The Apple Watch SDK isn't out yet, but should be coming soon. 
  3. Freeze the market

The last one is, in my opinion, the biggest one. Apple knew that it couldn't get its smartwatch to customers until next year, but it also couldn't leave Android Wear to take over the market. Announcing the Apple Watch now, and showing everything that it can (theoretically) do, will help to freeze the market a bit. The Apple faithful would have waited anyway, but Apple has more concerns beyond those customers. Part of keeping Android Wear from growing is keeping users from switching from iOS to Android, and that is a key of the iWatch. (I'm sorry, I can't keep writing Apple Watch every time; it's too awkward. You'll all keep up if I just use iWatch here and there, right?)

The iWatch is locked to the iPhone, so if anyone was considering an Android switch, this announcement might have pulled them back a bit. But, beyond that, there were those, like myself, who were on the fence about buying an Android Wear device, but are now going to hold off because Apple has shown flashes of capabilities that wearables could have, but don't yet. The Apple Watch is not a perfect device, far from it actually; but, it has a couple of truly special ideas. 

Apple's feature creep

I'll get to the truly special ideas in a minute, but first I want to dive into the odd troubles in what Apple announced with its smartwatch. As mentioned there were a couple of features that Apple announced that were good enough to make me put my smartwatch purchase plans on hold, but there were also quite a few things in the announcement that seemed completely off-base for an Apple device. It is clear that Tim Cook is taking the Apple Watch on as his baby. This is the turning point where he takes over and leaves Steve Jobs in the past. Gone is the "i" naming. As awkward as it is to say Apple Watch all the time, it serves as a constant reminder, for good and bad, that this is Tim Cook's Apple now, and this is his flagship device. 

Unfortunately, as far as can be said with the information at hand, the Apple Watch has some items to polish before releasing the device. The aim of the device was obviously to make it feel familiar to traditional watch users, and that comes through specifically with the "digital crown". The idea makes sense on the surface - keep a traditional hardware feature, but repurpose it for a new age. The trouble is that in practice it seems to just add complexity, which is something Apple has always tried to avoid. Sure, the crown will make it easier to scroll lists, and Apple was right to point out how silly pinch-to-zoom is on a smartwatch; but, double-tap-to-zoom would work fine, and the crown makes no sense with the main interface Apple has created. 

The iconic image of the Apple Watch is already the app swarm home screen. The thing is that the app swarm is a multi-directional collection of icons, and the digital crown can only move in two directions. For most usage of the Apple Watch, it seems like the best options are going to be to either ignore the crown, or to have to awkwardly switch between the crown and the touchscreen. Either way, Apple has added a feature to its Watch that has limited use, and complicates the user experience. 

But, the biggest trouble with the Apple Watch is the software design. Let's imagine for a second that you don't know anything about wearable software, but you knew about the past design temperaments of Apple and Google, and I showed you these side-by-side comparisons:

I'm willing to bet that just seeing those screens, most people would assume that the simple and clean UI design on the right was made by Apple, and the overly dense and complicated UI design on the left was made by Google. I can understand Tim Cook wanting to make the Apple Watch his baby, but it seems like he has lost his grip on the Apple ethos. The Apple Watch UI is customizable, which even Google thought was trouble, and that's something of a red flag. 

We'll have to see how more full-fledged apps work on the iWatch, but in general, I've come to think that Google has the right idea with Android Wear with the focus on quick, glanceable information. Long interactions with a smartwatch don't work well, but Apple seems to want to allow longer interactions. The Apple Watch also has an odd look of feature creep to it. For those who don't keep up on developer jargon, feature creep is when you keep adding more and more functionality well after the core software is done; it is the tipping point between adding value and adding unnecessary complexity to your software. The best example of feature creep is Samsung, but we tend to assume Apple will have more restraint than that. 

Instead, the Apple Watch appears to be trying to do more than is necessary for some reason. The addition of Apple Pay to the iWatch is an example of feature creep where it doesn't feel like Apple thought it out completely. Sure, using your watch to make a payment leads to nice marketing imagery, and it would likely work easily in real life, but it could easily end up posing security risks. Remember, there is no TouchID scanner on the Apple Watch, but you will still need to authenticate any payment that is done with the watch. You might think this means that after you tap your Apple Watch for an NFC payment, you'll need to pull out your iPhone and authenticate that payment with your fingerprint. But, in actuality, there is no authentication for an Apple Watch payment. All you do is double tap the button next to the crown on the Watch and that's it. That seems quite easy, and it is unlikely that a thief would get both your iPhone and Watch, but it still feels too insecure.

The various methods of communication through the Apple Watch also seem a bit overdone. The walkie-talkie feature and the custom emoji could be nice, if they work well. But, the drawings seem like more of a gimmick, as does the sharing of heartbeats. Having options that work in loud environments is nice, but to an extent, it feels as if Apple doesn't trust Siri or the hardware to handle dictation well enough, and needs to have multiple backup options. However, as odd as the heartbeat sharing might be, it does lead into the truly special ideas that Apple has brought to the table.

The Apple Watch's killer functionality and feature

Taptic Engine

As strange and potentially unnecessary as the heartbeat sharing feature might be, it is directly tied to the one and only killer piece of functionality that Apple showed off with its Watch - the Taptic Engine. In simple terms, the Taptic Engine is an advanced haptic feedback device that can generate "a tactile sensation that’s recognizably different for each kind of interaction." In practice, this means that you won't feel different vibration patterns on your wrist, but different "tapping" sensations. 

This is the one and only feature of the Apple Watch that made me, as an Android user, stop and say, "Damn. I wish Android Wear had that." The automatic parsing of messages to give preset responses was cool, but the Taptic Engine is what I really want to see make its way to all wearables. Of course, Apple is likely very confident in the patents it holds on this technology, since it has announced it about 4 to 6 months before the Apple Watch makes it to consumers.  

As you can tell by the basic description I gave, the Taptic Engine isn't really a new idea, rather it is an old idea that has been upgraded and finally placed in the perfect scenario. Custom vibration patterns have been around since before we had proper smartphones, but they never quite worked to their fullest potential. Many people keep phones in bags, and even if it is in your pocket, you may not feel the subtleties of the vibration if you are standing or walking. However, the idea finds its perfect home in wearables, because there is suddenly a guarantee that you'll feel what you need to feel. 

And, the potential uses of this feature are amazing, because it finally allows for ways to notify the user without requiring the user to look at the screen of the device. Vibration patterns and sounds can help you know what type of notification is coming through, but now there are ways to convey meaning and content without visual cues. The two major examples Apple gave were in sending custom tap patterns to friends, which could be as simple as "tap once for yes or twice for no", or it could be a more complex and private message that only you understand. The other use case Apple gave was navigation, where you would be able to tell by feel if you need to turn right or left without needing to look at a device. That could have far-reaching effects. 

Watch bands everywhere

The other feature that Apple got completely right was the easily swappable watch bands. This is one of those few things that any company could do, but it makes perfect sense that Apple would be the one to do it right. It is also most likely the reason why Jony Ive said that traditional watch makers should be scared by what will be coming with the Apple Watch. 

Let's face it, the Apple Watch is an okay-looking device, but it isn't as traditionally beautiful as you might have expected from Apple. It is bulbous, the digital crown doesn't quite make sense, and after having seen what round smartwatches can look like with the Moto 360 and the LG G Watch R, a square watch from Apple is a bit of a disappointment. 

All that said, Apple knows its market and it knows that it had to offer an easy way to customize and personalize the hardware, which is where the swappable bands comes in. The basic idea is to recreate the phenomenon of iPhone cases with the iWatch. iPhone cases are by far the most varied of any smartphone around, because makers know that whatever they create won't be a one-and-done proposition. The iPhone only substantially changes design every other year, which has helped to create a vibrant case market. And, people obviously want to make their iPhones look different from others, which helps push that same market. 

The Apple Watch can't have a case, but it can have watch bands; so, Apple did the best thing it could and created a proprietary (and very simple) way to change the watch band. As The Verge's Nilay Patel said during the Apple Watch announcement, "The new strap attachment mechanism thing is like, you had HUNDREDS OF YEARS TO FIGURE IT OUT BEFORE APPLE SHOWED UP, WATCH INDUSTRY." But, in some special occasions, that's what Apple does - it finds those one or two things that others could have and should have been fixed before, does it, and leaves us all to wonder how it hadn't been done already. 

Apple has learned over the years that consistency is key, and this standardized watch band clasp will likely be part of any Apple Watch design for the foreseeable future. That kind of consistency builds a large third-part accessory market; and, a large accessory market like that has an odd way of legitimizing a product in the eyes of a consumer. If you saw a Moto 360 sitting next to an Apple Watch on a store shelf, you may prefer the 360, but seeing dozens of watch band options for the Apple Watch can suddenly shift your perspective. 


Even if you're an Apple fan, it's hard to recommend buying the Apple Watch when it finally arrives next year, because it is hard to recommend first generation hardware. Unfortunately, if you're an Android fan, the announcement of the Apple Watch also serves to highlight that Android Wear is still very much a first generation platform. There is a lot of room for Android Wear to grow, just as there will be a lot of room for the Apple Watch to find its path. 

I am a habitual early adopter, but the only Android Wear hardware that really impressed me has been soured by ancient internals. The Apple Watch didn't really impress me overall, but it is clear that Apple has some good ideas, and some that I would have expected from Google. It still amazes me that it was Apple who first announced the idea to parse incoming messages to offer relevant quick reply options. That seems like such a Googley feature. 

Either way, Apple has certainly done its job on me, and made me question whether it is worth investing in Android Wear just yet. Apple hasn't succeeded in taking away a sale from an Android maker, just delaying the action for a while. But, if enough users feel the same way that I do, it could easily cut into the head start that Android Wear has in the wearable market. Maybe that alone will be enough, but we'll have to wait and see. 



1. DogeShibe

Posts: 1121; Member since: Jan 10, 2014

"Meanwhile, in mid-2015, a Google Glass wearer and an Apple Watch wearer are arguing in a bar over who looks like a huger idiot" - Rob DenBleyker.

23. sgodsell

Posts: 7605; Member since: Mar 16, 2013

I don't see what Glass has to do with watches. But if you want to compare Android Wear to an Apple Watch then sure. I really like Apples swappable bands. However Apples band are proprietary compared to all the existing watch bands that are currently out their in the market. So Android wear devices like the LG G watch, Gear Live, Sony SmartWatch, Asus Zen Watch, as well as others can use existing watch bands made for regular watches. I also like the Haptic feed back. Android Wears interface is a simple interface, but does allow you to add launchers. Apples interface is yet to be proven with that crown wheel. In the end things are going to improve with both. There are a few things that are certain. Android Wear is KitKat 4.4W. The only difference is the UI, no keyboard input, and a tiny display. But Android Wear can use existing Android code. Also Android Wear allows existing Android phone and tablet apps to add Android Wear watch functionality without the need to actually create an Android Wear app for the watch. Only Android Wear has this type of support and functionality.

35. steedsofwar unregistered

Some EXCELLENT observations by the author. Some terrible ones too. Android wear hardware and software is night and day better than Apples. This is Apple's penchant and they ifailed in epic proportions. Apple watch OS looks like Android Gingerbread from so many years ago. I'm not convinced about Apple pay on a watch, even without authentication is a good idea. It means getting closer to the terminal and doing awkward motions to pay. Full apps and long interaction on a tiny display is a major turn off for me. It's counter intuitive. Tap and tap harder? Seriously? SMH.

2. galanoth

Posts: 428; Member since: Nov 26, 2011

Late 2015 smartwaches should be awesome. More mature hardware. More mature Android wear platform. 20nm SOC for efficiency. 48 hours straight use is what I'm hoping for by next year.

3. DogeShibe

Posts: 1121; Member since: Jan 10, 2014

I don't find then much useful. I already spend so much time on "smart phones" that are making me socially dumb. But hey ...

4. InspectorGadget80 unregistered

Another iBias reviewer. Just because Apple have wireless payments on their watch that makes Moto 360 bad looking and the iWatch better? I think these iguys are in over their head and they need too look at the design aspects. Moto 360 looks like and feels like a acutal watch while they drool over the BRICK HEAVY iWatch that requires a cord instead of wireless charging. And Apple won't say what's the battery life on the watch. As for me I'll wait till next summer buying the 360 sequel

13. KillgoreTroutTime

Posts: 433; Member since: Jan 06, 2014

All you have to say is that you didn't read the article...

25. sgodsell

Posts: 7605; Member since: Mar 16, 2013

Everyone is talking like the Apple Watch is like this and that. However no one has tried it out. No one knows what the iWatch OS is truly like. What does the SDK look like? Is it iOS compatible? What's the battery life like? At least with Android wear its here today and no need to wait until 2015. Also if you have an Android device then you will not care about the iwatch because it will only work with iPhones. Whereas Android Wear works with Android devices.

41. InspectorGadget80 unregistered

Exactly they never talk bout the Iwatch battery life. Sites like Iengadget talks trash bout the 360 battery life but never give it ONE SINGLE PRO.

40. InspectorGadget80 unregistered

No just saying that everyone talks down On the Moto 360 and won't admit it's a better watch than the Iwatch. And every blog site just BIAS.

16. Finalflash

Posts: 4063; Member since: Jul 23, 2013

I think it was a pretty well written article highlighting ups and downs in both platforms. Google seems to have the right approach from the start this time as in providing a watch with smart features, not a phone on your wrist. Apple has decided to go with a solution with more depth but it literally is the wrong platform for the wrong device. A watch is a fashion item first and foremost. Having someone look at it for an hour not only diminishes that appeal for the user but for others seeing that interaction as well. You have tiny images on a tiny screen being zoomed in and out and scrolled left and right providing information not at a glance but inside apps and menus (multiple layers). That is by far the most irritating and unappealing design decision they could have made. So in this category it seems Google took the more Apple approach with a design more fit for the medium and Apple seems to have taken the Google approach from 2009 where it has depth but looks and feels terrible.

17. alltechinside

Posts: 248; Member since: Apr 21, 2013

This is what he said regarding payments: "Instead, the Apple Watch appears to be trying to do more than is necessary for some reason.......Sure, using your watch to make a payment leads to nice marketing imagery, but it simply doesn't make sense in practical use. Remember, there is no TouchID scanner on the Apple Watch, but you will still need to authenticate any payment that is done with the watch. This means that after you tap your Apple Watch for an NFC payment, you'll likely still need to pull out your iPhone and authenticate that payment with your fingerprint. If that's the case, it seems easier to just use your iPhone for the whole transaction, and leave NFC out of the iWatch." IDK what you read?

5. bigmaster

Posts: 198; Member since: Sep 05, 2014

Like I just said in a previous article we should wait till 2015 or the next major update of Android wear to see how really useful these smartwatches are ! And the 2nd gen of the moto 360,LG g r,Asus Zen watch and so on

6. amiaq

Posts: 509; Member since: Jun 30, 2012

Apart from licking to the apple core type of article. Yes the "time wear" is not there yet.

7. madmikepr

Posts: 138; Member since: Aug 09, 2011

I just don't get the zoom in , in the iwatch is awkward if you have it on the right hand think about it ... And trying to se you pictures on a watch is ridiculous. Please let's be real if they but a Samsung logo on the Iwatch people will still laughing for this ridiculous features...

10. DogeShibe

Posts: 1121; Member since: Jan 10, 2014

I get it...the English is ridiculous but I get it.

32. madmikepr

Posts: 138; Member since: Aug 09, 2011

Auto correct Lol

37. o0Exia0o

Posts: 903; Member since: Feb 01, 2013

What if, and this is just an assumption on my part, Apple has already come to realize that it might be a problem with the design and implemented a solution such as the watch face can be flipped upside down in the settings to accommodate those that would like to wear the watch on their left hand? Being as the watch has not be released yet it may be a bit presumptuous to start bashing it on something that we don’t know about yet. Lets just wait and see what comes along when the watch hits the market.

8. 0xFFFF

Posts: 3806; Member since: Apr 16, 2014

Apple and Google are both giant companies who are mostly disconnected from the needs of real people. These massive corporations focus on delivering profits. So we get old parts (iPhone 6, Moto 360) at high prices. We get tons of expensive watch bands (iWatch) for a smartwatch that has very short battery life and offers only minimal water resistance. Both smartwatch platforms require a lot of management by the user. Ultimately, they end up as "watches" that are not about telling time, but wasting time.

9. fzacek

Posts: 2486; Member since: Jan 26, 2014

I just don't feel the need for a smartwatch. Is taking your phone out of your pocket and checking the notifications really so much work?...

11. GoBears

Posts: 456; Member since: Apr 27, 2012

When you're doing active things like snowboarding, mountain biking and others...yes it is.

18. fzacek

Posts: 2486; Member since: Jan 26, 2014

I guess you have a point, but why not just check your notifications when you're done with the activity?...

19. GoBears

Posts: 456; Member since: Apr 27, 2012

Well in my case I have a 6yr old. So I don't like to be off the grid too long. For me a smartwatch is pretty handy at times. Although my next one will work with all androids instead of just Samsungs.

21. fzacek

Posts: 2486; Member since: Jan 26, 2014

Got it...

20. alltechinside

Posts: 248; Member since: Apr 21, 2013

give it time, people have said the thing about smartphones, like: "whats the point of having a web browser on a phone if it can't use flash" "What is there a need for a camera when I could just use a pocket camera that I bring with me" Likewise, people have said negative things when the first iPad (aka tablet) was released (me included)... "It's a big iPod touch" "Laptop does more, don't get a tablet" "No Flash!!!" List goes on.... I agree with you though, currently smartwatches don't have the appeal to me but they could have a very useful feature in the future which gives a better user experience on a watch than a phone. What is it though? well idk....yet

34. ManusImperceptus

Posts: 724; Member since: Jun 10, 2014

A few comments... Smartphone camera vs. pocket camera: Following this argument would mean being able to ditch the smartphone completely in favour of the smartwatch. The iPad is a big toy; colleagues constantly not being able to see all content on excel sheets is a fine example. Them taking twice the time to write an email is another. People in general settling for previous decade quality gaming is a third... I'll reserve judgment until I see whether smartwatches can truly carve out their own rightful niche; they're not there yet.

12. Augustine

Posts: 1043; Member since: Sep 28, 2013

I just can't get past the looks of a plastic, non-functional watch that came with a couple of bubble gums... Some say that the iWatch looks like an iPod Nano with straps, but that to me is being too generous towards it. If I were to choose a smartwatch, which I feel no inclination to buy whatsoever, I'd take the Moto 360 instead, seemingly a product for adults.

14. JakeLee

Posts: 1021; Member since: Nov 02, 2013

It takes some civil courage to speak just a little bit against Android nowdays. Androtakus everywhere....

15. DogeShibe

Posts: 1121; Member since: Jan 10, 2014

If the site in question is filled with JakeLees then yeah

27. iushnt

Posts: 3160; Member since: Feb 06, 2013

its sad how you are trying to popularize the name for android users as "Androtakus" but no one is actually interested in you..May be you can go to other websites, let's say Nikon and Canon and defend your American company and bash Nikon!! or vice-versa or what ever you want.. You don't give any valuable input to this site..try somewhere else

Latest Stories

This copy is for your personal, non-commercial use only. You can order presentation-ready copies for distribution to your colleagues, clients or customers at or use the Reprints & Permissions tool that appears at the bottom of each web page. Visit for samples and additional information.
FCC OKs Cingular's purchase of AT&T Wireless