Appian vs OutSystems

• Allows at a glance workflow documentation which assists in the need we have for information readiation.
• Drag and drop interface for workflow development greatly speeds our apps time to market.
• Using the advanced features of Appian, we are able to create working sites in a fraction of the time it would take to do so using "traditional" development.

Read full review

• Developing end user interfaces with ease and speed with a modern look and feel.
• First class low code development to reduce time to market with visual programming
• Their technical support team is fast and responsive. We've yet to have any issues they could not resolve.

Read full review

• Search issues when type ahead and database search are used in the same field.
• Buttons implementation where user is require[d] to click on the button description - if clicks on the button outside that text - button will not work.
• Problems with using certain off-the-shelf performance tools like WebLoad or Neoload. That is because of different dynamic variables being used internally in Appian - which these tools are unable to correlate. We are still investigating using other tools like Jmeter to overcome dynamic correlation problem for performance testing.

Read full review

• Price – The licensing model of OutSystems is very expensive and not suitable for small scale developments. This is offset by the time to develop and stability for larger scale developments
• Flexibility on PaaS version – The PaaS hosted version of OutSystems limits your flexibility to access the front end and backend database systems which can significantly restrict your options on high data volume developments or where anything requiring slightly out of the ordinary access is required
• Same price for PaaS and self-hosted system. Licensing model dictates that you pay the same price even when you host the system on your own hardware which effectively means you pay more to manage the infrastructure yourself

Read full review

• I believe it has negatively impacted our release dates. There may have been a misunderstanding as to the learning curve, even though it is "low code."
• The look and feel of the applications created using Appian have uniformity and it's easier to have "reuse" between applications.
• There is less developer control when it comes to features. I think this mainly has to do with the amount of plugins available. I would think there should be many more available plugins. But again, our use case is probably different than most others.

Read full review

• The ease of use of the OutSystems development process has been the biggest ROI for us. We have developed our Framework product and maintained/enhanced it with only 4 workers.
• OutSystems has enhanced their product very significantly over the last 4 years. They have gone from a simple to use tool to a very simple to use sophisticated tool that covers the standard mainframe-based computing apps and the apps used on handheld mobile devices all using the same basic set of development tools.

Read full review