The primary use cases are mostly related to the rapid low-code framework. Currently, I'm working on a business use case where we need to create a responsive website that enhances the customer's experience.

OutSystems is a hybrid framework and supports my mobile and web application development needs. This means I don't have to write separate code for mobile applications. It adapts the UI and functionality, whether I'm developing for web or mobile interfaces. All I need to do is provide the layout during development.

The tool has enhanced my development speed through its prebuilt templates and drag-and-drop interface. Unlike legacy frameworks like C# and Java, OutSystems provides everything ready to use. You need to connect integrations and formats, which allows developers to develop their modules rapidly.

In the healthcare sector where I work, we handle clinical and non-clinical research involving study criteria and customer-responsive interfaces.

In one of our recent projects, which involves setting up appointment bookings for healthcare organizations like NHS and Canadian provincial health services, OutSystems plays a crucial role. The system monitors Outlook email criteria every five minutes to detect appointment requests. When a request is identified, OutSystems uses AI capabilities to determine if it's a new booking or a follow-up based on the email content.

Once categorized, the tool integrates with other systems, such as Salesforce.

The tool's weakness is its focus on the solution only. Other than that, it's pretty easy to use for both technical and non-technical people. However, the tool lags in automation. For instance, we've used Python for scraping and other automated tasks. So, I believe automation is an area where it could improve.

I have been working with the product for three and a half years.

OutSystems servers are currently managed directly by the vendor. This setup makes scalability readily achievable because whenever we need to expand our operations to different locations, we can directly engage with the vendor who handles the tool. They can scale the infrastructure to meet our requirements. However, at this point, our focus isn't on scaling further because the configurations we've implemented for recent developments are adequate for targeting the Canadian and North American regions.

Technical support is good, especially for customers on the Gold tier like us. Typically, we receive responses within 24 hours, and their support team is very responsive.

Appian offers advantages in automation structures with its Appian RPA platform, formerly Jidoka. They have integrated this acquisition into their offerings as Appian RPA. Additionally, Appian has a well-established market presence. Appian holds a slight advantage over OutSystems, which entered the market approximately five years ago.

Our primary goal has been to enhance customer experience by deploying applications developed with OutSystems. The initial response from users has been positive, particularly in reducing previous backlogs. We've streamlined processes with the product, enabling rapid development, integration, and automation.

We haven't yet reached the stage of calculating ROI specifics. Typically, such evaluations are conducted either at the end of the fiscal year or three years.

The tool has its own AI modules, but we've utilized our custom models. As we focus on specific regions like Canada and North America, we've developed dedicated forms and solutions. We've implemented our custom models using Python and Gen AI to extract data from emails and forms. OutSystems does offer its own AI capabilities.

Due to its fast development strategies and everything, I would recommend OutSystems over Appian. Appian is in a different space and has its own components and frameworks.

I rate the overall product a seven out of ten.

I am a consultant for another organization. We've been using OutSystems to develop in-house applications and a convention-type application.

The solution is all-encompassing and very easy to use with its drag-and-drop feature. OutSystems has a Forge feature that allows me to drag and use predeveloped components into the platform so that I don't have to develop everything from scratch.

I'd like to see AI features integrated into the solution.

I have been using OutSystems for two years.

We've very rarely encountered an issue with the solution crashing.

I rate the solution’s stability a nine and a half out of ten.

OutSystems is a very scalable solution. We developed an app, and we've had no problem at all with having 200 people at the convention and, in other cases, 1,000 people at the convention. We use the solution daily in our organization.

There have been times when the solution's technical support took a while to respond. This happens mostly because their technical support is not in North America but Portugal.

I also extensively use another product called Apex. It's an excellent product, but it's not the same as OutSystems. With OutSystems, I can develop phone applications. I cannot do that with Apex because it's built more for a back office.

Using OutSystems to develop applications in-house as opposed to using third-party solutions has probably saved our clients a lot of money in the long run. They're not paying the licensing fees over and over again to the other platforms.

The solution's integration is very good. We've integrated the tool into some other SQL areas we have at the client, and it's no problem integrating at all. The solution is deployed on the cloud.

OutSystems is an excellent platform for development and would be an excellent tool for any small, medium, or enterprise business. However, depending on the price, which I don't know, it may be out of range for small and medium businesses.

Overall, I rate the solution a nine out of ten.

We use OutSystems for developing applications that are used by clients in Canada, USA, and Europe. OutSystems has been very effective for us in developing both web and mobile applications. It has reduced our development time by around 30 to 40 percent.

We've used features like batch processing timers, components, and integrations with other systems like SAP, which have accelerated our development process. In terms of productivity, we've seen a 30 percent reduction in screen design time and an additional 10 percent improvement when implementing client requirements. OutSystems' integration capabilities have significantly enhanced our app's functionality, making it quicker and easier to connect with other systems.

While I can't speak to the market impact, as a developer, I've seen significant reductions in development time across different versions of our applications. One area for improvement would be the UI controls in Service Studio. Sometimes, controls don't appear in the IDE, requiring us to check them in the web browser instead. Overall, our experience with OutSystems has been positive, though improvements in UI development would be welcomed.

