<?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 for UIEvolution</title>
	<atom:link href="http://www.uievolution.com/blog/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.uievolution.com/blog</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Tue, 18 Jan 2011 02:53:04 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Millennial Media: Mobile Ad Network Market Share by Monetizing Mobile And Tablet Applications – Options Available &#171; UIEvolution</title>
		<link>http://www.uievolution.com/blog/2011/01/millennial-media-mobile-ad-network-market-share/comment-page-1/#comment-15</link>
		<dc:creator>Monetizing Mobile And Tablet Applications – Options Available &#171; UIEvolution</dc:creator>
		<pubDate>Tue, 18 Jan 2011 02:53:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.uievolution.com/blog/?p=432#comment-15</guid>
		<description>[...] Free Apps Subsidized By Advertising: This category of applications makes up nearly 90% of all new applications in the market.  Since most small app developers do not have the ability to sell their own advertising, the easiest way to get into this business model is to partner with a leading advertising network.  UIE partners with Millennial Media, Google/Admob and Apple’s iAd to monetize our published apps.  One thing that an app developer must understand is that while these networks make it easy to get into the market you need to 1) integrate some of their client code into your app and 2) even the best generally do not have fill rates over 60% on an application.  This mean that at a minumum 40% of your ad requests will be unfilled.  For a current ranking of ad networks go to http://www.uievolution.com/blog/2011/01/millennial-media-mobile-ad-network-market-share/. [...]</description>
		<content:encoded><![CDATA[<p>[...] Free Apps Subsidized By Advertising: This category of applications makes up nearly 90% of all new applications in the market.  Since most small app developers do not have the ability to sell their own advertising, the easiest way to get into this business model is to partner with a leading advertising network.  UIE partners with Millennial Media, Google/Admob and Apple’s iAd to monetize our published apps.  One thing that an app developer must understand is that while these networks make it easy to get into the market you need to 1) integrate some of their client code into your app and 2) even the best generally do not have fill rates over 60% on an application.  This mean that at a minumum 40% of your ad requests will be unfilled.  For a current ranking of ad networks go to <a href="http://www.uievolution.com/blog/2011/01/millennial-media-mobile-ad-network-market-share/" rel="nofollow">http://www.uievolution.com/blog/2011/01/millennial-media-mobile-ad-network-market-share/</a>. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on WAC progress &#8211; Maybe it isn&#8217;t so wacky after all by MOBILE HTML5 AND BONDI – A CASE STUDY ON THE SAMSUNG WAVE &#171; UIEvolution</title>
		<link>http://www.uievolution.com/blog/2010/08/wac-progress-maybe-it-isnt-so-wacky-after-all/comment-page-1/#comment-12</link>
		<dc:creator>MOBILE HTML5 AND BONDI – A CASE STUDY ON THE SAMSUNG WAVE &#171; UIEvolution</dc:creator>
		<pubDate>Thu, 23 Sep 2010 06:45:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.uievolution.com/blog/?p=289#comment-12</guid>
		<description>[...] runtime (WRT) that supports BONDI 1.01. I have given an overview of both HTML5 and BONDI 1.01 in a previous post. When we combine the capabilities of HTML5 and BONDI, we can build useful applications very [...]</description>
		<content:encoded><![CDATA[<p>[...] runtime (WRT) that supports BONDI 1.01. I have given an overview of both HTML5 and BONDI 1.01 in a previous post. When we combine the capabilities of HTML5 and BONDI, we can build useful applications very [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Mobile Widgets &#8211; Moving Beyond the Clock by WAC progress &#8211; Maybe it isn&#8217;t so wacky after all &#171; UIEvolution</title>
		<link>http://www.uievolution.com/blog/2010/06/mobile-widgets-%e2%80%93-moving-beyond-the-clock/comment-page-1/#comment-11</link>
		<dc:creator>WAC progress &#8211; Maybe it isn&#8217;t so wacky after all &#171; UIEvolution</dc:creator>
		<pubDate>Wed, 18 Aug 2010 18:57:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.uievolution.com/blog/?p=269#comment-11</guid>
		<description>[...] In February 2010, the Wholesale Applications Community (WAC) was formed. This is an ambitious effort that brings together many different mobile operators and device manufacturers. The goal is to “simplify application development by giving developers the opportunity to write applications that can be deployed across multiple platforms and multiple operators.” This goal is to be accomplished with an API specification built on web technologies and by allowing the distribution of mobile applications to multiple operator stores. At the time WAC was formed, there were two existing API specifications with essentially the same goal. One of these was the OMTP BONDI API, and another was the Joint Innovation Labs (JIL) API. For background on BONDI and JIL, see “Moving Beyond the Clock”. [...]</description>
		<content:encoded><![CDATA[<p>[...] In February 2010, the Wholesale Applications Community (WAC) was formed. This is an ambitious effort that brings together many different mobile operators and device manufacturers. The goal is to “simplify application development by giving developers the opportunity to write applications that can be deployed across multiple platforms and multiple operators.” This goal is to be accomplished with an API specification built on web technologies and by allowing the distribution of mobile applications to multiple operator stores. At the time WAC was formed, there were two existing API specifications with essentially the same goal. One of these was the OMTP BONDI API, and another was the Joint Innovation Labs (JIL) API. For background on BONDI and JIL, see “Moving Beyond the Clock”. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Mobile Widgets &#8211; Moving Beyond the Clock by Mobile Widgets and HTML5 – Riding the Wave &#171; UIEvolution</title>
		<link>http://www.uievolution.com/blog/2010/06/mobile-widgets-%e2%80%93-moving-beyond-the-clock/comment-page-1/#comment-9</link>
		<dc:creator>Mobile Widgets and HTML5 – Riding the Wave &#171; UIEvolution</dc:creator>
		<pubDate>Tue, 13 Jul 2010 19:18:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.uievolution.com/blog/?p=269#comment-9</guid>
		<description>[...] are also available in the widget runtime. These HTML5 features, combined with the BONDI support available in the widget runtime, create a rich programming API for the widget [...]</description>
		<content:encoded><![CDATA[<p>[...] are also available in the widget runtime. These HTML5 features, combined with the BONDI support available in the widget runtime, create a rich programming API for the widget [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on doodads or gizmos… What is a widget? by Mobile Widgets – Moving Beyond the Clock &#171; UIEvolution</title>
		<link>http://www.uievolution.com/blog/2010/06/doodads-or-gizmos%e2%80%a6-what-is-a-widget/comment-page-1/#comment-7</link>
		<dc:creator>Mobile Widgets – Moving Beyond the Clock &#171; UIEvolution</dc:creator>
		<pubDate>Tue, 29 Jun 2010 18:12:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.uievolution.com/blog/?p=227#comment-7</guid>
		<description>[...] last post explored the question of &#8220;What is a widget?&#8221; This post takes that question a little further, investigating what types of applications might be [...]</description>
		<content:encoded><![CDATA[<p>[...] last post explored the question of &#8220;What is a widget?&#8221; This post takes that question a little further, investigating what types of applications might be [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

