OutSystems Reviews

Customer track and trace. We get information from SAP which is updated later by carriers (via EDI). The user interface is built in OutSystems.

Development timeframe and deliveries on sprints. Customers can check the progress on a weekly basis and provide adjustments and comments right away.

Agile development. I love that you save a lot of time on development and can focus on logic and business requirements.

Mobile apps need improvement.

No issues with stability.

No issues with scalability.

Technical support is a 10 out of 10.

We did not have a previous solution. We started the department using OutSystems with the goal of creating applications for our internal customers (departments and warehouse customers) to help their main businesses.

Setup was straightforward. I was not there at that time, but I know that it was very smooth. The developer at the time was trained by OutSystems and this helped with the first applications.

It is still very expensive, so small companies can’t generally afford it. We hope that this changes. Still, the time saving on development and delivery is worth the value.

Agile development is really worth it. Depending on the size of your department – and requirements – you don’t need a big development team. The same developer can take care of all steps: analysis, development, implementation, support.

I am using OutSystems in internal workflow processes for approving expenses.

The solution has helped us, but it's no longer a strategic choice for us. We are not investing anymore in this platform. We realized the value of using OutSystems if you have an internal development capability. We've been using the solution mostly in outsourcing for development tasks, and it doesn't make much sense to us, to pay the amount for the solution for the capital gains to go to the external provider we use for the development.

If I have a large team of developers, eventually using the solution would make sense. That's not the case. In my business model for IT, I do not have any internal development capability. I'd rather do it without a rapid development platform because the savings go to the provider. It doesn't go to me. I have to pay for the ticket and then I have to pay additional costs for the development. It doesn't make any sense. It is a good solution and technology, it only does not fit our use case.

The most valuable feature of OutSystems with discipline and the development processes. Instead of each developer doing tasks on their own with their own approach, et cetera, the solution would help bring some organization to the development process. 

I have been using OutSystems for approximately five years.

We did not experience a time when the solution did not perform, the solution is stable.

I rate the stability of OutSystems an eight out of ten.

The solution can scale. However, the catch is the pricing has become more and more expensive in the last few years. Consumption is increasing, and the price has increased a lot.

We have approximately 200 users using this solution in my company.

The support is not provided by OutSystems themselves. It's the service vendors, the integrators. There is a shortage of skilled workers that are knowledgeable of the tweaks of the platform and the shortcuts that can increase the productivity of using it.

We are using ServiceNow and it's depicted as a container for OutSystems. It's not the same, but it has the capability of doing some type of rapid development, and we are using it more and more.

The largest obstacle currently associated with OutSystems is its high cost and limited availability of skilled personnel. Despite being a rapid application development platform, having a highly skilled individual familiar with the platform can be much more beneficial than an inexperienced individual. Because there is a shortage of people with the necessary OutSystems skills, utilizing the platform can become expensive. This makes little sense, considering that a rapid application development platform should be accessible to the average person. However, having a highly skilled individual can greatly increase productivity, making the cost worthwhile.

I rate the initial setup of OutSystems a four out of ten.

I have not seen a return on investment using OutSystems.

OutSystems is expensive, and they changed the pricing model in the last couple of years.  It's changing too much and it's becoming unstable. They are constantly shifting their prices based on users, courses, and other factors.

To ensure that we will be able to benefit from leveraging internal development capability, I would suggest using a tool, such as OutSystems. With this solution, it is possible to increase the average productivity of the existing team of developers. Even a small increase of two to three percent can lead to significant gains. However, if there is a limited number of developers, it may be difficult to realize substantial productivity gains from using OutSystems.

I rate OutSystems a seven out of ten.

We use it to help our clients generate certificates. They needed an app to help them record and have data. It allows them to take the certificate number, check if it is authentic and if the equipment that the ticket number is issued against is working perfectly.

The drag-and-drop feature is very valuable.

The tutorials for the solution should be updated.

We have been using this solution for about a month and are currently using version 11.

The solution is stable and doesn't require many server resources, so I don't think there are stability issues. They have enterprise and have been around for a long time. Some of the tutorials we use were created in 2014, and we still use them.

The initial setup was straightforward. Once we registered, we installed it and were able to start work immediately. It took approximately 24 hours to set up.

I rate the solution an eight out of ten. The solution is good but can be improved by updating the tutorials available. I advise people considering the product to ensure they have their data somewhere to generate a certificate. Additionally, I advise them to do their own research. The application makes life easier.

Our use case is mainly for the manual control systems.

There are about 20 developers using this solution in my company.

The scratch coding is useful. The solution is easy to understand.

React is very easy to use for an experienced software developer.

It's difficult to do the component version control. I would like them to add more studying materials.

I have been using this solution for about six months.

Some systems have over 1,000 end users. It's very stable for heavy duty operation.

It's scalable.

Technical support is good.

For one developer to use, the cost is around $5,000.

