Comments on: Converting an application from Symbian to Windows Mobile http://www.mobileindustryreview.com/2008/10/converting_and_application_from_symbian_to_windows_mobile.html Daily news and opinion for 250,000 industry executives and mobile fanatics Wed, 15 Feb 2012 15:14:00 +0100 hourly 1 http://wordpress.org/?v=3.3.1 By: Tom Godber http://www.mobileindustryreview.com/2008/10/converting_and_application_from_symbian_to_windows_mobile.html/comment-page-1#comment-244765 Tom Godber Tue, 14 Oct 2008 17:47:59 +0000 http://www.mobileindustryreview.com/?p=10211#comment-244765 Would rather depend on what development platform he used...<br><br>If the app really works on S40, then it must be Java and so should be relatively portable, especially to Sony-Ericsson. If it is actually Symbian (and so not able to run on S40), he's in trouble - basically it would need a ground up rewrite.<br><br>Most Windows Mobile devices do have JVMs these days, but there are about five different JVMs in active use and the integration into the OS isn't great. For a budget port Java is easiest, but for proper integration you need to code natively. Windows Mobile is still a very small percentage of shipped devices so it's worth checking how big the market is before attempting that. Would rather depend on what development platform he used…

If the app really works on S40, then it must be Java and so should be relatively portable, especially to Sony-Ericsson. If it is actually Symbian (and so not able to run on S40), he's in trouble – basically it would need a ground up rewrite.

Most Windows Mobile devices do have JVMs these days, but there are about five different JVMs in active use and the integration into the OS isn't great. For a budget port Java is easiest, but for proper integration you need to code natively. Windows Mobile is still a very small percentage of shipped devices so it's worth checking how big the market is before attempting that.

]]> By: Ariz M. Kohli http://www.mobileindustryreview.com/2008/10/converting_and_application_from_symbian_to_windows_mobile.html/comment-page-1#comment-244764 Ariz M. Kohli Tue, 14 Oct 2008 17:19:33 +0000 http://www.mobileindustryreview.com/?p=10211#comment-244764 If there is a Java app (which there may very well be since you say S40) it can be ported on to many other modern Java enabled devices. Some fairly easily and some may take a little more effort.<br><br>If there's a native Symbian S60 application it can be ported on to the native Symbian UIQ Sony Ericsson devices and many other devices running UIQ (Motorola?). The UI would need changing in addition to very minor changes to utilise UIQ specific APIs.<br><br>Porting to Windows Mobile may or may not be easy, depending on how well the original application is coded and how the different parts of the application are decoupled. But it will definitely be a lot more work that porting to UIQ. If there is a Java app (which there may very well be since you say S40) it can be ported on to many other modern Java enabled devices. Some fairly easily and some may take a little more effort.

If there's a native Symbian S60 application it can be ported on to the native Symbian UIQ Sony Ericsson devices and many other devices running UIQ (Motorola?). The UI would need changing in addition to very minor changes to utilise UIQ specific APIs.

Porting to Windows Mobile may or may not be easy, depending on how well the original application is coded and how the different parts of the application are decoupled. But it will definitely be a lot more work that porting to UIQ.

]]> By: Tom Godber http://www.mobileindustryreview.com/2008/10/converting_and_application_from_symbian_to_windows_mobile.html/comment-page-1#comment-233034 Tom Godber Tue, 14 Oct 2008 12:47:59 +0000 http://www.mobileindustryreview.com/?p=10211#comment-233034 Would rather depend on what development platform he used...<br><br>If the app really works on S40, then it must be Java and so should be relatively portable, especially to Sony-Ericsson. If it is actually Symbian (and so not able to run on S40), he's in trouble - basically it would need a ground up rewrite.<br><br>Most Windows Mobile devices do have JVMs these days, but there are about five different JVMs in active use and the integration into the OS isn't great. For a budget port Java is easiest, but for proper integration you need to code natively. Windows Mobile is still a very small percentage of shipped devices so it's worth checking how big the market is before attempting that. Would rather depend on what development platform he used…

If the app really works on S40, then it must be Java and so should be relatively portable, especially to Sony-Ericsson. If it is actually Symbian (and so not able to run on S40), he's in trouble – basically it would need a ground up rewrite.

