<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Container projects: The next chapter in handset customisation</title>
	<link>http://www.visionmobile.com/blog/2007/06/container-projects-the-next-chapter-in-handset-customisation/</link>
	<description>Distilling market noise into market sense.</description>
	<pubDate>Sat, 17 May 2008 02:46:49 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: VisionMobile Forum :: The headaches of being a handset OEM</title>
		<link>http://www.visionmobile.com/blog/2007/06/container-projects-the-next-chapter-in-handset-customisation/#comment-27388</link>
		<dc:creator>VisionMobile Forum :: The headaches of being a handset OEM</dc:creator>
		<pubDate>Sat, 02 Feb 2008 09:14:12 +0000</pubDate>
		<guid>http://www.visionmobile.com/blog/2007/06/container-projects-the-next-chapter-in-handset-customisation/#comment-27388</guid>
		<description>&lt;!--%kramer-ref-pre%--&gt;[...] The next chapter in handset customisation [...]&lt;!--%kramer-ref-post%--&gt;</description>
		<content:encoded><![CDATA[<p><a href="http://dev.wp-plugins.org/wiki/Kramer"><img src="/blog/wp-content/plugins/kramer/kramer.php?kramer=gif-icon" class="technorati-balloon" alt="Kramer auto Pingback" style="border:0;" /></a>[&#8230;] The next chapter in handset customisation [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Everything and the Mobile Software Universe&#8230; &#187; Mobile Web 2.0 in the real world : SFR (Vodafone France) new offer (YouTube,DailyMotion,MSN,MySpace,eBay,Google Maps)</title>
		<link>http://www.visionmobile.com/blog/2007/06/container-projects-the-next-chapter-in-handset-customisation/#comment-6697</link>
		<dc:creator>Everything and the Mobile Software Universe&#8230; &#187; Mobile Web 2.0 in the real world : SFR (Vodafone France) new offer (YouTube,DailyMotion,MSN,MySpace,eBay,Google Maps)</dc:creator>
		<pubDate>Wed, 11 Jul 2007 23:33:02 +0000</pubDate>
		<guid>http://www.visionmobile.com/blog/2007/06/container-projects-the-next-chapter-in-handset-customisation/#comment-6697</guid>
		<description>[...] it (at last!) leaves it to the service providers themselves&#8230;it is perhaps time for the Andreas Container Projects? to help those kind of deployment, with no to little¬†OEM [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] it (at last!) leaves it to the service providers themselves&#8230;it is perhaps time for the Andreas Container Projects? to help those kind of deployment, with no to little¬†OEM [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andreas Constantinou</title>
		<link>http://www.visionmobile.com/blog/2007/06/container-projects-the-next-chapter-in-handset-customisation/#comment-6203</link>
		<dc:creator>Andreas Constantinou</dc:creator>
		<pubDate>Mon, 02 Jul 2007 16:50:53 +0000</pubDate>
		<guid>http://www.visionmobile.com/blog/2007/06/container-projects-the-next-chapter-in-handset-customisation/#comment-6203</guid>
		<description>Hi jcj,

Here's my take:

1. HSIs would deal with partner licensing, integration, validation, testing, project management, etc, i.e they would be involved after the partner ISV has sealed the deal with the operator. The long sales cycle problem applies up to the point of sealing the deal. Operators would pass on the liability for potential failures onto HSIs, who would in turn pass it onto the ISVs themselves.

2. Operators would want to take partner management away from the OEM so that they control which features/services are deployed on the OEM platform and have control of the overall integration project (as long as they can get away with it). Letting the OEM manage partner apps means the OEM can always come up with excuses, e.g. partner integration took too long and delayed the device launch, etc. In effect this takes the OEM outside the service delivery equation (well, almost).

Makes sense ?

Andreas</description>
		<content:encoded><![CDATA[<p>Hi jcj,</p>
<p>Here&#8217;s my take:</p>
<p>1. HSIs would deal with partner licensing, integration, validation, testing, project management, etc, i.e they would be involved after the partner ISV has sealed the deal with the operator. The long sales cycle problem applies up to the point of sealing the deal. Operators would pass on the liability for potential failures onto HSIs, who would in turn pass it onto the ISVs themselves.</p>
<p>2. Operators would want to take partner management away from the OEM so that they control which features/services are deployed on the OEM platform and have control of the overall integration project (as long as they can get away with it). Letting the OEM manage partner apps means the OEM can always come up with excuses, e.g. partner integration took too long and delayed the device launch, etc. In effect this takes the OEM outside the service delivery equation (well, almost).</p>
<p>Makes sense ?</p>
<p>Andreas</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jcj</title>
		<link>http://www.visionmobile.com/blog/2007/06/container-projects-the-next-chapter-in-handset-customisation/#comment-6010</link>
		<dc:creator>jcj</dc:creator>
		<pubDate>Fri, 29 Jun 2007 12:34:58 +0000</pubDate>
		<guid>http://www.visionmobile.com/blog/2007/06/container-projects-the-next-chapter-in-handset-customisation/#comment-6010</guid>
		<description>Wouldnt a number of the problems associated with the container approach continue to exist even after having an HSI? Software suppliers would still need to sell to operators and would therefore have to work through the long sales cycle problem. Operators would have to continue to deal with licensing, liability issues and potential business failures of partners.

And if the operator is only looking at contained partner applications (and not at container technology) wouldn't it be better to have the OEM handle the application integration instead of bringing in an HSI?</description>
		<content:encoded><![CDATA[<p>Wouldnt a number of the problems associated with the container approach continue to exist even after having an HSI? Software suppliers would still need to sell to operators and would therefore have to work through the long sales cycle problem. Operators would have to continue to deal with licensing, liability issues and potential business failures of partners.</p>
<p>And if the operator is only looking at contained partner applications (and not at container technology) wouldn&#8217;t it be better to have the OEM handle the application integration instead of bringing in an HSI?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andreas Constantinou</title>
		<link>http://www.visionmobile.com/blog/2007/06/container-projects-the-next-chapter-in-handset-customisation/#comment-5654</link>
		<dc:creator>Andreas Constantinou</dc:creator>
		<pubDate>Thu, 21 Jun 2007 16:03:53 +0000</pubDate>
		<guid>http://www.visionmobile.com/blog/2007/06/container-projects-the-next-chapter-in-handset-customisation/#comment-5654</guid>
		<description>Hi Guy,

You 're right - we need to differentiate between 'container technology' and 'contained partner applications'. 

European operators are about contained platform applications mostly (although Vodafone has in the past experiemented with container technology in the form of VSCL/VFX). Japanese operators are about container technology (DoJa/MOAP, BREW, POP-i) AND contained partner applications (e.g. Acrodea being specified by both DoCoMo and KDDI on all handsets from end 07).

Andreas</description>
		<content:encoded><![CDATA[<p>Hi Guy,</p>
<p>You &#8216;re right - we need to differentiate between &#8216;container technology&#8217; and &#8216;contained partner applications&#8217;. </p>
<p>European operators are about contained platform applications mostly (although Vodafone has in the past experiemented with container technology in the form of VSCL/VFX). Japanese operators are about container technology (DoJa/MOAP, BREW, POP-i) AND contained partner applications (e.g. Acrodea being specified by both DoCoMo and KDDI on all handsets from end 07).</p>
<p>Andreas</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Guy A.</title>
		<link>http://www.visionmobile.com/blog/2007/06/container-projects-the-next-chapter-in-handset-customisation/#comment-5652</link>
		<dc:creator>Guy A.</dc:creator>
		<pubDate>Thu, 21 Jun 2007 15:12:17 +0000</pubDate>
		<guid>http://www.visionmobile.com/blog/2007/06/container-projects-the-next-chapter-in-handset-customisation/#comment-5652</guid>
		<description>Andreas, just to be accurate here, in my opinion, "common platform" approaches or "platformization" strategies are related but are not the same as Containers of the type that Orange is doing. In the case of DoCoMo, its a complete Platform strategy - they specified Linux and Symbian, and they developed an entire UI/app/Middleware layer on top- which they licensed to their OEMs- that's SW development,not application sourcing. In the case of KDDI Common Platform- they also created a common BREW layer for the whole portfolio- ALL their handsets are supposed to share the same exact application environment. As for Softbank's POP-i, creating some special common API layer that supposed to create commonality across platforms. 

That is a much more technological approach, and it is not the same as simply specifying and sourcing a set of ISV custom apps, to be installed on top of a standard Open OS that has no special "layer" or "API" or "framework" specifically created by that Operator. European operators cannot really duplicate the approch of Japanese or even US Operators, so their Container strategy is just about the content of the container, not really "container technology". do you agree?</description>
		<content:encoded><![CDATA[<p>Andreas, just to be accurate here, in my opinion, &#8220;common platform&#8221; approaches or &#8220;platformization&#8221; strategies are related but are not the same as Containers of the type that Orange is doing. In the case of DoCoMo, its a complete Platform strategy - they specified Linux and Symbian, and they developed an entire UI/app/Middleware layer on top- which they licensed to their OEMs- that&#8217;s SW development,not application sourcing. In the case of KDDI Common Platform- they also created a common BREW layer for the whole portfolio- ALL their handsets are supposed to share the same exact application environment. As for Softbank&#8217;s POP-i, creating some special common API layer that supposed to create commonality across platforms. </p>
<p>That is a much more technological approach, and it is not the same as simply specifying and sourcing a set of ISV custom apps, to be installed on top of a standard Open OS that has no special &#8220;layer&#8221; or &#8220;API&#8221; or &#8220;framework&#8221; specifically created by that Operator. European operators cannot really duplicate the approch of Japanese or even US Operators, so their Container strategy is just about the content of the container, not really &#8220;container technology&#8221;. do you agree?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Everything and the Mobile Software Universe&#8230; &#187; 2007 &#187;</title>
		<link>http://www.visionmobile.com/blog/2007/06/container-projects-the-next-chapter-in-handset-customisation/#comment-5152</link>
		<dc:creator>Everything and the Mobile Software Universe&#8230; &#187; 2007 &#187;</dc:creator>
		<pubDate>Thu, 14 Jun 2007 15:08:52 +0000</pubDate>
		<guid>http://www.visionmobile.com/blog/2007/06/container-projects-the-next-chapter-in-handset-customisation/#comment-5152</guid>
		<description>&lt;!--%kramer-ref-pre%--&gt;[...] Container projects: The next chapter in handset customisationVisionMobile ForumMobile Linux UI gains fancy visual effectsLinuxDevices.comIMS :Seeing is believing, Fraunhofer FOKUS ,Open IMS, Mobile Web 2.0 and IMSOpen GardensProof Mobile AJAX Only Works In A Parallel RealitytechypeThe seven deadly sins of mobile retail salesSMS Text NewsThe Mojax ManifestoMobUserTechnologie riche #9 : Microsoft SilverlightFabien DeshayesThe story of Helio's OceanSmall SurfacesPilot Program Launched for French Transit SystemMobileCrunchTV &#38; Music Soar as Game Market Slows on MobileMobileCrunch [...]&lt;!--%kramer-ref-post%--&gt;</description>
		<content:encoded><![CDATA[<p><a href="http://dev.wp-plugins.org/wiki/Kramer"><img src="/blog/wp-content/plugins/kramer/kramer.php?kramer=gif-icon" class="technorati-balloon" alt="Kramer auto Pingback" style="border:0;" /></a>[&#8230;] Container projects: The next chapter in handset customisationVisionMobile ForumMobile Linux UI gains fancy visual effectsLinuxDevices.comIMS :Seeing is believing, Fraunhofer FOKUS ,Open IMS, Mobile Web 2.0 and IMSOpen GardensProof Mobile AJAX Only Works In A Parallel RealitytechypeThe seven deadly sins of mobile retail salesSMS Text NewsThe Mojax ManifestoMobUserTechnologie riche #9 : Microsoft SilverlightFabien DeshayesThe story of Helio&#8217;s OceanSmall SurfacesPilot Program Launched for French Transit SystemMobileCrunchTV &amp; Music Soar as Game Market Slows on MobileMobileCrunch [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: VoIP &#38; TLC news - luned&#236; 11 giugno</title>
		<link>http://www.visionmobile.com/blog/2007/06/container-projects-the-next-chapter-in-handset-customisation/#comment-4900</link>
		<dc:creator>VoIP &#38; TLC news - luned&#236; 11 giugno</dc:creator>
		<pubDate>Mon, 11 Jun 2007 03:22:17 +0000</pubDate>
		<guid>http://www.visionmobile.com/blog/2007/06/container-projects-the-next-chapter-in-handset-customisation/#comment-4900</guid>
		<description>[...] Container projects: il prossimo capitolo nella customizzazione dei telefoni cellulari Come gli operatori di telefonia mobile portano sul mercato terminali con software e funzionalit?† da loro richieste e cosa sta cambiando&#8230; (tags: mobile software applications operators) [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Container projects: il prossimo capitolo nella customizzazione dei telefoni cellulari Come gli operatori di telefonia mobile portano sul mercato terminali con software e funzionalit?† da loro richieste e cosa sta cambiando&#8230; (tags: mobile software applications operators) [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: outside the vox: Container projects: The next chapter in handset customisation.</title>
		<link>http://www.visionmobile.com/blog/2007/06/container-projects-the-next-chapter-in-handset-customisation/#comment-4756</link>
		<dc:creator>outside the vox: Container projects: The next chapter in handset customisation.</dc:creator>
		<pubDate>Fri, 08 Jun 2007 20:46:32 +0000</pubDate>
		<guid>http://www.visionmobile.com/blog/2007/06/container-projects-the-next-chapter-in-handset-customisation/#comment-4756</guid>
		<description>&lt;!--%kramer-ref-pre%--&gt;[...] Container projects: The next chapter in handset customisation. [...]&lt;!--%kramer-ref-post%--&gt;</description>
		<content:encoded><![CDATA[<p><a href="http://dev.wp-plugins.org/wiki/Kramer"><img src="/blog/wp-content/plugins/kramer/kramer.php?kramer=gif-icon" class="technorati-balloon" alt="Kramer auto Pingback" style="border:0;" /></a>[&#8230;] Container projects: The next chapter in handset customisation. [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: twofones: Carnival of the Mobilists #76</title>
		<link>http://www.visionmobile.com/blog/2007/06/container-projects-the-next-chapter-in-handset-customisation/#comment-4498</link>
		<dc:creator>twofones: Carnival of the Mobilists #76</dc:creator>
		<pubDate>Mon, 04 Jun 2007 09:00:07 +0000</pubDate>
		<guid>http://www.visionmobile.com/blog/2007/06/container-projects-the-next-chapter-in-handset-customisation/#comment-4498</guid>
		<description>&lt;!--%kramer-ref-pre%--&gt;[...] questions on how operators handle handset customization - Andreas has your answers.&#160; He writes a long and thoughtful piece at Vision Mobile on a new strategy in handset customization ‚Äì Container Projects.&#160; No formal [...]&lt;!--%kramer-ref-post%--&gt;</description>
		<content:encoded><![CDATA[<p><a href="http://dev.wp-plugins.org/wiki/Kramer"><img src="/blog/wp-content/plugins/kramer/kramer.php?kramer=gif-icon" class="technorati-balloon" alt="Kramer auto Pingback" style="border:0;" /></a>[&#8230;] questions on how operators handle handset customization - Andreas has your answers.&nbsp; He writes a long and thoughtful piece at Vision Mobile on a new strategy in handset customization ‚Äì Container Projects.&nbsp; No formal [&#8230;]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
