<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Designing Devices &#187; Form</title>
	<atom:link href="http://www.designingdevices.com/category/form/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.designingdevices.com</link>
	<description>Articles on Device Design</description>
	<lastBuildDate>Tue, 10 Jan 2012 17:00:26 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
		<item>
		<title>A Case for Single-Purpose Devices</title>
		<link>http://www.designingdevices.com/a-case-for-single-purpose-devices/</link>
		<comments>http://www.designingdevices.com/a-case-for-single-purpose-devices/#comments</comments>
		<pubDate>Wed, 20 Apr 2011 20:02:56 +0000</pubDate>
		<dc:creator>Dan</dc:creator>
				<category><![CDATA[Form]]></category>
		<category><![CDATA[Functionality]]></category>
		<category><![CDATA[Strategy]]></category>

		<guid isPermaLink="false">http://www.designingdevices.com/a-case-for-single-purpose-devices/</guid>
		<description><![CDATA[I believe there is still a place for single-function devices, under specific circumstances.]]></description>
			<content:encoded><![CDATA[<p>Two truisms seem to be happening right now with technology:
<ol>
<li><strong>Every activity that can be made digital will be.</strong> I don&#8217;t have to physically adjust my thermostat, it&#8217;s controlled by a computer.</p>
<li><strong>Every activity that can be made digital will be put on a multi-purpose (or &#8220;convergent&#8221;) device as an app.</strong> I don&#8217;t need an alarm clock, I&#8217;ve got an alarm on my mobile phone. This phenomenon is starting to be labeled <a href="http://en.wikipedia.org/wiki/Ephemeralization">&#8220;ephemeralization.&#8221;</a></ol>
<p>Where then does this leave single-purpose, single-function devices? Are they to vanish into history? Some certainly will. For example, cameras, MP3 players, and video cameras are taking a beating from mobile phones. But I believe there is still a place for single-function devices, under specific circumstances.</p>
<p>A single-function device (an &#8220;appliance&#8221; as <a href="http://orangecone.com/archives/2010/08/information_is_.html">Mike Kuniavsky calls them</a>, vs. a multi-function &#8220;terminal&#8221;) makes sense when:
<ul>
<li><strong>It can do more/is more powerful than similar functionality in a terminal.</strong> You won&#8217;t find professional photographers using Android phones to take wedding pictures, for instance. The power and control of an object designed to just be a camera outweighs any inconvenience of carrying around a specialty object to take pictures.
<li><strong>The physical activity the appliance engenders cannot be replicated digitally.</strong> In other words, an iPad isn&#8217;t going to substitute for your dishwasher.
<li><strong>The integration of hardware and software is key.</strong> A variation on not being able to be replicated digitally, some activities are simply easier when there are physical controls. It is still easier to type on a physical keyboard than it is on a touchscreen one.
<li><strong>It is prohibitively expensive or dangerous to make the activity digital.</strong> In theory, I could make an iPhone app to drive my car, but I think government agencies might have something to say about that.
<li><strong>There are a few billion people out there without a smartphone, tablet, or laptop.</strong> If your target base isn&#8217;t likely to have an expensive terminal device, an app on one isn&#8217;t going to work for them.
<li><strong>The device has to be stationary.</strong> Some devices have to be hooked into the systems of a location (plumbing, electricity, gas, water, etc.) to work. Likewise, some sensor-driven devices only work (or only work well) if they are calibrated for a certain space. For instance, Microsoft Kinect.
<li><strong>The form factor of any terminal device doesn&#8217;t match the activity.</strong> My $500 non-waterproof iPad isn&#8217;t the object I want to take on a scuba-diving trip.
</ul>
<p>Now I grant you some of these items are conditional—perhaps in the future the cameras in multi-use devices will be as good as professional ones. Even so, I feel there is always going to be a place for beautiful objects that one do one thing—but only if the integration of hardware and software is such that it makes accomplishing the task so much easier/more efficient/more fun than a multipurpose device would. That&#8217;s the challenge: how to <a href="http://www.designingdevices.com/device-differentiators/">differentiate</a> your single-purpose device so that consumers will buy it instead of (or in addition to) an app that does the same thing. Designers have to not only explain why you&#8217;d want to own the chef&#8217;s knife instead of a Swiss Army knife, but also make the specialty item worth owning. That&#8217;s the challenge.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.designingdevices.com/a-case-for-single-purpose-devices/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A Taxonomy of Device Forms</title>
		<link>http://www.designingdevices.com/a-taxonomy-of-device-forms/</link>
		<comments>http://www.designingdevices.com/a-taxonomy-of-device-forms/#comments</comments>
		<pubDate>Fri, 01 Jan 2010 19:04:25 +0000</pubDate>
		<dc:creator>Dan</dc:creator>
				<category><![CDATA[Form]]></category>

		<guid isPermaLink="false">http://www.designingdevices.com/a-taxonomy-of-device-forms/</guid>
		<description><![CDATA[It helps to consider these device categories, because each brings with it different expectations as to how to engage with the device and what kinds of functionality might be available, not to mention qualities such as durability and cost. Device designers need to be aware of this when considering what form a device should take.]]></description>
			<content:encoded><![CDATA[<p>In Marc Weiser&#8217;s seminal 1991 essay <a href="http://www.ubiq.com/hypertext/weiser/SciAmDraft3.html">The Computer for the 21st Century</a>, he defines three general forms for devices in the 21st century:
<ul>
<li><b>Tabs:</b> “inch-scale machines that approximate active Post-It notes” Mobile phones, and devices such as mobile cameras and MP3 players fall into this category, although most of these are larger than Weiser likely envisioned. Very few devices currently are as small and light as a pad of post-it notes. Digital watches and some medical devices, perhaps.
<li><b>Pads:</b> “foot-scale [devices] that behave something like a sheet of paper (or a book or a magazine)” Laptops, tablet PCs, and e-readers are examples of this category.
<li>and <b>Boards</b>: “yard-scale displays that are the equivalent of a blackboard or bulletin board” We&#8217;re making progress on this front, with large touchscreen walls, not to mention our flat screen TVs.</ul>
<p>Clearly, Weiser was thinking mostly of an office/workplace environment with his categorization scheme. If we expand our view out a little more to include homes and public spaces, I think there are some other general types that could be included in Weiser&#8217;s categories:
<ul>
<li><b>Dots:</b> tiny, nearly- or completely-invisible devices.
<li><b>Boxes:</b> devices that are slightly too large, bulky or heavy to be portable. Kitchen appliances such as toasters and many consumer electronics like stereo equipment fall into this category.
<li><b>Chests:</b> large, heavy devices that do not move, such as dishwashers, stoves, and refrigerators.
<li><b> Vehicles:</b> large, heavy devices that do move. Yes, cars are devices too, writ large.
</ul>
<p>It helps to consider these categories, because each brings with it different expectations as to how to engage with the device and what kinds of functionality might be available, not to mention qualities such as durability and cost. Device designers need to be aware of this when considering what form a device should take.</p>
<p>Of course, traditionally, this is has likely been determined before the designer even starts the project: &#8220;We need a new line of washing machines. Go make us some.&#8221; But in the 21st century, it&#8217;s not quite as simple. Frequently now, the starting point is <b>not</b> the form, but instead the functionality, with the form enabling and enhancing that. As electronics and computer components get smaller, it&#8217;s easier for what might have been a Box at one point to become a Pad, Tab, or even a Dot and &#8220;disappear&#8221; all together. There&#8217;s more computing power in a digital watch these days than in the NASA capsules that went to the moon. Functionality, and thus form, is more fluid and cross-category.</p>
<p>Of course, a Vehicle is not likely to become a Dot, but the functionality such as a navigation system that might have previously been stored in a car (in the dashboard, say), might now be in the Tab that is your mobile phone.</p>
<p>There is also an emotional response around different forms. We have a different relationship to our mobile phones than we do to our stoves, or to our cars as to our laptops. Some of this is certainly about price point (our cars cost more than our mobile phones), but some is the pure physicality of the object itself. A large, heavy, immobile object usually has more emotional weight than a small, mobile one. If just for the fact that it has a larger spatial (and fixed) presence in a room. You would immediately notice if it was gone. This is a tricky problem as more objects dematerialize and become Dots. Will you feel differently about your TiVo/DVR if there was no Box and no remote (only gestures for control)? </p>
]]></content:encoded>
			<wfw:commentRss>http://www.designingdevices.com/a-taxonomy-of-device-forms/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->
