<?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>Small Surfaces &#187; toyota</title>
	<atom:link href="http://smallsurfaces.com/tag/toyota/feed/" rel="self" type="application/rss+xml" />
	<link>http://smallsurfaces.com</link>
	<description>mobile user interface design / user experience design / interaction design resources</description>
	<lastBuildDate>Wed, 28 Jul 2010 10:10:34 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Overloading Car Dashboards</title>
		<link>http://smallsurfaces.com/2008/08/overloading-car-dashboards/</link>
		<comments>http://smallsurfaces.com/2008/08/overloading-car-dashboards/#comments</comments>
		<pubDate>Fri, 29 Aug 2008 19:42:40 +0000</pubDate>
		<dc:creator>Gabriel White</dc:creator>
				<category><![CDATA[mobile]]></category>
		<category><![CDATA[camry]]></category>
		<category><![CDATA[car]]></category>
		<category><![CDATA[music]]></category>
		<category><![CDATA[overloading]]></category>
		<category><![CDATA[touchscreen]]></category>
		<category><![CDATA[toyota]]></category>

		<guid isPermaLink="false">http://www.smallsurfaces.com/?p=559</guid>
		<description><![CDATA[&#8220;So what has probably happened here &#8211; Toyota had to create this one product that integrates the GPS, CD changer, the blue tooth telephone, the trip information and the other 15 things I have not discovered yet. It probably started as one component, which then had to be reworked to integrate the second component and [...]]]></description>
			<content:encoded><![CDATA[	<p>&#8220;So what has probably happened here &#8211; Toyota had to create this one product that integrates the GPS, CD changer, the blue tooth telephone, the trip information and the other 15 things I have not discovered yet. It probably started as one component, which then had to be reworked to integrate the second component and so on. When everything was said and done, we have what I get to use now. It sure does meet all product functionality requirements that it was set to achieve, but it falls well short of usability requriements &#8211; thanks to product integrations. Do your products suffer from this same problem?&#8221;</p>
	<p><strong>Link:</strong> <a href="http://productmanagementtips.com/2008/04/14/product-integration-usability-killer/">Product Integration &#8211; Usability killer?</a> (productmanagementtips.com, <a href="http://www.uselog.com/2008/08/product-integration-as-barrier-for.html">via</a>)</p>

 

<p><b>Related:</b></p>
<ul>
		<li><a href="http://smallsurfaces.com/2006/02/zen-of-palm/" rel="bookmark">Zen of Palm</a></li>
	</ul>
<p>Share on <a href="http://www.facebook.com/sharer.php?u=http://smallsurfaces.com/2008/08/overloading-car-dashboards/&t=Overloading Car Dashboards">Facebook</a> | Save to 
<a href="http://del.icio.us/post?url=http://smallsurfaces.com/2008/08/overloading-car-dashboards/&title=Overloading Car Dashboards">del.icio.us</a> | 
<a href="http://smallsurfaces.com">Small Surfaces</a> is published by <a href="http://www.gabrielwhite.com/">Gabriel White</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://smallsurfaces.com/2008/08/overloading-car-dashboards/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
