In front of this challenge, many questions arise : what target technology to choose? What budget estimate? What possible hope? What are the risks?

• MyDraft, your passport to the rich Web

KarmicSoft's approach offers a secure migration path to your existing applications (Client/Server, Web 1.0, etc) by addressing your constraints on risks, budgets, deadlines, flexibility, quality and regulatory compliance. Far from making a clean sweep of the glorious past, we first extract the DNA of the existing app in a semi-automatic way, we offer workshops for real-time prototyping to clarify the new perimeter without gaps or inconsistencies and we formulate proposals to meet your goals.

• Kind of migration

a. Migrating an existing Client/Server application.
The ergonomics and productivity for end users are adapted to the massive input of persistent data. However, the economic environment will require endless changes in an accelerated pace. Pins productivity of client-server development still refer, with a RAD tool that made the success of the first versions. Nevertheless, the historical complexity of the code has reached the limit of maintainability, making changes more and more risky. In addition, the "fat client" technology is threatened by obsolescence, as well as technical skills and development for these technologies are becoming increasingly rare on the market. Finally, remote access has become a must, but the ergonomics of the "web 1.0" and responsiveness of the development are not at stake. Especially since the estimate of migration for specific development on modern web platforms are prohibitive...

b. Migrating a desktop application
You have applications running on desktop computers or laptops, but you would like to make it truly collaborative, other than by sending files by email. The use remains heavily manual which exposes the result to handling errors. The formulas developed with great care are stable, but scaling up your application would take it at many risks. It is time to change, but at what cost, how soon and at what level of risk?

c. Migrating a web 1.0 application
The web experience has validated the need for universal access, but the ergonomics, productivity, use, quality and scalability show long term limitations. In addition, mobile computing is of interest. Every click loads a new page in your browser, updating data requires form-based handling, you have to fill several pages before sending data while you are expecting massive input. In short, the rich web tempt you, but transition seems risky.

• Goals summary

In a nutshell, you want to :
• go to the rich web for remote, local and mobile data access, without sacrificing usability or productivity
• have to endure reasonable and under control development delays and costs
• start a new era and easily benefit from continuous technological and functional changes, because the business requires a strong responsiveness to change

More (still under translation) to come soon ;-)