Comments on: Container projects: The next chapter in handset customisation http://www.visionmobile.com/blog/2007/06/container-projects-the-next-chapter-in-handset-customisation/ Distilling market noise into market sense. Tue, 09 Mar 2010 09:11:11 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Andreas Constantinou http://www.visionmobile.com/blog/2007/06/container-projects-the-next-chapter-in-handset-customisation/comment-page-1/#comment-6203 Andreas Constantinou Mon, 02 Jul 2007 16:50:53 +0000 http://visionmobile.com/blog/2007/06/container-projects-the-next-chapter-in-handset-customisation/#comment-6203 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 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

]]> By: jcj http://www.visionmobile.com/blog/2007/06/container-projects-the-next-chapter-in-handset-customisation/comment-page-1/#comment-6010 jcj Fri, 29 Jun 2007 12:34:58 +0000 http://visionmobile.com/blog/2007/06/container-projects-the-next-chapter-in-handset-customisation/#comment-6010 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? 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?

]]> By: Andreas Constantinou http://www.visionmobile.com/blog/2007/06/container-projects-the-next-chapter-in-handset-customisation/comment-page-1/#comment-5654 Andreas Constantinou Thu, 21 Jun 2007 16:03:53 +0000 http://visionmobile.com/blog/2007/06/container-projects-the-next-chapter-in-handset-customisation/#comment-5654 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 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

]]> By: Guy A. http://www.visionmobile.com/blog/2007/06/container-projects-the-next-chapter-in-handset-customisation/comment-page-1/#comment-5652 Guy A. Thu, 21 Jun 2007 15:12:17 +0000 http://visionmobile.com/blog/2007/06/container-projects-the-next-chapter-in-handset-customisation/#comment-5652 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? 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?

]]> By: Mobile Point View by Paul Ruppert http://www.visionmobile.com/blog/2007/06/container-projects-the-next-chapter-in-handset-customisation/comment-page-1/#comment-4652 Mobile Point View by Paul Ruppert Thu, 01 Jan 1970 00:00:00 +0000 http://visionmobile.com/blog/2007/06/container-projects-the-next-chapter-in-handset-customisation/#comment-4652 <!--%kramer-pre%-->comprised of visonaries and actionaries in the Mobile Space. Soon, I hope to be contributor to this great body of work. This week's carnival has a plethora of posts covering the phantom Google phone, a great FAQ list on Mobile Ajax,a ditty on handset customization (wouldn't that be personalization given the intimacy of mobile handsets?), a proper English written (as opposed to techno-speak) on mobile widgets, OSGi Mobile and it's place in the mobile Java development environment (way beyond my technical<!--%kramer-post%-->

comprised of visonaries and actionaries in the Mobile Space. Soon, I hope to be contributor to this great body of work. This week’s carnival has a plethora of posts covering the phantom Google phone, a great FAQ list on Mobile Ajax,a ditty on handset customization (wouldn’t that be personalization given the intimacy of mobile handsets?), a proper English written (as opposed to techno-speak) on mobile widgets, OSGi Mobile and it’s place in the mobile Java development environment (way beyond my technical

]]> By: Mobile Analyst Watch http://www.visionmobile.com/blog/2007/06/container-projects-the-next-chapter-in-handset-customisation/comment-page-1/#comment-4530 Mobile Analyst Watch Thu, 01 Jan 1970 00:00:00 +0000 http://visionmobile.com/blog/2007/06/container-projects-the-next-chapter-in-handset-customisation/#comment-4530 <!--%kramer-pre%-->VisionMobile about Container projects: The next chapter in handset customisationRoger Entner at IAG about Hearing Voices in my HeadBena Roberts at BKI Media about Virgin Mobile teams up with Infospace for Mobile Search<!--%kramer-post%-->

VisionMobile about Container projects: The next chapter in handset customisationRoger Entner at IAG about Hearing Voices in my HeadBena Roberts at BKI Media about Virgin Mobile teams up with Infospace for Mobile Search

]]> By: VisionMobile Forum http://www.visionmobile.com/blog/2007/06/container-projects-the-next-chapter-in-handset-customisation/comment-page-1/#comment-29224 VisionMobile Forum Thu, 01 Jan 1970 00:00:00 +0000 http://visionmobile.com/blog/2007/06/container-projects-the-next-chapter-in-handset-customisation/#comment-29224 <!--%kramer-pre%-->Rethinking application environments (March 07) - The significance of Google's Android (November 07) - Prague or Berlin? Behind the scenes of the SIM industry (April 07) Theme: Mobile operator strategies: -Container projects: The next chapter in handset customisation(June 07) - Motorola's UIQ: Diversion or U-Turn? (October 07) Theme: OEM strategies - The headaches of being a handset OEM (April 07) Theme: Service delivery technologies - On-device portals: Sardines in a can<!--%kramer-post%-->

Rethinking application environments (March 07) – The significance of Google’s Android (November 07) – Prague or Berlin? Behind the scenes of the SIM industry (April 07) Theme: Mobile operator strategies: -Container projects: The next chapter in handset customisation(June 07) – Motorola’s UIQ: Diversion or U-Turn? (October 07) Theme: OEM strategies – The headaches of being a handset OEM (April 07) Theme: Service delivery technologies – On-device portals: Sardines in a can

]]>