<?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 Interface of a Cheeseburger</title>
	<atom:link href="http://www.informationarchitects.jp/en/the-interface-of-a-cheeseburger/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.informationarchitects.jp/en/the-interface-of-a-cheeseburger/</link>
	<description>We architect information.</description>
	<lastBuildDate>Fri, 03 Feb 2012 21:41:04 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Dlaczego Windows jest lepszy niz OSX &#171; dc1 &#34;blog&#34;</title>
		<link>http://www.informationarchitects.jp/en/the-interface-of-a-cheeseburger/comment-page-3/#comment-155087</link>
		<dc:creator>Dlaczego Windows jest lepszy niz OSX &#171; dc1 &#34;blog&#34;</dc:creator>
		<pubDate>Sun, 06 Jun 2010 09:45:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.informationarchitects.jp/the-interface-of-a-cheeseburger#comment-155087</guid>
		<description>&lt;p&gt;[...] myslenia takze sklonila mnie postawa ludzi z 37signals oraz artykul &#8220;The interface of Cheesburger&#8221; ktore uswiadomily mi, ze Windows to jest wlasnie to, czego ludzie potrzebuja i co chetnie [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] myslenia takze sklonila mnie postawa ludzi z 37signals oraz artykul &#8220;The interface of Cheesburger&#8221; ktore uswiadomily mi, ze Windows to jest wlasnie to, czego ludzie potrzebuja i co chetnie [...]</p>]]></content:encoded>
	</item>
	<item>
		<title>By: nice article on informationarchitects &#124; ruben braun</title>
		<link>http://www.informationarchitects.jp/en/the-interface-of-a-cheeseburger/comment-page-3/#comment-154729</link>
		<dc:creator>nice article on informationarchitects &#124; ruben braun</dc:creator>
		<pubDate>Tue, 04 May 2010 08:29:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.informationarchitects.jp/the-interface-of-a-cheeseburger#comment-154729</guid>
		<description>&lt;p&gt;[...] older article about interface branding The cheeseburger as has the easiest food interface one could think of. No [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] older article about interface branding The cheeseburger as has the easiest food interface one could think of. No [...]</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Anton</title>
		<link>http://www.informationarchitects.jp/en/the-interface-of-a-cheeseburger/comment-page-3/#comment-153131</link>
		<dc:creator>Anton</dc:creator>
		<pubDate>Wed, 08 Jul 2009 10:21:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.informationarchitects.jp/the-interface-of-a-cheeseburger#comment-153131</guid>
		<description>&lt;p&gt;I am glad I stumbled across this, interface = brand is a strong idea. May not always be correct, but still worth dwelling upon, in any product design, on or offline. Thank you.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I am glad I stumbled across this, interface = brand is a strong idea. May not always be correct, but still worth dwelling upon, in any product design, on or offline. Thank you.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: jordan</title>
		<link>http://www.informationarchitects.jp/en/the-interface-of-a-cheeseburger/comment-page-3/#comment-153051</link>
		<dc:creator>jordan</dc:creator>
		<pubDate>Sat, 20 Jun 2009 07:03:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.informationarchitects.jp/the-interface-of-a-cheeseburger#comment-153051</guid>
		<description>&lt;p&gt;Couldn’t agree more. So I would describe the formula like this: Uniqueness + Interface = Brand Positioning + Touchpoints = Brand Unique benefit + Emotional experience = Brand Innovation + Personality = Brand&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Couldn’t agree more. So I would describe the formula like this: Uniqueness + Interface = Brand Positioning + Touchpoints = Brand Unique benefit + Emotional experience = Brand Innovation + Personality = Brand</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Lalao Rakotoniaina</title>
		<link>http://www.informationarchitects.jp/en/the-interface-of-a-cheeseburger/comment-page-3/#comment-152926</link>
		<dc:creator>Lalao Rakotoniaina</dc:creator>
		<pubDate>Tue, 12 May 2009 15:50:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.informationarchitects.jp/the-interface-of-a-cheeseburger#comment-152926</guid>
		<description>&lt;p&gt;Sorry, I&#039;m a bit late. It is indeed a great article. Interaction starts when someone needs to grab a hold of something may it be an idea or a product. When talking about interfaces (as they enable interaction), one actually talks about everyday things. Besides, your point about Nielsen&#039;s useit.com is absolutely true with regards to the &quot;contraction law&quot; of branding.  &lt;/p&gt;