I've been with OutSystems for about three and a half years now.

On a scale from one to ten, I'd rate the stability of OutSystems at nine.

In terms of scalability, I'd rate it at eight.

OutSystems' technical support has been very helpful and responsive.

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

Deployment with OutSystems has generally been straightforward, although we've encountered some challenges with UI development.

I'm mostly focused on development, but our DevOps and maintenance team consists of about five to six people.

The main benefits we've seen after implementing OutSystems include significant time savings, improved deployment processes, and convenient configuration settings in the service center.

As for licensing costs, I'm not directly involved in that aspect.

Overall, I'd rate OutSystems a nine out of ten.

I use the solution since it is a low-code platform. I am more into the BFSI domain. Most of the projects that have dealt with revolve around the banking sector. I have used the product for web development and mobile applications. My company has worked on a mobile app for a bank's core processes. My company took care of the website part of the bank with the help of OutSystems. My company also operates with other clients who operate in the banking sector. My company has also dealt with the insurance domain and mutual funds.

The product's high price is an area of concern, where improvements are required. OutSystems should play around with the market or with its competitors. A lot of the clients feel that the license cost of OutSystems is way too high than the prices of its competitors.

In the future, I want OutSystems to offer support for which they should not charge any money from users. If a client is new to OutSystems and has taken a license for two or three years, I believe that the solution should provide free support for a year.

I have been using OutSystems for four years.

Stability-wise, I rate the solution an eight or nine out of ten.

When it comes to the scalability part and its impact on our organization's growth, I can say that the development and implementation timelines are minimalistic, which is something that is good. It is pretty easy to implement anything that a specific client wants with the help of OutSystems. It doesn't take years to implement something with OutSystems since such areas can be dealt with quickly.

From migration to adding internal applications is easy with the product. The platform is very adjustable based on the requirements. The customization levels offered by the product are good. It is possible to distribute the loads in OutSystems.

My company deals with around ten customers who use the product.

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

The product's setup is more of a PnP procedure, making it an easy process. I feel that the setup process can be a bit complex at an architectural level.

The solution is deployed on an on-premises model.

The number of people required for the deployment and maintenance of the product depends on the product that is used. If a business entity has multiple business units, it takes a longer time to implement the product. In general, my company has a team of around 15 to 20 people to take care of the implementation process.

The clients who use OutSystems feel that it is a bit expensive.

There is a need to make yearly payments towards the licensing costs attached to OutSystems. It is an expensive product.

I don't see any differences between Java and Clutter or OutSystems since I use different products depending on the requirements of our company's clients. I don't get the clients to choose a particular platform, but my company recommends OutSystems. Not all of our company's clients prefer OutSystems.

The product's scalability is very good. The tool offers easy integration with multiple platforms.

The product's features and speeding up the application development process stem from the fact that the capabilities provided by the tool are not limited. The whole platform, user experience, and implementation time are good.

The interface of OutSystems has impacted our company's development workflow since it is very user-friendly. I rate the product's interface a four out of five.

Though OutSystems is an expensive product. If an organization wants better dynamics when it comes to a particular platform, I would recommend OutSystems to such companies.

In terms of user support and community engagement, I rate the tool a ten out of ten.

The value and positive impact experience from the use of the solution stems from the fact that it works very well when it comes to load balancing. The product is also easily configurable.

I rate the overall tool a nine out of ten.

OutSystems has use cases in the health care, accounting, banking, insurance, and automotive industries.

The most valuable features of OutSystems are the user interface, the flexibility to quickly integrate with almost anything in the system, and the ability to connect with databases.

The solution's testing framework needs to be improved, and the workflow should be slightly more mature. The solution should use generative AI capabilities.

I have been using OutSystems for nine years.

We haven’t faced any issues with the solution’s stability.

OutSystems is a scalable solution. The solution is auto-scalable regarding the number of users or the volume of data.

I have created an application which is being used by almost 2,00,000 users. That was done for some kind of enterprise wide application where it is being used across the globe. That's the maximum number of users I have created an application for.

The solution's technical support is quite useful, but it takes a good amount of time to get a solution from them. The technical support is not so quick and could be faster.

The solution’s initial setup is straightforward.

We implemented the solution through an in-house team. Depending on the size of the application, the solution's deployment hardly takes a few minutes.

With the solution, I have seen around 80% to 90% increase in the return on investment.

OutSystems is a very expensive solution, and it has to be cheaper. Users have to pay a yearly licensing fee for the solution.

I have used the solution for both web and mobile application development. In the healthcare domain, we used the solution to create a mobile application related to patient care. We also used the solution to create web applications, including banking and in-house enterprise applications.

It hardly takes around six resources, including developers, for a typical project which goes for around six months. I would recommend the solution to other users. I rate the solution a nine out of ten for user support and community engagement.

Since I've worked with the solution for nine years, I'm well aware of its visibility. I will promote the solution if the business needs align with what can be achieved with OutSystems.

Overall, I rate OutSystems an eight out of ten.