The growing incidence of smartphones enables customers to access applications originally designed to be run in a desktop computer’s web browser. These new devices offer user interfaces unlike those found in personal computers, because of the different design.
The smart phone variants of popular internet applications are freely accessible to the users. These variants are usually developed long after the web variant was finished. The rational of their existence is that web-based applications usually can not be directly used on the smart phones. First, this is because the design and user interaction facilities of smart phones (e.g. on touch screens the optimal density and size of widgets is special), on the other hand browsers found in smart phones do not offer the same functionalities as those of desktop computers. This is a challange for developers, because developing a smart phone variant of the original application with the same functionality is resource demanding. Often the whole application has to be rewritten from scratch.
The aim of current project is to ease and simplify the above process. The initial platform constraint was to base the development on Google Web toolkit (GWT) for desktop, and on Android for smart phones. The common programming language of both platforms is Java. This offers the opportunity to share code segments between the two different platform variants of the application. I show what design and development patterns and considerations can be applied to achive the above goals, how the application can be modelled, what practices are to be followed in order to have the least difference between the source-code of the two configurations.