Hi Tony,

Kindly Refer to this link for the latest release of the Reactive web.

https://www.outsystems.com/blog/posts/reactive-web-applications/

Hi Tony, 

You mentioned that you have reviewed some the blogs, but I found this post to be very informative

https://www.outsystems.com/forums/discussion/52761/reactive-web-the-next-generation-of-web-apps/

My opinion is that reactive we will greatly improve the user experience. It seems as if the reactive web apps leverage a bunch of Javascript modules built by Outsystems in order to create a mobile like experience through the web browser (not entirely achievable with traditional web apps). 

 I would use reactive web when user experience is critical for your application (which in my case is almost all of the time). I see reactive web apps almost entirely replacing traditional web apps for our purposes. 

Data is also returned on demand, adding to the user experience. 

Perhaps traditional web apps will be more applicable when you have to cater for different web browsers and their various versions. 

This would be my opinion. 

Thanks, 

Nicholas

Yea so far I have reviewed https://www.outsystems.com/blog/posts/reactive-web-applications/ and https://www.outsystems.com/forums/discussion/52761/reactive-web-the-next-generation-of-web-apps/

but still confused when to use reactive or tradtional.

Hi Tony,

I work at OutSystems R&D. Reactive apps are recent, and we plan to continue evolving documentation regarding the differences between modules very soon. Regarding the decision I would:

• Use reactive for all new applications
• Use traditional to continue existing apps, or apps that require very specific features (e.g. support for older IE browsers)

Cheers,
Tiago Simões