OutSystems Reviews

OutSystems excels with building web interfaces fast and lends itself to custom integrations written in .Net. Most anything can be brought in given this ability to be extended. One of the drawbacks to the speed of development is that most quality control teams become quickly overwhelmed and may be unable to keep up.

It allows you to develop an app from scratch in a matter of weeks/months, maintaining the required stability and allowing you to focus on companies' further needs instead of spending all your time in the developing stage.

The development of the user interface is possible without a complete backend. Informing business users on how it will work can be done before the complex logic is developed. It gives us a faster ability to discuss the business process.

OutSystems works great when you have little time and a lot to be done. OutSystems has a great community and has a lot of things already done in the Forge, so you don't have to implement everything yourself.

OutSystems is suitable for any web application, reactive or not, or even numerous mobile applications. Solutions can be obtained in a shorter time frame.

I think where I can say that it might be less appropriate, will be in mobile applications where you want very different things, with many effects being intruded. In OutSystems it turns out to be possible, but I think in these cases it is better to develop a native application. But be aware, today with OutSystems, you can develop great, and better, mobile applications.

We started to use it to work out POC, then by supporting our entire business processes, and we will start replacing legacy systems (starting with small bits and bites). From my point of view, the complete system is well supported. OutSystems isn't the only system for creating and building POC. Therefore, comparatively, it is too expensive.

The first thing to be mentioned is that you must be aware of the costs and know that you can afford it. While the alternatives to get the same outcome might be more expensive, OutSystems should fit the budget in order to maximize gains. It is well suited for companies which desire to innovate fast and are willing to invest (effort, money) in it.

OutSystems is great for quick learning and easy implementation. It is not great for extensive and intrinsically difficult applications.

OutSystems is well suited for most application types where it does not have to interact with a legacy system that does not have API integration. OutSystems is extremely responsive however is not the best in the world for mass data manipulation.

I think OutSystems is the ideal program to use when you want to work in a lean and agile way (and who doesn't want that?). OutSystems is easy to learn, flexible and highly intuitive. Even without any former IT experience, I was able to build and develop quality features for our new "client following system" within a few months, thanks to OutSystems being low-code.

I think it's appropriate in most places. Really, at this moment, I don't see where OutSystems it's going wrong. Have the scenarios trusted and the controls for one environment more secure. For our part, OutSystems is well suited for the best performance of our users, clients and people that interact with the system.

OutSystems is often promoted as being a system without limits. I admit, that I have had difficulty finding things that this platform cannot do. It is well suited for both big and small organizations with limited IT staff. OutSystems handles integrations well. The platform also accommodates tying in AI elements for both speech and video into your applications. You can save binary objects directly into the database, create complex workflows hiding most of the typical complexity from the citizen developer, easily create multi-lingual aware applications, and connect to external systems via API calls. They also offer on-premise and Saas solutions.

OutSystems is well suited in mobile and web application development and delivery and increasing delivery cadence. It is less suited as a solution for API management and integrations.

I guess you can just read the marketing literature & Gartner Magic Quadrant papers because they deliver on:

1. Speed to Market
2. Retiring Legacy Products

I think in a real-time and embedded environment it is not appropriate to use OutSystems. For starting with mobile apps it is highly appropriate because it is so easy to get your first app.

For me personally it is the best system I ever worked with and also the OutSystems roadmap is filling our needs.

OutSystems is well suited for the quick development of medium to complex applications, as well as the quick transfer of knowledge of developers from other programming languages.

In our case, we had a fairly big backlog of smaller projects that kept on being ignored because there not being any time and or budget left for them. Thanks to OutSystems we can now finalize these projects within our timelines and budget.

OutSystems has the ability to adapt to business customer needs on the fly. Rapid prototyping has allowed our business partners to receive a product that actually fulfills all of their business requirements.

It works well with a wide range of applications, it depends on the expertise of the developer.

Not sure at this time.

Outsystems is well suited for database-driven applications and client-facing apps that are required to handle a lot of data. Especially ones that require rapid development. Outsystems is well suited for database-driven applications and client-facing apps that are required to handle a lot of data. Especially ones that require rapid development.

OutSystems is suited for any situation as long as the strategy is well thought of. The necessary sponsors within the company also all need to be convinced and aligned. It is very difficult to move forward if the entire team is not convinced by the solution that is being implemented, and the necessary freedom needs to be given to see the whole platform's potential.

This rapid application development platform works great for building applications from scratch. The build of a new application is really easy and very easy to set up. Within minutes you have your application running and deployed to your users.
Less suited for rebuilding an entire application. This was our greatest mistake. Never rebuild. Build something next to it.