Hi,

You can check that comparison in here:

https://success.outsystems.com/documentation/11/getting_started/choose_the_right_app_for_your_project/

You have there a good detail about the differences and what each of them can do or do not:

you can take a look at this too. It's about Reactive vs PWAs but have a good context too:

https://medium.com/@techrug/are-outsystems-reactive-web-apps-the-same-as-progressive-web-apps-6260426555d6

The advantage of each one of them...Depends of the use case.

Hope this documentation can help you decide.

Best regards,

Ricardo Pereira

Hi Lucas,

Please check the below link:
https://success.outsystems.com/documentation/11/getting_started/choose_the_right_app_for_your_project/

https://www.outsystems.com/blog/posts/all-you-need-to-know-about-reactive-web/#web-development-future

Regards
Krishnanand Pathak
 

Hey!

You can find the differences in the guided path. Also, attaching a image which can make you understand in a better way.

Hi everyone!

Lucas' question was more about the column in blue vs RWA.

	Reactive Web App	Mobile App	OS "Mobile" App when used on desktop (by using the link and without setting as PWA)
Code Reusability	Common logic for all devices and screen sizes.	Common logic for all supported native mobile platforms, and supported browsers for PWAs.	Common logic for all devices and screen sizes.
Runs in	A browser. No installation is needed.	Native mobile apps run in Android and iOS devices. PWAs run in any device with a supported browser.	A browser. No installation is needed.
User Experience	Responsive layout for all screen sizes and types.	Dedicated mobile UI patterns and experiences.	Dedicated mobile UI patterns and experiences. Unless an explicit effort is done to support different screens sizes (specially large sizes).
Performance	Performance designed for the client side, with smart mechanisms to optimize the data transfer.	Performance designed for the client side, with smart mechanisms to optimize the data transfer.	Performance designed for the client side, with smart mechanisms to optimize the data transfer.
Access to device hardware	HTML5 supported device capabilities.	Native mobile apps access a range of device capabilities through Cordova plugins. PWAs use dedicated plugins, which by design can access only hardware that the browser running the PWA is allowed to access.	HTML5 supported device capabilities.
Offline capabilities	No offline capabilities.	For storing offline data, native mobile apps use local storage and PWAs use browser storage.	Yes. It uses the browser storage.
Deployment and updates	Updates are automatic when users refresh the browser page.	Native mobile apps can update automatically, and users need to install a new version only when you change the native shell. PWAs update automatically when the app detects a new version.	Updates are automatic when users refresh the browser page.
Distribution	Share the app link with users.	You can distribute native mobile apps in-house or through the app stores. Users can run a PWA directly from your website, and add the app icon to the device home screen.	Share the app link with users.

I have filled in each capability of the blue column based on my understanding of how it works. However, I acknowledge that there may be additional nuances or factors that I haven't considered, and I would like to get your opinion.

Given that the last column appears to have equivalent capabilities as RWA, is there a compelling reason to choose RWA over a mobile app that can be designed with optional offline capabilities and sensor usage? 

Regards,

Ricardo

Yes indeed it would be helpul