<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: The Mechanics Behind the Mobile User Interface</title>
	<atom:link href="http://www.visionmobile.com/blog/2009/05/the-mechanics-behind-the-mobile-user-interface/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.visionmobile.com/blog/2009/05/the-mechanics-behind-the-mobile-user-interface/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=the-mechanics-behind-the-mobile-user-interface</link>
	<description>Distilling market noise into market sense.</description>
	<lastBuildDate>Mon, 06 Sep 2010 09:00:45 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Andreas Constantinou</title>
		<link>http://www.visionmobile.com/blog/2009/05/the-mechanics-behind-the-mobile-user-interface/comment-page-1/#comment-66767</link>
		<dc:creator>Andreas Constantinou</dc:creator>
		<pubDate>Tue, 09 Jun 2009 07:54:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.visionmobile.com/blog/?p=736#comment-66767</guid>
		<description>Hi Steph,

Good point - OEMs will be reluctant to see core apps replaced due to liabilities and brand dilution. 

However, OEMs should be able to allow 3rd party core apps (calendar, contacts, inbox, etc) to be developed as premium content (selected content only) and downloaded via an app store. This will allow a new type of content - what we &#039;ve called &#039;UI personalities&#039; to be created (see &lt;a href=&quot;http://www.visionmobile.com/blog/2009/01/ui-personalities-a-new-premium-content-market-on-the-radar/&quot; rel=&quot;nofollow&quot;&gt;earlier article&lt;/a&gt;). A market of this type is already established in Japan by the 3 major operators.

