Skip to main content

 

Introduction into migrating Traditional Web to Reactive Web Apps

 

OutSystems

Introduction into migrating Traditional Web to Reactive Web Apps

This document is a work in progress and we invite you to send us your feedback.

This document is intended for experienced developers and leads as guidance in migrating Traditional Web Apps to Reactive Web Apps. The migration requires good knowledge of the new front-end features and knowledge of the application architecture. Check our training Becoming a Reactive Web Developer for an introduction.

In October 2019, we released Reactive Web, enabling our developers to create the next generation of Web Apps. Due to significant changes to the Reactive App, we do not provide a tool for automatic migration of the Traditional Web Apps.

The migration process is manual. The effort might be significant, depending on the size and complexity of the applications, particularly in the front end. If your apps are supported by a solid architecture, you can reuse a lot of server-side logic and speed up the migration.

Migration, for the most part, implies creating new UI with the new framework, and then creating logic using new development paradigm. In the process, you may rethink and improve your user experience, especially if your app has an outdated look and feel.

The developers already familiar with the Mobile App will find in the Reactive App many concepts they already know, do to the similarities in the development tools. The developers who develop primarily in the older Traditional Web App technology may need to learn more about Mobile App, Reactive Web App, and the client-side development paradigm.

Effort estimation and team requirements

To estimate how long your project can take, start by a proof of concept and migrate simple Screens, and then move to more complex Screens. The effort you invest should be a good indication of how fast your team is able to migrate the app to the new runtime.

Consider also using a gradual release strategy where you migrate only some Screens or sets of Screens and deploy them side by side with the old Screens. In the process, you should test how the Screens work on devices with different display sizes.

Before initiating a migration project, make sure that:

  • There is a real value in migration. For example, that active development is planned for the app, there is a need to reuse elements between Mobile and Web apps, the improvements in end-user experience justify the investment, and similar.
  • Your team has experience and training in building Reactive Apps or Mobile Apps. Reactive Web App is built on top of modern client-side logic that is powered by a well-designed server side. The development team should be familiar with both. If you are not confident that the team is ready for the task, we advise working with partners or developers that are experienced in the migration projects.
  • Was this article helpful?