&lt;p&gt;I cannot agree with you about Facebook&#039;s interface, though. To me it is another example of an early goer: the first big thing in the genre to hit the market and for free. Their early interface was unpredictible, features were arranged in an unintuitive manner, no hierarchy, no cue. People just had this incredible urge to get back in touch with their long-forgotten mates from kindergarden.&lt;/p&gt;

&lt;p&gt;For example: how predictive is it that when you&#039;re consulting someone&#039;s profile and then you click on the &quot;friends&quot; tab, you get back to your own list of friends? How usable is that? Navigation is consistent, all right! But I cannot use my knowledge of navigating my own content to the purpose of navigating someone else&#039;s. I cannot build my experience on my early learnings, I have to learn some other ways to do just the same thing: that IS unconsistency at work. &lt;/p&gt;

&lt;p&gt;I can go on and on on facebook, but that&#039;s neither the point, nor worth it.&lt;/p&gt;

&lt;p&gt;Anyway, informationarchitects.jp makes a great contribution to the design community and thanks for that.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Sorry, I&#8217;m a bit late. It is indeed a great article. Interaction starts when someone needs to grab a hold of something may it be an idea or a product. When talking about interfaces (as they enable interaction), one actually talks about everyday things. Besides, your point about Nielsen&#8217;s useit.com is absolutely true with regards to the &#8220;contraction law&#8221; of branding.  </p>

<p>I cannot agree with you about Facebook&#8217;s interface, though. To me it is another example of an early goer: the first big thing in the genre to hit the market and for free. Their early interface was unpredictible, features were arranged in an unintuitive manner, no hierarchy, no cue. People just had this incredible urge to get back in touch with their long-forgotten mates from kindergarden.</p>

<p>For example: how predictive is it that when you&#8217;re consulting someone&#8217;s profile and then you click on the &#8220;friends&#8221; tab, you get back to your own list of friends? How usable is that? Navigation is consistent, all right! But I cannot use my knowledge of navigating my own content to the purpose of navigating someone else&#8217;s. I cannot build my experience on my early learnings, I have to learn some other ways to do just the same thing: that IS unconsistency at work. </p>

<p>I can go on and on on facebook, but that&#8217;s neither the point, nor worth it.</p>

<p>Anyway, informationarchitects.jp makes a great contribution to the design community and thanks for that.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Pearl</title>
		<link>http://www.informationarchitects.jp/en/the-interface-of-a-cheeseburger/comment-page-3/#comment-152914</link>
		<dc:creator>Pearl</dc:creator>
		<pubDate>Thu, 07 May 2009 22:39:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.informationarchitects.jp/the-interface-of-a-cheeseburger#comment-152914</guid>
		<description>&lt;p&gt;Re: &quot;Sandwiches can be Complicated at Times
...The cheeseburger as has the easiest food interface one could think of. No forks, no knives, no spoons, no plates, no chopsticks.&quot; &lt;/p&gt;

&lt;p&gt;If you watch BK&#039;s Whopper Virgins documentary, the simplicity is also cultural. Quite a few didn&#039;t know how to eat it, or pick it up.&lt;/p&gt;

&lt;p&gt;Watching it made me think, these people aren&#039;t used to stuffing food in their mouths. And exporting the burger concept suddenly seems like such a barbaric act.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Re: &#8220;Sandwiches can be Complicated at Times
&#8230;The cheeseburger as has the easiest food interface one could think of. No forks, no knives, no spoons, no plates, no chopsticks.&#8221; </p>

<p>If you watch BK&#8217;s Whopper Virgins documentary, the simplicity is also cultural. Quite a few didn&#8217;t know how to eat it, or pick it up.</p>

<p>Watching it made me think, these people aren&#8217;t used to stuffing food in their mouths. And exporting the burger concept suddenly seems like such a barbaric act.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Martin K</title>
		<link>http://www.informationarchitects.jp/en/the-interface-of-a-cheeseburger/comment-page-3/#comment-152773</link>
		<dc:creator>Martin K</dc:creator>
		<pubDate>Tue, 14 Apr 2009 05:36:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.informationarchitects.jp/the-interface-of-a-cheeseburger#comment-152773</guid>
		<description>&lt;p&gt;@S: How can you deny that a nipple is a brand? It&#039;s instantly recognized, intensely sought after by half of the world population, and carries both a strong attraction and a high recognition value. Just because it is crowdsourced and not owned by a single corporation doesn&#039;t mean it&#039;s not a brand.&lt;/p&gt;

