<?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"
	>
<channel>
	<title>Comments on: Yahoo! Go 2.0 shows how far mobile UI design has to go</title>
	<atom:link href="http://www.disambiguity.com/yahoo-go-20-shows-how-far-mobile-ui-design-has-to-go/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.disambiguity.com/yahoo-go-20-shows-how-far-mobile-ui-design-has-to-go/</link>
	<description>pretty design pending</description>
	<pubDate>Fri, 09 Jan 2009 15:08:54 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Olly Wright</title>
		<link>http://www.disambiguity.com/yahoo-go-20-shows-how-far-mobile-ui-design-has-to-go/#comment-8212</link>
		<dc:creator>Olly Wright</dc:creator>
		<pubDate>Tue, 09 Jan 2007 17:56:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.disambiguity.com/yahoo-go-20-shows-how-far-mobile-ui-design-has-to-go/#comment-8212</guid>
		<description>Sure. It's possible to get 'out onto the web' on almost any phone. But in practice most operators make this as hard as they can. It's certainly not something that the average user would want to do often. They also do stuff like provide no data charge for content from their services, whilst charging per byte for other sites accessed.

Their business plans in the near (and perhaps mid) term appear to depend on getting users to use their mobile internet services. It reminds me of AOL circa the mid 90s, as opposed to being a pure ISP.

I'm not trying to paint the operators in an especially bad light. I think the whole mobile industry has gotten itself into a situation where real standards are currently out of reach (the kind that will see orders of magnitude increase in mobile sites and mobile site access). To this end I do applaud Yahoo, it is a step (albeit a small one) in the right direction.</description>
		<content:encoded><![CDATA[<p>Sure. It&#8217;s possible to get &#8216;out onto the web&#8217; on almost any phone. But in practice most operators make this as hard as they can. It&#8217;s certainly not something that the average user would want to do often. They also do stuff like provide no data charge for content from their services, whilst charging per byte for other sites accessed.</p>
<p>Their business plans in the near (and perhaps mid) term appear to depend on getting users to use their mobile internet services. It reminds me of AOL circa the mid 90s, as opposed to being a pure ISP.</p>
<p>I&#8217;m not trying to paint the operators in an especially bad light. I think the whole mobile industry has gotten itself into a situation where real standards are currently out of reach (the kind that will see orders of magnitude increase in mobile sites and mobile site access). To this end I do applaud Yahoo, it is a step (albeit a small one) in the right direction.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: leisa.reichelt</title>
		<link>http://www.disambiguity.com/yahoo-go-20-shows-how-far-mobile-ui-design-has-to-go/#comment-8207</link>
		<dc:creator>leisa.reichelt</dc:creator>
		<pubDate>Tue, 09 Jan 2007 16:14:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.disambiguity.com/yahoo-go-20-shows-how-far-mobile-ui-design-has-to-go/#comment-8207</guid>
		<description>Interesting comment re: walled garden Olly.

I think it's really interesting with mobile internet that there is such a strong *perception* of a walled garden when, in most instances that I've come across, the garden isn't actually walled at all!

True &lt;a href="http://en.wikipedia.org/wiki/Walled_garden_(media)" / rel="nofollow"&gt;Walled gardens&lt;/a&gt; seem to be pretty rare these days, meaning that you can almost always access the 'real' internet... but the way that the landing pages for each network are designed, the exit points are often difficult to locate (even when you're looking for them), and the OS UI rarely helps. So, intriguingly, we end up with imaginary walls.</description>
		<content:encoded><![CDATA[<p>Interesting comment re: walled garden Olly.</p>
<p>I think it&#8217;s really interesting with mobile internet that there is such a strong *perception* of a walled garden when, in most instances that I&#8217;ve come across, the garden isn&#8217;t actually walled at all!</p>
<p>True <a href="http://en.wikipedia.org/wiki/Walled_garden_(media)" / rel="nofollow">Walled gardens</a> seem to be pretty rare these days, meaning that you can almost always access the &#8216;real&#8217; internet&#8230; but the way that the landing pages for each network are designed, the exit points are often difficult to locate (even when you&#8217;re looking for them), and the OS UI rarely helps. So, intriguingly, we end up with imaginary walls.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Olly Wright</title>
		<link>http://www.disambiguity.com/yahoo-go-20-shows-how-far-mobile-ui-design-has-to-go/#comment-8205</link>
		<dc:creator>Olly Wright</dc:creator>
		<pubDate>Tue, 09 Jan 2007 15:47:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.disambiguity.com/yahoo-go-20-shows-how-far-mobile-ui-design-has-to-go/#comment-8205</guid>
		<description>"It’s outrageous that little seems to be happening to increase consistency across handsets and browsers and operating systems"

If only! Unfortunately we have deadlock because everyone is competing with everyone else. The operators don't want to work with each other, and don't want to cede 'control of the customer' to the .coms (google, yahoo, etc). Meanwhile the handset manufacturers don't want to work with each other and don't want to hand over complete UX control to the operators (who tend to be very bad at it anyway).

Result... gridlock

Yahoo Go is interesting but it's still walled-garden-like. And I have reservations about the use of lots of different midlets (assuming this is a midlet?). 

iMode worked for very specific reasons to do with the Japanese market. Namely extreme control by the operators (DoCoMo and AU KDDI are the only serious operators there), who specified iMode standards to all handset manufacturers. There is no parallel to this market structure outside of Japan.</description>
		<content:encoded><![CDATA[<p>&#8220;It’s outrageous that little seems to be happening to increase consistency across handsets and browsers and operating systems&#8221;</p>
<p>If only! Unfortunately we have deadlock because everyone is competing with everyone else. The operators don&#8217;t want to work with each other, and don&#8217;t want to cede &#8216;control of the customer&#8217; to the .coms (google, yahoo, etc). Meanwhile the handset manufacturers don&#8217;t want to work with each other and don&#8217;t want to hand over complete UX control to the operators (who tend to be very bad at it anyway).</p>
<p>Result&#8230; gridlock</p>
<p>Yahoo Go is interesting but it&#8217;s still walled-garden-like. And I have reservations about the use of lots of different midlets (assuming this is a midlet?). </p>
<p>iMode worked for very specific reasons to do with the Japanese market. Namely extreme control by the operators (DoCoMo and AU KDDI are the only serious operators there), who specified iMode standards to all handset manufacturers. There is no parallel to this market structure outside of Japan.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ric</title>
		<link>http://www.disambiguity.com/yahoo-go-20-shows-how-far-mobile-ui-design-has-to-go/#comment-8200</link>
		<dc:creator>Ric</dc:creator>
		<pubDate>Tue, 09 Jan 2007 13:45:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.disambiguity.com/yahoo-go-20-shows-how-far-mobile-ui-design-has-to-go/#comment-8200</guid>
		<description>In Moggridge's "Designing Interactions" there is an interview with one of the people involved with the introduction of iMode in Japan, and they noted that you are often at the mercy of the third-party suppliers of services when it comes to interactions - is that an issue with Go 2.0?</description>
		<content:encoded><![CDATA[<p>In Moggridge&#8217;s &#8220;Designing Interactions&#8221; there is an interview with one of the people involved with the introduction of iMode in Japan, and they noted that you are often at the mercy of the third-party suppliers of services when it comes to interactions - is that an issue with Go 2.0?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
