Return to the archive index

Re: wearables: interfaces, functions...

Carol Stein <> writes:
> >However, as a way of turning your comment completely on its head: if
> >what you're going to do is let someone run Microsoft Word, why bother?
> 
> I thought I explained that the reason to bother is to make wearables
> *affordable* for those of us who WOULD use the novel
> applications. How many aircraft documenters do you think there are
> in the world?

Documenters are few -- but people doing repairs are many. Mechanics
and many other professions have obvious applications for
wearables.

> It's true that wearables exist already, and have for some years now,
> for the niche markets (such as this, and surgeons working on a small
> scale, etc.). But to make wearables cheap (and ubiquitous), we need
> volume, and that entails making them as a replacement for today's
> general-purpose PC business & home user.

I am not very sure about that. First of all, the home and business
user won't want them instead of laptops unless there is a compelling
application that can't be done on the laptops. People don't move to
new technologies without strong incentives.

Second of all, there is nothing very novel in the technologies we're
talking about other than the heads up displays -- everything else is
fundamentally quite cheap to build even in modest quantities.

> But first -- I want my wearable! And I've already been waiting since
> June 1998 for it! I want it now!

Then build one. It won't take that much time or effort. It might be
cruder than what you wanted, but it certainly isn't *that* difficult...

-- 
Perry E. Metzger		

--
Subscription/unsubscription/info requests: send e-mail with subject of
"subscribe", "unsubscribe", or "info" to 
Wear-Hard Mailing List Archive (searchable): http://wearables.blu.org
Please, *PLEASE* don't subscribe through a forward/expander/false domain

From Wear-Hard Mailing list Archive (WH)
Maintained by R. Paul McCarty

Archive created with babymail