User Interface Considerations When Porting
You must perform additional development work to adapt the user interface of a Windows Mobile–based application from Pocket PC to Smartphone and vice versa.
The following table shows some of the differences between the user interface for Windows Mobile-based Pocket PC and the user interface for Smartphone that you must take into consideration.
| User interface element | Windows Mobile-based Pocket PC | Windows Mobile-based Smartphone |
|---|---|---|
| Touch screen | Present | Not present |
| Hardware-based keyboard | Present if the OEM chose to implement a hardware-based keyboard | Present in the form of a number pad.
Some Smartphones have keyboards |
| Softkeys | Present as a menu bar and/or mapped to hardware keys | Present, and mapped to hardware keys |
| Direction input (Direction Pad is one such implementation) | Present | Present |
Consider also the screen size and screen orientation of the Windows Mobile–based device. For more information see Display Considerations When Porting.
For more information on the differences between Windows Mobile-based Pocket PC and Smartphone, see the following MSDN articles:
- Developing Applications for Windows Mobile:FAQ
- Developing for Windows Mobile-based Smartphones: Present and Future
See Also
Creating Portable Applications | Display Considerations When Porting | Porting Samples and References | User Interface Control Guidelines | Design Guidelines
Send Feedback on this topic to the authors