All options are equally commendable, but our system is notably budget-friendly. As a result, many customers are now making the switch to our platform. There are three key reasons behind this shift: our user-friendly interface, the stability of our solution, and its competitive pricing.

I have experience with high-code platforms like Java and Clutter.

We are using almost all the local solutions, including OutSystems, Mendix, Appian, etc.

This is the first time we are using a no-code solution end-to-end.

I've also used Microsoft PowerApps.

Clients were also using UiPath.

Before OutSystems, I mainly worked with .NET and Android development.

We have used some local platforms before.

I have experience with Mendix, PowerApps, and Power Automate. The UI and UX of OutSystems are better than Mendix. The UI of OutSystems is easy to understand.

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

We did not use another low-code platform before, although many of the traditional development technologies were widely tested (Java, .NET/C#, OpenEdge, etc.). OutSystems was the first which provided a complete, easy, and effective platform.

Before that, I used a server platform called Forti. It is similar to the OutSystems Platform. We were able to use mobile and web publications and able to create using that.

I worked on an AD platform as well. 

Comparatively, I'm able to see OutSystems is very easy to maintain and easily fulfills the business requirements. 

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.

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.

We do use another similar product which isn't very well-known. It's a product from Germany and we use it mainly for internal use in the same way that we use OutSystems.

Comparatively, as a low-code kind of platform, OutSystems is the most intuitive to use, but if you have an experienced programmer in Java and .NET like myself, then the other platform is probably a bit more flexible.

We previously used Darknet but switched to OutSystems because it offered some more tools and features.

We use ServiceNow for CMDB and ITSM related needs; we don't use ServiceNow for application development, so for us, the two aren't comparable. I don't have any experience with SericveNow's capabilities in that space. 

We were using traditional development tools like Java/.NET but the overall development time was longer compared to Outsystems. Also, our previous solution had other overheads such as release management, version management, code management, monitoring, etc., all of which are built-in with OutSystems.