Most Windows Mobile devices do have JVMs these days, but there are about five different JVMs in active use and the integration into the OS isn't great. For a budget port Java is easiest, but for proper integration you need to code natively. Windows Mobile is still a very small percentage of shipped devices so it's worth checking how big the market is before attempting that.

]]> By: Ariz M. Kohli http://www.mobileindustryreview.com/2008/10/converting_and_application_from_symbian_to_windows_mobile.html/comment-page-1#comment-233033 Ariz M. Kohli Tue, 14 Oct 2008 12:19:33 +0000 http://www.mobileindustryreview.com/?p=10211#comment-233033 If there is a Java app (which there may very well be since you say S40) it can be ported on to many other modern Java enabled devices. Some fairly easily and some may take a little more effort.<br><br>If there's a native Symbian S60 application it can be ported on to the native Symbian UIQ Sony Ericsson devices and many other devices running UIQ (Motorola?). The UI would need changing in addition to very minor changes to utilise UIQ specific APIs.<br><br>Porting to Windows Mobile may or may not be easy, depending on how well the original application is coded and how the different parts of the application are decoupled. But it will definitely be a lot more work that porting to UIQ. If there is a Java app (which there may very well be since you say S40) it can be ported on to many other modern Java enabled devices. Some fairly easily and some may take a little more effort.

If there's a native Symbian S60 application it can be ported on to the native Symbian UIQ Sony Ericsson devices and many other devices running UIQ (Motorola?). The UI would need changing in addition to very minor changes to utilise UIQ specific APIs.

Porting to Windows Mobile may or may not be easy, depending on how well the original application is coded and how the different parts of the application are decoupled. But it will definitely be a lot more work that porting to UIQ.

]]> By: Tom Godber http://www.mobileindustryreview.com/2008/10/converting_and_application_from_symbian_to_windows_mobile.html/comment-page-1#comment-230221 Tom Godber Tue, 14 Oct 2008 11:47:59 +0000 http://www.mobileindustryreview.com/?p=10211#comment-230221 Would rather depend on what development platform he used...<br><br>If the app really works on S40, then it must be Java and so should be relatively portable, especially to Sony-Ericsson. If it is actually Symbian (and so not able to run on S40), he's in trouble - basically it would need a ground up rewrite.<br><br>Most Windows Mobile devices do have JVMs these days, but there are about five different JVMs in active use and the integration into the OS isn't great. For a budget port Java is easiest, but for proper integration you need to code natively. Windows Mobile is still a very small percentage of shipped devices so it's worth checking how big the market is before attempting that. Would rather depend on what development platform he used…

If the app really works on S40, then it must be Java and so should be relatively portable, especially to Sony-Ericsson. If it is actually Symbian (and so not able to run on S40), he's in trouble – basically it would need a ground up rewrite.

Most Windows Mobile devices do have JVMs these days, but there are about five different JVMs in active use and the integration into the OS isn't great. For a budget port Java is easiest, but for proper integration you need to code natively. Windows Mobile is still a very small percentage of shipped devices so it's worth checking how big the market is before attempting that.

]]> By: Ariz M. Kohli http://www.mobileindustryreview.com/2008/10/converting_and_application_from_symbian_to_windows_mobile.html/comment-page-1#comment-230220 Ariz M. Kohli Tue, 14 Oct 2008 11:19:33 +0000 http://www.mobileindustryreview.com/?p=10211#comment-230220 If there is a Java app (which there may very well be since you say S40) it can be ported on to many other modern Java enabled devices. Some fairly easily and some may take a little more effort.<br><br>If there's a native Symbian S60 application it can be ported on to the native Symbian UIQ Sony Ericsson devices and many other devices running UIQ (Motorola?). The UI would need changing in addition to very minor changes to utilise UIQ specific APIs.<br><br>Porting to Windows Mobile may or may not be easy, depending on how well the original application is coded and how the different parts of the application are decoupled. But it will definitely be a lot more work that porting to UIQ. If there is a Java app (which there may very well be since you say S40) it can be ported on to many other modern Java enabled devices. Some fairly easily and some may take a little more effort.

If there's a native Symbian S60 application it can be ported on to the native Symbian UIQ Sony Ericsson devices and many other devices running UIQ (Motorola?). The UI would need changing in addition to very minor changes to utilise UIQ specific APIs.

Porting to Windows Mobile may or may not be easy, depending on how well the original application is coded and how the different parts of the application are decoupled. But it will definitely be a lot more work that porting to UIQ.

]]>