InformationWeek: The Business Value of Technology

InformationWeek: The Business Value of Technology
e2 Conference & Expo - Boston 2013
= Member Content
Facebook Twitter Share

E-mail | Print | Permalink | LinkedIn | RSS

Apple iWatch: 7 Reasons It Won't Fly


Squeezing a processor into an iPod Nano form factor mostly means a less-capable computing device, and adding a wristband doesn't change that.




Apple is reportedly experimenting with wristwatches made of curved glass, a project that could add another profitable product to the company's iOS arsenal.

Writing for the New York Times, Nick Bilton cited people familiar with Apple's tests and reported other signs of Apple's interest in wearable devices.

Apple is not the only company exploring this area, as can be seen by the departure of Richard DeVaul, one of its high-profile wearable computing hires from 2010 who left Apple to join Google in 2011. Google is expected to soon release a developer prototype of its Project Glass eyeglasses and the wearable era will face its first mass-market reality check.

Understandable as it may be that the tech industry would like to see wearable devices follow the same explosive growth trajectory as the mobile market experienced over the last six years, Apple, Google and other companies in this space have yet to demonstrate there's any mass-market value to buckling, strapping, mounting or otherwise attaching small, Internet-aware computers to one's body.

There is certainly niche-market value: The Nike + iPod sensor, the Nike Fuelband and other activity-tracking gadgets like the Jawbone UP wristband are loved by some. But these specialized gizmos will never have the broad impact of the iPhone.

The reason is simple: Having an Internet-connected computer with audio and video capabilities in your pocket turns out to be transformative. Having a strap to attach a less-capable Internet-connected computer to one's wrist is something less than that.

[ Want another opinion? Read Why Apple iOS-Driven Smartwatch Makes Sense. ]

The problem with wearable computing is that "wearable" barely matters as a modifier of "computing." Squeezing a processor into an iPod Nano form factor mostly means a less-capable computing device, and adding a wristband doesn't change that.

It may not always be so, once processor power consumption drops and energy generation through skin contact, radiant light, nano-chemistry and motion rises to the point that devices regenerate power at the rate they use it. But by then "wearable" will be far less interesting than "implanted" as far as computing goes.

"Wearable" matters more at the moment for Google's Project Glass, because the form of the device is critical to its function. "Wearable" for a timepiece is largely a matter of convenience and preference. Millions of people already have a Pocket iWatch, otherwise known as an iPhone. The wrist-mountable equivalent of the (as-yet) nonexistent iPhone Nano won't really being anything new to the table.

Watches and glasses are different from computers in that they're sold as fashion accessories and status symbols. The form matters more than the commodity function, telling time. Why else would anyone pay hundreds, thousands or tens of thousands of dollars for a luxury watch?

Former Apple designer Bruce Tognazzini has penned an essay on the merits of an Apple iWatch. But I find it unconvincing. The two "killer applications" he cites, passcode management and iDevice location, are nothing of the sort. Rather than relying on the iWatch to eliminate iPhone passcode entry, the iPhone would be better off with biometric access support. And finding one's iPhone can already be done well enough through iCloud.

Federal agencies must eliminate 800 data centers over the next five years. Find how they plan to do it in the new all-digital issue of InformationWeek Government. Download it now (registration required).


 1 | 2  | Next Page » 




InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
Subscribe to RSS


Advertisement


InformationWeek Reports

report Cloud Implementer's Checklist
Once your agency has completed the business case for a private cloud, how do you actually move ahead with your data center transformation? Our report provides a practical set of steps to get you there, including a "to do" list that will be helpful to anyone on your IT team who's involved in the project. By the time you're done, your data center should be home to a more flexible, on-demand IT services.

report Cloud Compliance in Government
Compute clouds created for government data centers must adhere to a range of specifications designed to support data and system security, privacy, and governance. FISMA, HIPAA, SOX, and SAS 70 are just some of the requirements that have to be taken into account as federal IT pros deploy a shared-services cloud model. In this report, we identify the key specs that need to be factored into any federal cloud architecture.

report Government Cloud Platform Strategy
This report analyzes the key IT infrastructure considerations that must be taken into account for implementing cloud services in federal data centers: software/hardware environment, multi-tenancy, security, virtualization, and management tools. We also explain the key important role that APIs play in supporting hybrid scenarios that tap into public cloud services.

report The Business Case for Government Clouds
This report assesses usage scenarios, barriers, and other variables that factor into the decision of whether and how to implement cloud computing in federal environments.