<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: The HumanCentric mobile phone</title>
	<atom:link href="http://blog.humancentric.com/the-humancentric-mobile-phone/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.humancentric.com/the-humancentric-mobile-phone/</link>
	<description>We believe that great experiences come from understanding people.</description>
	<lastBuildDate>Sun, 01 Aug 2010 10:36:46 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Brian Chiarizia</title>
		<link>http://blog.humancentric.com/the-humancentric-mobile-phone/comment-page-1/#comment-1581</link>
		<dc:creator>Brian Chiarizia</dc:creator>
		<pubDate>Wed, 06 Jan 2010 15:01:40 +0000</pubDate>
		<guid isPermaLink="false">http://blog.humancentric.com/?p=128#comment-1581</guid>
		<description>@loki

The main purpose for designing this phone was not for the actual physical design of the hardware. It was created in order to give our Interaction &amp; Graphic Designers a phone that we could use to showcase our Interaction Design work to potential clients without having to use someone else&#039;s design.

We wanted to create a fairly simple and clean look that would not distract from the actual work that we would be presenting on screen. There are several traditional hard buttons that were incorporated into the design so that the user has the ability to control certain things on screen. 

Hope this helps clarify the original intent of the design.</description>
		<content:encoded><![CDATA[<p>@loki</p>
<p>The main purpose for designing this phone was not for the actual physical design of the hardware. It was created in order to give our Interaction &amp; Graphic Designers a phone that we could use to showcase our Interaction Design work to potential clients without having to use someone else&#8217;s design.</p>
<p>We wanted to create a fairly simple and clean look that would not distract from the actual work that we would be presenting on screen. There are several traditional hard buttons that were incorporated into the design so that the user has the ability to control certain things on screen. </p>
<p>Hope this helps clarify the original intent of the design.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Wirtanen</title>
		<link>http://blog.humancentric.com/the-humancentric-mobile-phone/comment-page-1/#comment-1449</link>
		<dc:creator>Andrew Wirtanen</dc:creator>
		<pubDate>Wed, 30 Dec 2009 14:08:43 +0000</pubDate>
		<guid isPermaLink="false">http://blog.humancentric.com/?p=128#comment-1449</guid>
		<description>@loki

This was a competition by our industrial designers. It was not analyzed by myself or the human factors team, and the UI was never developed. As a company, we voted on several designs.

The two unmarked buttons serve as softkeys, which are traditionally used in mobile phone software. The idea here, I believe, is that the phone does not have to be a touch screen. I&#039;ll ask the designers to comment further.</description>
		<content:encoded><![CDATA[<p>@loki</p>
<p>This was a competition by our industrial designers. It was not analyzed by myself or the human factors team, and the UI was never developed. As a company, we voted on several designs.</p>
<p>The two unmarked buttons serve as softkeys, which are traditionally used in mobile phone software. The idea here, I believe, is that the phone does not have to be a touch screen. I&#8217;ll ask the designers to comment further.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: loki</title>
		<link>http://blog.humancentric.com/the-humancentric-mobile-phone/comment-page-1/#comment-1438</link>
		<dc:creator>loki</dc:creator>
		<pubDate>Tue, 29 Dec 2009 19:31:37 +0000</pubDate>
		<guid isPermaLink="false">http://blog.humancentric.com/?p=128#comment-1438</guid>
		<description>That phone doesn&#039;t seem particularly user centric, even accounting for the fact that it is hard to tell from the single picture, no follow up links, and no shots of the UI.

I would like to hear why they chose an iPhone clone design with two unmarked butons and two completely similar buttons as the hardware interface.

More informative posts please!</description>
		<content:encoded><![CDATA[<p>That phone doesn&#8217;t seem particularly user centric, even accounting for the fact that it is hard to tell from the single picture, no follow up links, and no shots of the UI.</p>
<p>I would like to hear why they chose an iPhone clone design with two unmarked butons and two completely similar buttons as the hardware interface.</p>
<p>More informative posts please!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: HF Potpourri — the Human Factors Blog</title>
		<link>http://blog.humancentric.com/the-humancentric-mobile-phone/comment-page-1/#comment-1158</link>
		<dc:creator>HF Potpourri — the Human Factors Blog</dc:creator>
		<pubDate>Mon, 14 Dec 2009 13:05:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.humancentric.com/?p=128#comment-1158</guid>
		<description>[...] HF usability company HumanCentral held an internal competition to design an handset.  I&#8217;d love more information on the [...]</description>
		<content:encoded><![CDATA[<p>[...] HF usability company HumanCentral held an internal competition to design an handset.  I&#8217;d love more information on the [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
