OutSystems

OutSystems it's an amazing platform, that allows the development of amazing application. It's community is very helpful and in the forums one's problem can be solved very fast by peers. Integrations with other systems are a great plus also.

The OutSystems Platform is well suited for: Applications with forms and process flows. Reporting and dashboard applications. Web Site without content management.

Well suited for organization transformation, moving from old legacy systems into quick and agile action movers.
All topics that can be developed, like simple workflows or action triggers, are well suited to use OutSystems.
A few examples include invoice financial approvals, meetings action trackers, automatic escalations flows, email automation triggers, operational process simplification for day to day tasks, etc.

Well suited for internal exposure of business processes (invoicing, API layer to other systems, customer maintenance etc), whether a UI is required or not.
Not so well suited for full fledged web design. An OutSystems application must serve one particular business need, if gets too much functionalities and responsibilities it tends to get chaotic and complex.

It fits all business cases that you encounter, it might too expensive for very small businesses.

[It's well suited] To big companies, that need quick results. It is good if you need to have your team of programmers without needing a lot of time to learn the app. It's easy to learn and very intuitive. I don't think it suits the needs of small companies with low capital power due to its price.

OutSystems is well-suited for high-performance scenarios, or high graphic performance scenarios. It is always recommended to use native language.

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.

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.

The applications are really process-based, and that will help the business to focus on what really matters.

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.

OutSystems is well suited for small isolated experiences in our landscape. Connecting to legacy data sources is a struggle for big companies.

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.

it's well suited to use in agile scrum way of working easy to deploy and quick way to see effect of your work

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 when you want to deliver a product fast and don't have a full-blown budget for a very big development team, and when you want to see/release fast results.

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 very well suited to bespoke workflows that the business is expanding into or even legacy, but then you have the typical barriers to change.

OutSystems is a perfect tool when you are new to development and want to start learning development. They have very nice programs online which you can use to start learning for free. How awesome is that? Besides that, they have a very good and active community online as well as very good documentation.

OutSystems is very well suited for the quick development of applications.

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