I have used it for a company in Saudi Arabia. The application was mainly focused on transportation. The other application is a recent upgrade.

I love OutSystems because, as a manager and someone who has experience with various traditional development technologies (approximately 20 technologies), it provides a standard approach. Unlike other companies where there is no development standard, with OutSystems, we have our own standard. This makes it easier when transitioning between developers or onboarding new team members.

It's not easy to master OutSystems within the first month. Even if you have ten years of experience, like me, it will take about two to three months to explore everything. For example, customizing a header or integrating a video is not easy.

Many people assume that mastering OutSystems is as simple as drag and drop, but for specific tasks, you need someone with development experience, preferably a senior or expert with over five years of experience.

Sometimes it requires both skills, someone who knows how to develop and add script code or extensions to our system. However, there are also times when it is easy. Let's say around seventy percent of the time; it's easy. Customizing the user interface, aside from the header, is relatively straightforward, although I did encounter difficulties with the header.

Another example is working with live video, which is also not easy.

I have been using OutSystems for one year.

It is very stable. I would rate the stability a nine out of ten.

The scalability of OutSystems is not bad. I know someone who conducted a scalability test. They used SCC Solutions, a telecom company with a great team of developers. They encountered some issues compared to what OutSystems claimed. However, I believe you always need to have a package that can handle more users than OutSystems recommends.

If they suggest an eight-gigahertz processor, you should go for a better specification. But overall, it's not a major problem. Just make sure to exceed the recommended specifications. OutSystems is widely used in many regions. It's extensively utilized in the UK and Australia, as I have experience working with these countries. However, in some countries, traffic and other factors can make it more challenging.

I did contact the customer service and support team, but they mostly provide general IT support.

I believe there is room for improvement in technical support. However, they are good and responsible in terms of providing documentation and guidance to help you.

I believe you would need someone who is already good in development or has a logical understanding of development. OutSystems has four layers: the timers and processes layer, the interface layer, the version layer, and the database layer.

Sometimes, when you add a module from the first layer, it doesn't work because it needs to be compatible and supported by the OutSystems platform. Many components or modules from the first layer are often incomplete or non-functional when compared to the later layers.

Therefore, you need to comprehend the logic and then integrate it. It's not always straightforward. There are challenges involved.

If you don't have someone who is already skilled in development, most of the time, you won't succeed. I believe you need a certain level of intelligence to excel in OutSystems. You have to be intelligent, like in development.

I've brought in many developers who weren't skilled in development and put them in our system. They excelled at all the traditional tasks but when I asked for any custom work, it took them around one month to finish.

The deployment process is very easy. It involves just one publish button. They call it the "one publish" button.

In our system, there are always many challenges in development. For example, you don't need an administrator or a developer because we have something called architecture AI. It can evaluate your application and determine if it follows the best practices or not. We already have a baseline of good practice cases or standards for our system, so we're not far from the best practices. There are certain things you can't do directly, like calling a server action. Instead, you need to use client actions.

There are many perspectives like this that you need to consider. Otherwise, it won't work. For example, you can't simply drag and drop a client action inside a server action.

I believe anyone would require about two to three months of training, and they would need to build their own application. The issue in our system is that sometimes developers are only skilled in either logic or UI. I think it's important to train people to be proficient in all aspects.

There is an annual cost of approximately 23k. So sometimes, you need to wait for a return on investment. It also requires skilled individuals who know how to utilize this technology and train others. Finding good developers isn't easy because most of the people who work with OutSystems come from Big Data or have multiple engineering backgrounds. We face difficulties in finding the right people, and I think this is a common issue across platforms. Nonetheless, I consider it a unique feature.

Overall, I would rate the solution an eight out of ten. I still believe in our system, despite some limitations in traditional development. There is always room for improvement.

I think they are constantly making progress and adding new features. However, sometimes it's not easy to achieve customizations.

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.

We have been actively following the below strategy for our application development:

• Core applications and systems (SaaS-based external products)
• Bespoke Applications (using Microsoft Azure and Dotnet Application development technologies and tools)
• Quick turnaround applications for web and mobile (Outsystems)
• Portal knowledge and corporate portals (WordPress, SharePoint, DocuWare)
• Cloud Platform (Azure and AWS)
• Support within two hours on the community portal
• Access to native functionalities (camera, geolocation, QR code reader, and access to file systems, address book, and device calendar)
• Supports custom branding
• Supports custom plugins
• Silk UI response framework
• Big focus on performance
• Best practice for CSS and JS
• Tested on several modern browsers and devices
• Support and community (52000+ members, 500+ projects, and two-hour response time)

The OutSystems platform has improved the quick turnaround for application development and deployment.

It provides for faster development and better software releases.

The solution helps reduce costs and gives us an efficient budget.

The ease of management is great.

The product has good reliability and has improved business continuity with increased resilience.

We have a lot of choices through open-source standards.

The product gives us better customer experiences.

There is access to native functionalities (including the camera, geolocation, QR code reader, and access file systems, address books, and device calendars).

It supports custom branding and custom plugins and has a Silk UI Response Framework.

There is a big focus on performance.

The product has best practices for CSS and JS.

It has been tested on several modern browsers and devices.

There is support and a good community (52000+ members across 500+ projects and a two-hour response time).

Below are the solution's most valuable features:

• Device support (Android 4.0+, iOS 7+, Windows 8.1+)
• Access to native functionalities (camera, geolocation, QR code reader, access to file systems, address books, and device calendars)
• Custom branding
• Custom plugins
• Silk UI Response Framework
• Performance
• Best practices for CSS and JS
• Tested on several modern browsers and devices
• Great support and strong community (52000+ members, 500+ projects, and a two-hour response time)
• Online developer training
• Integration Studio
• Service Studio
• Service Center
• Deployment services
• Faster development and better software releases
• Reduce costs/improves budget
• Ease of management
• Reliability/improved business continuity with resilience
• Choice through open-source standards
• Better customer experiences

Areas of improvement include:

• Offering workflow solutions
• Adding event-driven architecture
• Usage of PWA, Responsive, and SPA architecture for front-ends.
• Better documentation and deployment tools. The packaging features need to be standardized using DevOps.
  
• Vertical Tabs (there is a Vertical Tabs problem: Entities.Orientation)
• Data Grid improvements and UI improvements
• There are performance issues in table data using React
• They need to make improvements in various UI assets.
• There should be automation of logs
• We have performance issues while fetching bulk data
• Need integration with core systems and integration with Outlook email

This is a no-code platform solution. We have been using this for the past five years. We've used it for building solutions for web applications and mobile applications. There is a quick turnaround for applications that need to be implemented and deployed for business.

The solution offers good stability.

There are good scalability options. However, scalability can improve.

The solution offers excellent customer support and responses can be expected within two hours from the community forum to help with resolution.

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

The initial setup is straightforward. The process is good enough and elaborate documentation and help in community forums can help the process.

This was an in-house implementation from the development team.

ROI and TCO are great.

With the pressure to deliver new customer and employee digital experiences and having to adjust existing enterprise systems to cope with the market changes, 75% of app development would use low-code platforms. Outsystems has the highest ROI.

The setup cost, pricing, and licensing costs are competitive.

We have not evaluated any other options.