As a Domino developer preparing to mobilize your existing Notes or Domino applications, you have a lot of analysis and planning to do before you can write a single line of code. The decisions you make at the very beginning of a mobilization project can affect the project’s success in many ways. You need to understand whether the target Notes or Domino application is a suitable candidate for mobilization, whether the application can be built using no more than a reasonable amount of effort, and whether the end user community will be happy with the end result (from both a performance and features standpoint).

As I’ve demonstrated in the earlier articles in this series (listed below), there are many options available to Domino developers. Understanding the different approaches to mobilization, the strengths and weaknesses of each approach, and the impact each one has on developers and users is an important aspect of the work at hand. My goal now is to equip you to evaluate your development options and make the best choices for your projects. I’ll do that by detailing some of the development choices and approaches you need to think through before beginning any mobilization project.