Developing for smartphones in the way the industry is currently doing is relatively new. Of course, there has been enterprise-level mobile development for several decades. The platforms have changed, however. Think of:  from stylus-input to touch-input (different screen res, different control layout etc.)  new ways of handling multi-tasking on mobile platforms (e.g. WP7's tombstoning)The way these platforms work aren't totally new (iPhone has been around for quite awhile now for example), but at the moment when developing a functionally equal application for both desktop and smartphone it comes down to developing two applications from ground up.Especially with the birth of Windows Phone with the .NET-platform on board and using Silverlight as UI-language, it's becoming appealing to promote the re-use of (parts of the UI). Still, it's fairly obvious that the needs of an application on a smartphone (or tablet) are very different compared to the needs of a desktop application. An (almost) one-on-one conversion will therefore be impossible.My question: are there best practices, pitfalls etc. documented about developing  cross-device applications (for example, developing an app for both the desktop and the smartphone/tablet)? I've been looking at weblogs, scientific papers and more for a week or so, but what I've found so far is only about migratory interfaces.
Are there any best practices on cross-device development?
gui;user interface;windows phone 7
What you are talking about is essentially building a family of products that use a common code base. I disagree with premise that you would have to re-write a large part of the code base for different platforms. Sure there are going to be platform specific areas, but by in large this shouldn't affect the common code base. The basic premise or practice that provides the most usefully insight into cross platform development is the concept of design for change. At a most fundamental level, you need to identify what areas are likely to change and/or areas that you know are going to change. In your case, I can identify four areas that fall into this category. User InterfaceHardware InterfaceOperating system Interface Varying Feature SetsThe first three are definitely platform dependent. The forth one in my opinion is more of a configuration thing, but it is still important from a design perspective.  The first three are pretty easily isolated by abstracting each interface behind a common interface. For example, you should have an abstraction layer for operating system services such as semaphore control. The interface should be the same from the common codes point of view regardless of the operating system that you are using. Essentially, the idea is to create virtual interfaces.  Honestly, this pretty much defines the Adapter design pattern. I realize that you are not looking for design patterns specifically, but often times design patterns solve many of the challenges involved in designing a product for multiple platforms because they specific support the notion of design for change.  To tackle the concept of varying feature sets it is important design features that have low coupling with other elements in the system. For example, in a word document, the save option should not depend on the fact that the open file feature is enabled. You should aim to make disabling features as easy as stubbing out the interface. At this point building with a specific set of features should largely be part of your build configuration. Based on what product you are building you can decide weather or not to include a given feature or a stubbed interface. This just one possible solution. I am sure that there are other ways to do this, but concept is the same.        