My experience with Appian.
Updated August 24, 2017

My experience with Appian.

Leonid Spektor | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User

Overall Satisfaction with Appian

No good support was provided. With such a new and unusual language, and Appian widgets and their limitations and awful training - Appian is the only resource that can provide guidance to new developers. It is not like Java; one can "Google" and find the answers.
[It's being used for] Large scale responsive web design for Ministry of Health sites.
  • Responsive
  • Instant results
  • Interpretive
  • Lack of version control and being different for all modules.
  • Expression Language is a Lisp dialect - that forces functional programming. JavaScript or VB would be easier.
  • Several users working on the same module might create problems. No individual work space.
  • API is not well documented with comprehensive examples.
  • Functions do not work well with large numbers when they should.
  • Training exercises are full of mistakes - that turns training into the worst experience. Training MUST be improved to provide quality good examples, and not guesses what should be there but was missed. How can one learn - if training examples are a trash, while the exams ask questions on topics not covered????
  • Too much documentation. Must be much, much more concise. Who can read and memorize so many pages of Appian "Britannica"???
  • Some errors are captured during editing, while others are not, or show up in a different window????
  • GUI widgets lack numerous hooks to make design more creative. Need access to all widget features. Otherwise developers are limited to "limited" widget behavior.
  • Response in a cloud could be too slow, following data entry. For example, one enters a name and validation takes up to a dozen of seconds.
  • Development environment is not coherent between different objects, some can only be edited using old GUI. A lot remains to be done to make development environment simple , intuitive and coherent.
  • Learning curve it too big because documentation is too spread and voluminous, and training [is] a trash with mistakes and bad examples.
  • Once basic learning is done, a developer can become productive.
  • Overall, impact is positive since it takes the headache of browser compatibility and responsive layouts [away].
Conceptwave BPM that uses JavaScript Rhyno with libraries as its language, and JavaScript makes programming much more intuitive.
Suited well for large scale responsive web design. Its widgets are sufficient but limited when it comes to GUI creativity. So - it is not suited for games design or intensive scientific computing, since its functions fail handling large decimal numbers.

Using Appian

A good start, but difficult to learn and too much documentation, Must become simpler to go into the future and becoming a standard of web development.
ProsCons
Like to use
Easy to use
Technical support not required
Well integrated
Feel confident using
Unnecessarily complex
Inconsistent
Cumbersome
Lots to learn
  • Development
  • GUI design
  • DB mapping (sort of)
  • Db mapping
  • Process modeling using diagramming
  • Searching