I would rate this solution 8 out of 10.

We use OutSystems for our customers in the banking and utility sectors. 

OutSystems is a low-code solution. Most features are drag-and-drop, so it's pretty easy to work with. It thus helps the organization by saving time for developers. 

The OutSystems Accelerator is the most valuable feature. 

There are very few resources available to learn OutSystems. If someone is utterly new to OutSystems and is trying to understand this technology by searching on platforms like YouTube, Udemy and Coursera, they won't find anything. It has negligible resources. 

In the next release of OutSystems, I would like to see a few more customizations in the front end. 

I have been using it for four months. 

I would rate the stability an eight out of ten. 

I would rate the scalability a nine out of ten.  

I would rate the technical support nine out of ten. 

Previously I was working on high-code solutions. Then I started using OutSystems low-code solution. 

The initial setup was straightforward. I would rate the ease of setup a ten out of ten. 

I would rate the pricing a five out of ten. There are no additional costs with the standard license. 

I would advise anyone wanting to use OutSystems to start learning early while pursuing a college degree. 

We are a team of ten Software Developers who use OutSystems in my company. We plan to increase the usage of OutSystems in the future. I would rate the overall product an eight out of ten. 

My engagement with the solution was primarily as a private contractor for our banks. We were doing several RPA developments for banks. So they had some processes whereby they wanted to use a low-code approach. They wanted to create workflows out of that. That's what I was focusing on.

Their drag-and-drop functionality is amazing. Their visual layout designers tend to be way better than the ones that I've seen - even compared to something as simple to use as Power Apps.

It's easy to set up the solution.

The product is mostly stable. 

One of the things that they could do a little better is the performance speed of the UI refresh. It sometimes seems a little choppy, depending on what sort of machine power we have. I have a moderately powered machine, and I still found that the reload of the UI was not the most accurate, and I would have to reload the same page a couple of times to get the reflection of the right information. 

It's frustrating in that if you forget to refresh, you're showing somebody the wrong thing, and your bosses aren't happy with you.

The documentation needs to be more robust.

Their UI reach refresh rates could be perhaps better. There's a lot of heavy focus on the client being able to create, to refresh quickly. I don't know what that mechanism looks like for them. 

The integrations that have been created for automated testing, et cetera, should be a big area of improvement for them. If they could think about creating better integrations or opening up the integration space to get more hooks into more automated testing frameworks and platforms, it would be a nice little addition to their whole arsenal.

OutSystems has an opinionated approach to how it will save the data in the back and how it will create application architecture. So they have components, and they have the ability to break things into smaller pieces, however, if I was ever to try and take the system that OutSystems created and try and replicate and take that code base, for example, and put it into a .NET IDE, it doesn't work. Ever. That was sort of a bummer for me.

One of the things that I keep hearing from people is, "We are going to use low-code applications of platforms to create a very basic proof of concept," and that is where their inclusions end. However, to use that proof of concept of complex work, we need to go back to the Javas, and the .NETs, and the C++ of the world. The ability to get that code over and make it work in these different IDEs was not well thought through.

I've used the solution for a year and a half. 

Except for the issues around screen refreshes, its stability is okay. It's fine. It's comparable to PowerApps.  

I've also used Microsoft PowerApps.

Clients were also using UiPath.

The initial setup was straightforward, however, initially getting my feet wet, and kicking it off, can be difficult. The documentation at that moment in time was lacking. It was a very basic, here's how you do a hello world kind of thing, and everything else that followed those instructions were based on the same simple idea. If they could just start making the documentation a bit more realistic with real-world situations, they'll definitely be helping their clients a lot.

There isn't a lot of maintenance needed. There only needs to be one person maintaining the product.

My advice would be more for OutSystems. They need to make documentation foolproof. They need to make it easy enough for anyone to read and get it up and running. From OutSystems's point of view, they would prefer not to have people struggle for installations, so they should make it really super quick. 

I'd rate the solution seven out of ten.

OutSystems could improve by being more like GitHub. It would be more helpful for us for division management and version control for our application.

I have been using OutSystems for approximately five years.

The scalability of OutSystems is very good, it scales automatically very useful for us.

We are satisfied with the support but it could be better. We are the product provider and sometimes we contact the support for our customers and we have to escalate our issue most of the time for the correct answer.

I rate the support from OutSystems a four out of five.

I would recommend this solution to others.

I rate OutSystems a nine out of ten.

The tool makes the development process easier. 

I have difficulty in using several new features. Some of the product's features are tricky to use as well. 

I have been working with the product for six months. 

I would rate the solution's stability an eight out of ten. 

I would rate the product's scalability a nine out of ten. My company has around 20 people for the product. We use the product daily. 

The product's setup is easy. One person is enough to handle its deployment. 

The product is expensive and I would rate its pricing a seven out of ten. You need to pay a yearly subscription to use the product. 

I would rate the product a nine out of ten.