What is our primary use case?
We use Appian for client on-boarding, anything onboard related, really: loading institutional clients, tracking that information in a single reporter, doing the follow-up, creating the plan parables for them, and developing for them.
In my organization, there are about 150 users who are currently using Appian on a daily basis. We use Appian very extensively. Every day, there are more than 100 unique logins to the system.
What is most valuable?
Appian also has very flexible local integration and we have used that extensively to integrate with our Legacy system.
What needs improvement?
The user interface is good, but it's not perfect. They should provide more flexibility so designers can create a more picture-perfect device. There should be more features on mobile UX development as well.
Currently, it's easy to use and It gets the job done, but it's not flexible in regards to creating the mobile application from scratch. You have to play within the framework and the rules of the UX; however, that's something that not many customers like. Customers want a flexible mobile application development platform. I think Appian should make a lot of improvements with respect to their mobile application development by providing more flexibility for designers in order to allow them to create their own UX components and control the display of the data onscreen.
I would like to see more flexibility in terms of the UI. I know that it's not designed to be a big application that allows you to do multiple things, like creating the second year stream of the pie, for example. I feel like Appian has been so instrumental in making their entire product local, and have really improved the user interface design, but the user interface design is limited to authenticated users only — although there are some limited pieces available on the login page. I would like Appian to extend their local capabilities to the login page as well so that we could create an available application that can be targeted to any customer. For example, if you flipped it, you would see information about various products and other information, something that could be very realistic if only Appian would allow these capabilities to be extended to the login page.
For how long have I used the solution?
I have been using Appian for more than 10 years.
What do I think about the stability of the solution?
The stability is good. We have been using Appian for our strategy and tactical solutions and it has held up very well for us. The team was able to adapt to the changes of the new version very quickly and were able to implement the application without any complexities or jumping hurdles relating to development. There were no issues for us. Appian has been meeting just as many of the requirements in my department as the stakeholders have. The stakeholders are happy with the UI and ease of the application. The overall usability has improved and everyone is happy with Appian.
What do I think about the scalability of the solution?
We believe that the scalability of Appian depends on the expertise of the Appian designers. It completely depends on the skill of the designers — how they design the applications determines the scalability of processes and data. In other words, the platform is very scalable. It stores the data as memory so the data allows us to retrieve the information rapidly; but again, we had already done the data management so the team was focused on data retention and data management. They set up their architecture in such a way that the system and the application can be scaled very quickly, so we are not seeing any problems with the scaling of Appian.
How are customer service and technical support?
My team mainly interacts with Appian cloud support who regularly provides them with solutions and advises them about any existing platform issues.
Which solution did I use previously and why did I switch?
We previously looked at the Pega system; actually, one of our departments is currently using Pega system, but we wanted to diversify our technology base to provide a better experience for our stakeholders. My CIO recommended we make an investment because these two platforms are leading BPM tools offering similar functionalities, including BPM, EI, and case management. So we were calculating the pricing, trying to figure out what the return on the investment would be if we went with one platform or the other and what it would cost us in terms of losses between Pega and Appian.
How was the initial setup?
The initial setup was straightforward. The team was able to set it up quickly, build up the applications and deploy it within six to ten weeks.
What about the implementation team?
We have an in-house team that is comprised of Appian architects, designers, consultants and professionals who are trained on the Appian platform.
What other advice do I have?
I would definitely recommend Appian. It has come a long way and it's a good product. It's entering into the area of a local application development platform. Appian is continuously making product updates every quarter.
I would give Appian a rating of nine out of ten.
Which deployment model are you using for this solution?
Which version of this solution are you currently using?