Appian Reviews

SAIL (Self-Assembling Interface Layer), a scripting language provided by Appian. It is the equivalent of JS and CSS. It allows creation of complex UIs which are also responsive. With SAIL, we have a single language for both the UI logic and its appearance. UI components can be built as reusable components and used in multiple UI interfaces.

Process Modeling enables creation of business process workflows. You can create complex business workflows in a visual manner, and it is also easy to debug/monitor.

Offline capabilities and responsive capabilities could be better. The mobility features of Appian platform are still evolving.

Native mobile capabilities or hybrid mobile app capabilities are very limited. Things like offline sync, offline storage, access to smartphone device features, etc. are not supported by the Appian platform yet.

Excellent.

It is Java based, can be deployed in JBoss or WebSphere container.

I would rate it eight out of 10. It certainly is the best for enterprise application development.

Our primary use for this solution is Business Process Automation.  Appian is good for enterprise process automation as well as general purpose low code development.

Since implementing, we have had a faster time to solution, with fewer resources needed per project compared to other tools.

The most valuable features of Appian are the Low Code, robust Process Design, Run-time Management, Deployment, Interfaces, and Mobility.  The business rules capability are advanced and the integration capabilities are second to none.  We also find security to be more robust than pretty much all other application platforms we've worked with in the past.

We've used a good number of Business Process Automation tools in the past and none of them have given the value for money we are seeing with Appian.  Appian enables us spend the least time designing beautiful and robust interfaces that automatically render in Web browsers and native mobile apps securely without any additional effort.  With very little learning curve, an Appian designer will start designing very complex and dynamic interfaces that consume data from everywhere.

We would however like to have more granular control for interface styling in future releases.  Appian releases updates to the platform every quarter.

It reduces development time in half making us more efficient.

• It is fast and efficient.
• Mobile

All enterprises focus on these features in their work.

• Apps development
• BPM

It would be nice if you could create your own customized apps when the business needed them.

No issues.

No issues.

I would rate technical support as an eight out of 10.

I previously used .NET Framework. I switched because I think Appian is better for enterprise.

Appian is easy to set up, but JBoss is complex. JBoss is the application server for running Appian.

There are two solutions depending on your situation: an on-premise solution and a cloud solution.

Oracle BPM. Appian was better.

It is more efficient and reduces time. There is no need to worry about vulnerabilities in the system, because Appian built a secure system.

I am working with all of these products: Pega, Appian, and OutSystems. I use Appian as a process orchestrator for workflow and rule-based routing, and it is preferred when I am developing an enterprise-wide application. The application is mobile-friendly, allowing me to use it across any device, whether mobile, laptop, or desktop.

It is easy for me to define the process and create configurable workflows. Additionally, they have provided inbuilt integration points and services, which facilitates integration with external services.

If there is a very complex process that includes a lot of data transitioning and memory-centric processes, it consumes a lot of memory. For those use cases, Appian needs to optimize memory utilization. AI-related features should also be more integrated.

I have been in this ecosystem for quite some time. For Pega, it is 20 years, and for Appian, it is more than ten years.

I would rate the stability as eight out of ten. As a product, there are no issues. It depends on how it has been designed and how it has been configured.

Appian is scalable in its architecture.

Their customer service is responsive, and the team is very prompt for support. The response depends on the kind of partnership vendors have and their relationship with them. For step one issues, which impact most of the business on that workflow, I get quick support from the Appian team.

Positive

Whenever there is a production deployment, it involves the Appian development team. However, if other systems are also involved, representatives from the integration teams of different systems are needed as well.

There are two buckets. On the pricier side, both Appian and Pega are enterprise-level solutions, placing them on the slightly higher side. 

However, the robustness of the products, their features, and their availability justify the pricing.

I have considered Appian, Pega, Uncorp, and Mendix as alternate solutions.

Overall, everything is eight out of ten. 

I am a little bit biased towards Pega. Pega has a lot more standardized processes, which take less time to go to market compared to Appian. Appian provides a platform.