Is it time to subscribe to a printer service from HP?

Ever since my dad brought home an...

What’s the best way of buying a phone today?

How did you buy your latest phone?...

MWC: What device highlights did you miss?

So, early last week I predicted that...

Converting an application from Symbian to Windows Mobile

Daniel caught me the other day. He’s a mobile developer working on some nifty communications services aimed at Ethiopians throughout the world.

He’s got some chaps to create a Symbian S40/S60 version of the service he’s aiming to launch — and is wondering how difficult it will be to convert the application to work on other platforms (e.g. Sony Ericsson).

What’s your view?

6 COMMENTS

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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.

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Recently Published

Is it time to subscribe to a printer service from HP?

Ever since my dad brought home an HP LaserJet printer (version 3, if memory serves), I have been printing with an HP. Over the...

What’s the best way of buying a phone today?

How did you buy your latest phone? I'm asking because I'm thinking about what I should be doing. When I was living in Oman, I...

MWC: What device highlights did you miss?

So, early last week I predicted that next to nothing from Mobile World Congress would break through into the mainstream media. I was right,...

How Wireless Will Pave the Path to Neobank Profitability

I'm delighted to bring you an opinion piece from Rafa Plantier at Gigs.com. I think it's particularly relevant given the recent eSIM news from...

An end of an era: Vodafone UK turns off 3G services

I thought it was worthwhile highlighting this one from the Vodafone UK team. For so long - for what feels like years, seeing the...

Mobile World Congress: Did the mainstream media notice?

I resolved this year to make sure I wrote something - anything - about Mobile World Congress, the huge mobile industry trade show taking...