My Experience with OutSystems
Vitor Cosme | TrustRadius Reviewer
September 18, 2017

My Experience with OutSystems

Score 8 out of 10
Vetted Review
Verified User
Review Source

Overall Satisfaction with OutSystems

At Deloitte, we provide consulting services to other companies and, for some of them, we use OutSystems as our main implementation technology. We have projects that focus [not] only on front ends, but also, projects that use OutSystems functionalities to integrate with core and legacy applications. It is used by several departments inside the organization.
  • The out-of-the-box functionality that processes a SOAP endpoint is very useful.
  • The functionality of using one application as a dependency of others.
  • The low code functionalities.
  • Projects that use native cordova plugins sometimes have lots of conflicts generating native mobile apps.
  • The merging system when working with other developers.
  • The customization system has to be more extendable to other non out-of-the-box features.
  • Due to its RAD features, projects ship earlier.
  • Due to low code, developers can focus on quality and user experience.
  • Our web team does not need to know native mobile languages. They can become expert in web.
Our choice for OutSystems came from previous projects that the company had. Still, when compared to Sitecore, the platform is easier to use, it has a nicer and more friendly visual interface. Also, installing an on-premise version was a lot easier to do with OutSystems than with Sitecore Web Content Management.
In my opinion, OutSystems is a major advantage when integrating with legacy systems inside organizations. Using the 4LC approach and micro services, it kind of gets really easy to work with integration. When customization is the word, OutSystems can be kind of a drawback when "time" is the major word of the project.