This post originated from an RSS feed registered with .NET Buzz
by Scott Hanselman.
Original Post: Microsoft "MSN Direct" and Wrist.NET applied to "Wearables"
Feed Title: Scott Hanselman's ComputerZen.com
Feed URL: http://radio-weblogs.com/0106747/rss.xml
Feed Description: Scott Hanselman's ComputerZen.com is a .NET/WebServices/XML Weblog. I offer details of obscurities (internals of ASP.NET, WebServices, XML, etc) and best practices from real world scenarios.
One of the reasons
I want Wrist.NET to succeed is my belief that the only jewelry (stuff you wear all
the time) that will be worn all the time in my lifetime is watches, rings and to some
degree, necklaces. Perhaps will see some displays in glasses but that's
10 years+ out and iffy at best. A watch is a perfect size to provide me with
more than just the time, and I don't carry my phone with me everywhere.
However, a comment in my last post about the watch said that it was too much of a
'gadget' and possibly too large. He said:
"That's why I'm more interested in the smartphones or maybe even some wearables."
I'm not sure about this whole vagueness of wearables. I'm not sure there's as
much of a market for a "Flava Flav" style SPOT device, do you?
Previous Topic
One of the reasons
I want Wrist.NET to succeed is my belief that the only jewelry (stuff you wear all
the time) that will be worn all the time in my lifetime is watches, rings and to some
degree, necklaces. Perhaps will see some displays in glasses but that's
10 years+ out and iffy at best. A watch is a perfect size to provide me with
more than just the time, and I don't carry my phone with me everywhere.