OutSystems Reviews

My company uses OutSystems for developing mobile applications and web applications.

The most valuable feature of the solution is that it is a low-code tool with which it becomes very fast for users to create something and to show the creation to the customer much faster than any other technology.

In OutSystems, cloud management is an area of concern where improvements are required. Searching through the logs is an area with certain shortcomings where improvements are required in OutSystems.

I have been using OutSystems for half a year. My company has a partnership with OutSystems, and we have a lot of certified engineers.

OutSystems has some issues with stability. When OutSystems is used as an enterprise solution or has millions of users, then there are some stability problems with your stability. When millions of users use your application, the management of the databases and caching systems is sometimes not that efficient in OutSystems.

It is a scalable solution.

My company deals with small and medium-sized businesses.

The solution's technical support is good, especially owing to its documentation part. I rate the technical support a ten out of ten.

Positive

The initial setup of OutSystems is easy.

The solution can be deployed in a few hours.

The solution is deployed on the cloud. A user gets access to the user interface and some applications that you can install on Windows, making it a process that one person can do.

OutSystems is an expensive product. My company has to make monthly payments towards the licensing costs attached to the solution. I am unsure about how much my company spends towards the solution's costs, but its cost runs into thousands of euros. There are some additional costs towards which certain payments are to be made, considering that one needs to pay for the end user who uses the solution.

I know about the competitors of OutSystems. I didn't choose any of the competitors of OutSystems since it was a product that already existed in my company.

A person is required to maintain the solution.

If someone needs to show their customers really fast results of the development phase of an application, OutSystems is a very good solution that is expensive at the same time.

I rate the overall tool an eight out of ten.

OutSystems is a versatile development platform that I find incredibly useful for various purposes. It is great for building both web and mobile applications, making it suitable for large enterprises and small to mid-sized businesses across different industries like banking, healthcare, manufacturing, and more. With its visual development, pre-built components, and easy maintenance, OutSystems has significantly expedited software development in my experience, offering a rapid and efficient solution for a wide range of applications.

In comparison to other local development platforms, OutSystems is quite advanced. While every platform can benefit from ongoing enhancements, OutSystems seems to have most of the features I, as a software professional, would look for. I have started working with it, and I find it to be a genuinely cool and effective platform for my development needs.

OutSystems is already on the right track for improvements. They plan to transition from their cloud platform to a cloud-native architecture, emphasizing infrastructure scalability and the integration of Docker containers, which is a positive step forward. I would also like to see OutSystems improve its integration capabilities, especially with emerging technologies like AI and GPT. Integrating with AI and GPT models could enhance OutSystems' functionality and help it easily adapt to new trends and concepts in connectivity and artificial intelligence in future releases.

I have been using OutSystems since 2011.

I would rate the stability of OutSystems as a ten out of ten.

OutSystems supports both horizontal and vertical scaling, and I find it quite easy to scale applications when needed. Adding a front-end server to a cluster, for instance, is a straightforward task that takes just a few minutes. As long as you follow OutSystems' recommended application composition and architecture, scalability is not a problem, and I would rate it a solid ten out of ten for scalability. In our company, around eighteen to nineteen developers are actively using OutSystems to develop applications for our customers. For mid-sized applications with OutSystems, you don't require large teams. OutSystems encourages small teams to use agile methodology. Typically, you need an engagement manager, a tech lead, and two to three developers for a medium-sized project. Additionally, a solution architect may be necessary initially, and then one tech lead and two developers are often sufficient for ongoing work.

I have had a positive experience with OutSystems' tech support. They offer a guided learning path, well-structured documentation, and a valuable component repository called Forge. Their community is also quite active, with fellow users and even OutSystems champions and family members providing assistance. In addition, they have a stable support process where you can create a support ticket, and the OutSystems team will reach out to help with any issues. Overall, I'm satisfied with the support available from OutSystems through their various resources.

Setting up OutSystems is straightforward, and even citizen developers can quickly learn and start building software with it. While complex applications may require professional expertise, OutSystems provides numerous prebuilt components and features, such as UI components for creating beautiful interfaces and easy database design tools, making it accessible even for those without extensive design or development experience. It is also user-friendly when it comes to handling logic, integrating with third-party services, and working with APIs. Overall, I find it to be a great and user-friendly platform for software development. The deployment process in OutSystems involves using a tool called Lifetime, which acts as a control console for managing different environments. When you purchase an OutSystems license, you typically receive three environments: development, QA, and production, along with a separate Lifetime environment. Lifetime keeps track of application versions and modules deployed on servers in each environment. It alerts you when an environment is outdated compared to a new version in development. Lifetime also checks references and other prerequisites before deploying releases from one environment to another, making the deployment process straightforward and well-managed.

OutSystems licenses are not cheap, but they fall within the range of standard pricing. It is not very expensive or overly budget-friendly; it is more in the middle, making it an average-cost option for organizations.

Before using OutSystems, I explored other tools like APN and Automation Anywhere. However, I found OutSystems to be the best fit because it offers both rapid application development and flexibility. Unlike some other tools, OutSystems allows you to integrate with third-party libraries and technologies like .NET, Java, BigQuery, and more, making it a more flexible and easily adaptable platform.

I would definitely recommend OutSystems to others. Overall, I would rate it as a ten out of ten.

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. 

For some of the business processes, we want the process owners to be able to set up their own flow-throughs, process flows, workflows, etc. They don't need to have any kind of prior coding experience. They should be able to establish workflows for their respective processes by just dragging and dropping elements as part of self service without relying on IT (where possible).

OutSystems has really brought about citizen developers in my organization without any real coding experience to be able to develop their own work slows in their area of work.

The flow editor is the most valuable feature. It is simple and intuitive, and it can guide you step-by-step.

From an ecosystem perspective, it has a highly integrated flow editor, user interface, and data logic behind it. It has a very connected local ecosystem.

One of the biggest areas for improvement is that every time an existing data element is modified, it creates a new data element. It doesn't really modify that particular data element. So, a user has to follow an extra step of removing the existing data element and bringing in the new and modified data element that is being added, which sort of goes into negative productivity.

I have been using this solution for about four and a half years.

OutSystems' tech support is very good. They're fairly responsive.

It is one of the good solutions available in the market. I would rate OutSystems an eight out of 10.

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.

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 is easy to use. 

I have been using OutSystems for six months.

OutSystems support is okay. 

Setting up OutSystems is easy. It take one or two hours. 

The price is okay. OutSystems isn't expensive. It's a mid-range solution.

I rate OutSystems nine out of 10. I recommend evaluating it as a POC first. If everything is okay, you can start.

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.