Andreas</description>
		<content:encoded><![CDATA[<p>Hi Steph,</p>
<p>Good point &#8211; OEMs will be reluctant to see core apps replaced due to liabilities and brand dilution. </p>
<p>However, OEMs should be able to allow 3rd party core apps (calendar, contacts, inbox, etc) to be developed as premium content (selected content only) and downloaded via an app store. This will allow a new type of content &#8211; what we &#8216;ve called &#8216;UI personalities&#8217; to be created (see <a href="http://www.visionmobile.com/blog/2009/01/ui-personalities-a-new-premium-content-market-on-the-radar/" rel="nofollow">earlier article</a>). A market of this type is already established in Japan by the 3 major operators.</p>
<p>Andreas</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steph</title>
		<link>http://www.visionmobile.com/blog/2009/05/the-mechanics-behind-the-mobile-user-interface/comment-page-1/#comment-66724</link>
		<dc:creator>Steph</dc:creator>
		<pubDate>Tue, 02 Jun 2009 13:30:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.visionmobile.com/blog/?p=736#comment-66724</guid>
		<description>Hi Andreas, 

 I indeed believe the boundary between Core and Download apps is reducing at least in term of integration capability and UX. I-Phone is definitely a good example for this. (although facilitated by supporting only one form factor/kind of device).

Opening all the phone environment (phone book, calendar) to 3rd parties is indeed not without risk for OEMs both from a security viewpoint and you rightly pointed this out.  I see another reason for OEM to be reluctant: Ability to differentiate.  

Do you see  Nokia, Samsung and co leaving the core-apps ground to generic-UI/3rd-party-branded apps?

I don&#039;t see that happening yet and  I&#039;m as such still curious on the evolution, deployment and flavours of Android at top OEMs.  I believe fragmentation risk is high.

Stephane</description>
		<content:encoded><![CDATA[<p>Hi Andreas, </p>
<p> I indeed believe the boundary between Core and Download apps is reducing at least in term of integration capability and UX. I-Phone is definitely a good example for this. (although facilitated by supporting only one form factor/kind of device).</p>
<p>Opening all the phone environment (phone book, calendar) to 3rd parties is indeed not without risk for OEMs both from a security viewpoint and you rightly pointed this out.  I see another reason for OEM to be reluctant: Ability to differentiate.  </p>
<p>Do you see  Nokia, Samsung and co leaving the core-apps ground to generic-UI/3rd-party-branded apps?</p>
<p>I don&#8217;t see that happening yet and  I&#8217;m as such still curious on the evolution, deployment and flavours of Android at top OEMs.  I believe fragmentation risk is high.</p>
<p>Stephane</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andreas Constantinou</title>
		<link>http://www.visionmobile.com/blog/2009/05/the-mechanics-behind-the-mobile-user-interface/comment-page-1/#comment-66704</link>
		<dc:creator>Andreas Constantinou</dc:creator>
		<pubDate>Fri, 29 May 2009 14:17:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.visionmobile.com/blog/?p=736#comment-66704</guid>
		<description>Hi jcj,

The &#039;power apps&#039; moniker unfortunately is a poor one at explaining what facilities/flexibility/APIs/etc make the app special. The one objective metric to use for &#039;power apps&#039; is the % portion of the user journey, but no one in the industry publishes accurate data so far - and as such I could not argue in favour or against media players being &#039;power apps&#039;. 

The idle screen should increasingly &#039;consume&#039; more and more data (service status, ads, device info, user info, etc). But that doesn&#039;t mean that calendar info will end up exclusively on the idle screen. There will always be a many-to-many relationship between data sources and apps which mashup that data. So the calendar-on-steroids app will also include location, contacts info, mashed with event info, network plans info (e.g. you are eligible for an update in 1 month), etc.

Overall I see the calendar app as a &#039;power app&#039; as the time-based view (what you can do today, tomorrow and what you did last month) to be an underserved one with little innovation to date; yet there is a clear need as time is the fundamental variable by which we perceive our environment (maybe I &#039;m getting to scientific now :)

Andreas</description>
		<content:encoded><![CDATA[<p>Hi jcj,</p>
<p>The &#8216;power apps&#8217; moniker unfortunately is a poor one at explaining what facilities/flexibility/APIs/etc make the app special. The one objective metric to use for &#8216;power apps&#8217; is the % portion of the user journey, but no one in the industry publishes accurate data so far &#8211; and as such I could not argue in favour or against media players being &#8216;power apps&#8217;. </p>
<p>The idle screen should increasingly &#8216;consume&#8217; more and more data (service status, ads, device info, user info, etc). But that doesn&#8217;t mean that calendar info will end up exclusively on the idle screen. There will always be a many-to-many relationship between data sources and apps which mashup that data. So the calendar-on-steroids app will also include location, contacts info, mashed with event info, network plans info (e.g. you are eligible for an update in 1 month), etc.</p>
<p>Overall I see the calendar app as a &#8216;power app&#8217; as the time-based view (what you can do today, tomorrow and what you did last month) to be an underserved one with little innovation to date; yet there is a clear need as time is the fundamental variable by which we perceive our environment (maybe I &#8216;m getting to scientific now <img src='http://www.visionmobile.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Andreas</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jcj</title>
		<link>http://www.visionmobile.com/blog/2009/05/the-mechanics-behind-the-mobile-user-interface/comment-page-1/#comment-66700</link>
		<dc:creator>jcj</dc:creator>
		<pubDate>Fri, 29 May 2009 06:15:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.visionmobile.com/blog/?p=736#comment-66700</guid>
		<description>Interesting article.. A few comments/questions:

- Given the rise in media consumption, wouldn&#039;t a media player, especially one that integrated well with popular media sources on the internet be one of the &quot;power apps&quot;?

- You mentioned location apps of the future having many views. An alternate view would be to think of location apps as continuing to be map based but location (esp current location) could be an important piece of contextual information that can be used to enhance other apps. 

- Is the Calendar likely to graduate into playing such a significant role, given its current insignificance (it doesn&#039;t merit mention in the &quot;user journey&quot; diagram)...I think that some of the functionality mentioned in Calendar 2.0 will actually end up in the Idle Screen app.</description>
		<content:encoded><![CDATA[<p>Interesting article.. A few comments/questions:</p>
<p>- Given the rise in media consumption, wouldn&#8217;t a media player, especially one that integrated well with popular media sources on the internet be one of the &#8220;power apps&#8221;?</p>
<p>- You mentioned location apps of the future having many views. An alternate view would be to think of location apps as continuing to be map based but location (esp current location) could be an important piece of contextual information that can be used to enhance other apps. </p>
<p>- Is the Calendar likely to graduate into playing such a significant role, given its current insignificance (it doesn&#8217;t merit mention in the &#8220;user journey&#8221; diagram)&#8230;I think that some of the functionality mentioned in Calendar 2.0 will actually end up in the Idle Screen app.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt Millar</title>
		<link>http://www.visionmobile.com/blog/2009/05/the-mechanics-behind-the-mobile-user-interface/comment-page-1/#comment-66662</link>
		<dc:creator>Matt Millar</dc:creator>
		<pubDate>Wed, 27 May 2009 08:44:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.visionmobile.com/blog/?p=736#comment-66662</guid>
		<description>Phonebook 2.0 is an interesting space - as integration of social aspects from web 2.0 changes the value added by the phone operators.

See http://www.hellosonar.com/ for another example of innovation in this space.</description>
		<content:encoded><![CDATA[<p>Phonebook 2.0 is an interesting space &#8211; as integration of social aspects from web 2.0 changes the value added by the phone operators.</p>
<p>See <a href="http://www.hellosonar.com/" rel="nofollow">http://www.hellosonar.com/</a> for another example of innovation in this space.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andreas Constantinou</title>
		<link>http://www.visionmobile.com/blog/2009/05/the-mechanics-behind-the-mobile-user-interface/comment-page-1/#comment-66630</link>
		<dc:creator>Andreas Constantinou</dc:creator>
		<pubDate>Tue, 26 May 2009 22:03:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.visionmobile.com/blog/?p=736#comment-66630</guid>
		<description>Hi Sneed,

The diagram is an illustration of a simplified user journey, but not an actual or &#039;average&#039; user journey. We &#039;ve omitted most apps to demonstrate the concept. In practice there are high 10s of apps in a phone. 

Andreas</description>
		<content:encoded><![CDATA[<p>Hi Sneed,</p>
<p>The diagram is an illustration of a simplified user journey, but not an actual or &#8216;average&#8217; user journey. We &#8216;ve omitted most apps to demonstrate the concept. In practice there are high 10s of apps in a phone. </p>
<p>Andreas</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sneed</title>
		<link>http://www.visionmobile.com/blog/2009/05/the-mechanics-behind-the-mobile-user-interface/comment-page-1/#comment-66621</link>
		<dc:creator>sneed</dc:creator>
		<pubDate>Tue, 26 May 2009 18:33:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.visionmobile.com/blog/?p=736#comment-66621</guid>
		<description>There seems to be a lot of apps missing from the &quot;user journey&quot; - GPS? email? 

why? does it just represent the core apps?</description>
		<content:encoded><![CDATA[<p>There seems to be a lot of apps missing from the &#8220;user journey&#8221; &#8211; GPS? email? </p>
<p>why? does it just represent the core apps?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Xatakamovil</title>
		<link>http://www.visionmobile.com/blog/2009/05/the-mechanics-behind-the-mobile-user-interface/comment-page-1/#comment-66690</link>
		<dc:creator>Xatakamovil</dc:creator>
		<pubDate>Thu, 01 Jan 1970 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.visionmobile.com/blog/?p=736#comment-66690</guid>
		<description>&lt;!--%kramer-pre%--&gt;Pero creo que la guía de contactos, la agenda y la localización son los campos más prometedores. Simplemente porque así es como los humanos concebimos el mundo: por la gente, el tiempo y los lugares que nos rodean. Vía &#124;Vision Mobile&lt;!--%kramer-post%--&gt;</description>
		<content:encoded><![CDATA[<div style="margin: 0; padding: 1em; background: #666666; color: #FFFFFF;">
<p><!--%kramer-pre%-->Pero creo que la guía de contactos, la agenda y la localización son los campos más prometedores. Simplemente porque así es como los humanos concebimos el mundo: por la gente, el tiempo y los lugares que nos rodean. Vía |Vision Mobile<!--%kramer-post%--></p>
</div>
]]></content:encoded>
	</item>
	<item>
		<title>By: bitácora sortega</title>
		<link>http://www.visionmobile.com/blog/2009/05/the-mechanics-behind-the-mobile-user-interface/comment-page-1/#comment-66733</link>
		<dc:creator>bitácora sortega</dc:creator>
		<pubDate>Thu, 01 Jan 1970 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.visionmobile.com/blog/?p=736#comment-66733</guid>
		<description>&lt;!--%kramer-pre%--&gt;notables diferencias en las dos visiones ofrecidas y, en cierto modo, son un ejemplo del camino que falta por recorrer para acercar las necesidades e intereses de los usuarios al ritmo de la extensa y compleja industria de los móviles. Son datos significativos que,sumados a otras aportaciones, pueden orientar algunas líneas de investigación que es necesario abordar desde la experiencia del usuario de dispositivos móviles. Aquí os dejo el extracto del punto 4 del Manifiesto. Cuestiona la estrategia seguida en la era&lt;!--%kramer-post%--&gt;</description>
		<content:encoded><![CDATA[<div style="margin: 0; padding: 1em; background: #666666; color: #FFFFFF;">
<p><!--%kramer-pre%-->notables diferencias en las dos visiones ofrecidas y, en cierto modo, son un ejemplo del camino que falta por recorrer para acercar las necesidades e intereses de los usuarios al ritmo de la extensa y compleja industria de los móviles. Son datos significativos que,sumados a otras aportaciones, pueden orientar algunas líneas de investigación que es necesario abordar desde la experiencia del usuario de dispositivos móviles. Aquí os dejo el extracto del punto 4 del Manifiesto. Cuestiona la estrategia seguida en la era<!--%kramer-post%--></p>
</div>
]]></content:encoded>
	</item>
</channel>
</rss>
