I’m currently porting an app that was written for Windows Mobile 2003 (compact framework 1.0) and I’ve decided that my lowest denominator is going to be a smartphone running windows mobile 5. I’ve successfully got it compiling and running under VS2008 on “Professional” device but there is going to be a significant challenge to getting it working on a smartphone.
The problem I have as I need to replace TabControls, RadioButtons, buttons, and so on. I was wondering if there was any clever ways of doing this to cut down on the manual grunt work. Or at least some best practices for doing it.
There’s no easy way of converting a normal Windows Mobile app to Smartphone, since (as you’ve noted) the smartphone addition doesn’t have any clickable controls. I wrote one smartphone app a few years ago, and did almost everything with the two menus.
If I were you, I would get rid of the idea of making smartphone the lowest common denominator. I don’t think there are very many phones out in the world anymore running the smartphone edition (I don’t know of any personally, but there might be a few old ones still). If you go with the normal edition of Windows Mobile 5 and .Net Compact Framework 2.0, there’s every likelihood that your application would work with Mono, which means it would work on the iPhone in addition to any WinMo 5+ device.