Welcome to MSDN Blogs Sign in | Join | Help

ToddHa's WebLog

Musings, notions, thoughts about technology and software.

News

  • Disclaimer
    The information in this weblog is provided "AS IS" with no warranties, and confers no rights. This weblog does not represent the thoughts, intentions, plans or strategies of my employer. It is solely my opinion. Inappropriate comments will be deleted at the authors discretion. All code samples are provided "AS IS" without warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.
Windows Mobile App Feedback

This is a question for those of you who write Windows Mobile applications (preferably managed, but native is fine too). We're developing a managed Windows Mobile application, and one of the issues we've run into is that we'd like to support both Smartphones and Pocket PCs (or WM6 Standard and WM6 professional devices, respectively).

My first WM application was a Sudoku game I wrote that worked fine on both Smartphones and PocketPCs, but it was in my spare time. I didn't handle things like text input (A-Z, a-z, symbols, etc), localization, and Pocket PC input panels. I also wrote all of my own controls (of which there was exactly 1). I also didn't get code coverage numbers (a new post on that later this week).

Unfortunately, there are some differences that make it hard to have one binary running on both. For example, we resize appropriately when the InputPanel control on the PocketPC is shown, but obviously, it's not required on the Smartphone. Another common problem we have is setting keyboard shortcuts. We want to make sure the application experience is great, regardless of whether you're on T-9 device or have a full fledged keyboard with touch screen.

My current thought is have mostly the same source, but reinvent certain controls like the StatusBar and ComboBox so that they work and are accessible on both platforms. Then I'll have one primary project and have two outputs : one for Smartphone (with a custom set of #defines), and one for PocketPC (with its own set of #defines).

So my question is:

What do others do, and what do you recommend?

I'm looking for both advice and personal experiences while developing a WM app.

Thanks!

Edit: To be clear, my plan is to have one primary project targeting the PPC, and one "ghost" project which targets Smartphone. All of the "ghost" project's files will actually be links to the primary project's files.

Posted: Monday, October 22, 2007 8:28 PM by toddha

Comments

Kevin Daly said:

I'd say the key is to have good separation between UI and business logic (Model View Presenter could be a good fit here) and don't try to shoehorn the UI into a common pattern for Smartphone and Pocket PC, because that risks giving you a very anaemic experience for the latter. The differences go beyond the characteristic of a given control and extend to what's a good layout, what features should be present, how people should interact with the device  and so on.

# October 22, 2007 4:27 PM
Anonymous comments are disabled
Page view tracker