&lt;p&gt;And unrelated, a true Starbucks customer story:
Me: &quot;Cafe Latte please&quot;
Clerk: &lt;em&gt;confused&lt;/em&gt; &quot;A plain latte?&quot;&lt;/p&gt;

&lt;p&gt;To the clerk&#039;s defense, the store was in Christopher Street, NY.&lt;/p&gt;

&lt;p&gt;I&#039;ve also started to order my coffee &quot;medium&quot; size in Starbucks, most of the greenshirts can decode that.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>@S: How can you deny that a nipple is a brand? It&#8217;s instantly recognized, intensely sought after by half of the world population, and carries both a strong attraction and a high recognition value. Just because it is crowdsourced and not owned by a single corporation doesn&#8217;t mean it&#8217;s not a brand.</p>

<p>And unrelated, a true Starbucks customer story:
Me: &#8220;Cafe Latte please&#8221;
Clerk: <em>confused</em> &#8220;A plain latte?&#8221;</p>

<p>To the clerk&#8217;s defense, the store was in Christopher Street, NY.</p>

<p>I&#8217;ve also started to order my coffee &#8220;medium&#8221; size in Starbucks, most of the greenshirts can decode that.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: ugg</title>
		<link>http://www.informationarchitects.jp/en/the-interface-of-a-cheeseburger/comment-page-3/#comment-152454</link>
		<dc:creator>ugg</dc:creator>
		<pubDate>Wed, 18 Mar 2009 04:44:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.informationarchitects.jp/the-interface-of-a-cheeseburger#comment-152454</guid>
		<description>&lt;p&gt;Yes if you include ’service’ and ’support’ also to the interface then we are talking about the same thing. Although I am not sure that it is common to think of it that way. I haven’t seen many ‘interface designers’ that include it. But it is a theoretical discussion about what and what not to include in the definition of ‘interface’, we are saying the same thing.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Yes if you include ’service’ and ’support’ also to the interface then we are talking about the same thing. Although I am not sure that it is common to think of it that way. I haven’t seen many ‘interface designers’ that include it. But it is a theoretical discussion about what and what not to include in the definition of ‘interface’, we are saying the same thing.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: cheeseburger wins again! at most of you are average</title>
		<link>http://www.informationarchitects.jp/en/the-interface-of-a-cheeseburger/comment-page-3/#comment-152350</link>
		<dc:creator>cheeseburger wins again! at most of you are average</dc:creator>
		<pubDate>Tue, 24 Feb 2009 18:50:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.informationarchitects.jp/the-interface-of-a-cheeseburger#comment-152350</guid>
		<description>&lt;p&gt;[...] strong and how both are of equal value to the consumer/end user. Check out the full post here.      &#171; daniel [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] strong and how both are of equal value to the consumer/end user. Check out the full post here.      &laquo; daniel [...]</p>]]></content:encoded>
	</item>
	<item>
		<title>By: graphic design london</title>
		<link>http://www.informationarchitects.jp/en/the-interface-of-a-cheeseburger/comment-page-3/#comment-152289</link>
		<dc:creator>graphic design london</dc:creator>
		<pubDate>Wed, 04 Feb 2009 16:33:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.informationarchitects.jp/the-interface-of-a-cheeseburger#comment-152289</guid>
		<description>&lt;p&gt;Im looking into re-designing my site and making every site I make as easy to use as possible (despite my clients wanting to do the opposite most of the time). &lt;/p&gt;

&lt;p&gt;Your article really made me think about brands in a different way. &lt;/p&gt;

&lt;p&gt;Thanks.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Im looking into re-designing my site and making every site I make as easy to use as possible (despite my clients wanting to do the opposite most of the time). </p>

<p>Your article really made me think about brands in a different way. </p>

<p>Thanks.</p>]]></content:encoded>
	</item>
</channel>
</rss>

