Comments on: Motorola, the Recession, Android, what about MIDP3, and the potential for good things to come http://weblog.cenriqueortiz.com/mobility/2008/10/30/motorola-the-recession-android-and-the-potential-for-good-things-to-come/ Thoughts on Mobile Software, Development & Technologies Thu, 11 Mar 2010 15:47:43 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Vicky http://weblog.cenriqueortiz.com/mobility/2008/10/30/motorola-the-recession-android-and-the-potential-for-good-things-to-come/comment-page-1/#comment-8310 Vicky Thu, 18 Dec 2008 23:34:15 +0000 http://weblog.cenriqueortiz.com/?p=1083#comment-8310 That’s actually what a company I saw at CTIA last Sept is trying to do with their mobile/embedded platform Voyager (runs symbian, CF, and I think android)- problem is, when do you stop integrating platforms (since I doubt Android or any other will be dominant any time soon)? they’ll always be yet another "next best" one released. After talking with people who know people who know people at Mot, they don’t think a universal pform can happen. They’ve been slow to jump on the android train- They'd be smart to drop symbian first to try and cut into Nokia. That’s actually what a company I saw at CTIA last Sept is trying to do with their mobile/embedded platform Voyager (runs symbian, CF, and I think android)- problem is, when do you stop integrating platforms (since I doubt Android or any other will be dominant any time soon)? they’ll always be yet another “next best” one released. After talking with people who know people who know people at Mot, they don’t think a universal pform can happen. They’ve been slow to jump on the android train- They’d be smart to drop symbian first to try and cut into Nokia.

]]> By: Sean Sheedy http://weblog.cenriqueortiz.com/mobility/2008/10/30/motorola-the-recession-android-and-the-potential-for-good-things-to-come/comment-page-1/#comment-7736 Sean Sheedy Mon, 03 Nov 2008 23:46:40 +0000 http://weblog.cenriqueortiz.com/?p=1083#comment-7736 One thing about the MIDP/CLDC stack that we forget about is that there is a lot of expertise in creating implementations that run on just about every phone platform in existence. So, these new platforms are simply a port away from running a MIDP/CLDC stack. I think that there is a really strong argument for having an execution environment whose existence can be counted on across a wide array of devices. Of course that means that addressing the issues that currently make application portability between devices a challenge should be given a very high priority. One thing about the MIDP/CLDC stack that we forget about is that there is a lot of expertise in creating implementations that run on just about every phone platform in existence. So, these new platforms are simply a port away from running a MIDP/CLDC stack. I think that there is a really strong argument for having an execution environment whose existence can be counted on across a wide array of devices. Of course that means that addressing the issues that currently make application portability between devices a challenge should be given a very high priority.

]]> By: Sean Sheedy http://weblog.cenriqueortiz.com/mobility/2008/10/30/motorola-the-recession-android-and-the-potential-for-good-things-to-come/comment-page-1/#comment-7735 Sean Sheedy Mon, 03 Nov 2008 20:40:52 +0000 http://weblog.cenriqueortiz.com/?p=1083#comment-7735 On the future of MIDP3, it is a requirement in MSA 2.0: (Section 6.2, MSA 2.0 EDR): JSR 271 defines the Mobile Information Device Profile version 3.0 (MIDP 3.0). JSR 271 is a mandatory component in all MSA 2.0 Subset and MSA 2.0 full implementations. Now, JSR-249 was originally going to be the definition of a CDC-based handset platform, while 248 was the CLDC platform. This leads to questions like, why was JSR-249 "downgraded" to being an evolution of 248? What handsets will be targets for MSA 2.0 in late 2009? As far as ME's role as a mobile application platform (excluding other embedded uses), is there a will within the other companies in the ME EC to protect their investment in ME by assuming a stewardship role and working together to create an answer to these new platforms, or have they put ME in maintenance mode to pursue their own proprietary answers or hitch up to another bandwagon? On the future of MIDP3, it is a requirement in MSA 2.0:

(Section 6.2, MSA 2.0 EDR): JSR 271 defines the Mobile Information Device Profile version 3.0 (MIDP 3.0). JSR 271 is a mandatory component in all MSA 2.0 Subset and MSA 2.0 full implementations.

Now, JSR-249 was originally going to be the definition of a CDC-based handset platform, while 248 was the CLDC platform.

This leads to questions like, why was JSR-249 “downgraded” to being an evolution of 248? What handsets will be targets for MSA 2.0 in late 2009? As far as ME’s role as a mobile application platform (excluding other embedded uses), is there a will within the other companies in the ME EC to protect their investment in ME by assuming a stewardship role and working together to create an answer to these new platforms, or have they put ME in maintenance mode to pursue their own proprietary answers or hitch up to another bandwagon?

]]> By: McGuire’s Law » Blog Archive » Business Observations: November 2, 2008 Edition http://weblog.cenriqueortiz.com/mobility/2008/10/30/motorola-the-recession-android-and-the-potential-for-good-things-to-come/comment-page-1/#comment-7693 McGuire’s Law » Blog Archive » Business Observations: November 2, 2008 Edition Sun, 02 Nov 2008 14:15:57 +0000 http://weblog.cenriqueortiz.com/?p=1083#comment-7693 [...] Motorola, the Recession, Android, what about MIDP3, and the potential for good things to come [...] [...] Motorola, the Recession, Android, what about MIDP3, and the potential for good things to come [...]

]]>