There are many things I LOVE about Appian, but let's stick to 3 main points shall we?
1.) What's your background? Because it doesn't matter. Welcome to Appian!
I have seen and actually work with many people who did not choose a tech-related major in school or even had a general interest in application development, but with Appian, the learning curve in tangent with its Rapid Development makes it so easy that anyone from any field/background can become an expert & lead designer with this BPM in a year!
2.) Need this application done in a year? You'll have it in 6 months.
With only a few months of experience to account, I can easily tell this BPM's rapid development is by far one of its strongest points!
For example, your company/organization requires an application for external users (customers) to log-in without hassle, fill out an electronic application for capital expenditures & allow both appropriate internal users (Reviewers, Board of Directors, etc.) & any associated applicants to review that application's budget, estimated expenses, and multiple requests that will also keep track of all related historical data throughout that project's duration.
Keep in mind this application needs to be available offline & online and should be mobile-friendly for users that are always on the go; Appian will always be the answer for quick yet perfect solutions.
Because this BPM uses SAIL (Self-Assembling Interface Layer), once your deploy this application, it will be available for use for computer and mobile phones without additional configuration! In addition, you won't have to bother with hundreds of web-links when everything is converged into just 5 tabs - News, Tasks, Record, Reports, and Actions.
3.) My last point will be a quote of my own - "A program is only as strong as its community."
I believe this to be true because this BPM, from what I've gathered from its previous versions, has grown exponentially because of the strong feedback and effort received from its community. There's not a day I have used this BPM where I haven't been able to get an answer about an issue I'm facing at the time if not some leads/hints as to how to go about fixing the issue on my own.
In other words, the community that support and use this BPM are always there to help one another.
Sometimes, I may run into a problem and look at the error log and I'm not really able to ascertain what the problem is because the error information itself is not accurate or the notification is too vague. In which case, you'll have to strip your code line by line (or maybe comment out your code by sections) to find out where the error is occurring.
This dislike does not come up too often, but sometimes, there may be functions that are available for use and are actually very handy, but because there is no official documentation in place, it is frown upon to use them since in regards to best practices, there are not recommended, and if someone has to review your code and is not familiar with the use of that function, there will be an unneeded learning curve, if not blocker, for them to endure.
If you're a customer who may be considering using Appian BPM for your wants and needs, then make sure you have money because unless I'm mistaken, it is not exactly inexpensive.
However, given the rapid development this BPM can provide, it won't require too much time for the job to be finished. Just know and understand what you want from start to finish.
If you're someone who's looking into becoming a BPM Developer, I would say given Appian a try. You don't need previous experience in, well, anything, and after a month or 2, you'll be a developer of your own caliber (just know the ins and outs of best practices and understand why they are the "best).
Currently, the business problems I'm helping solve currently are the following:
1. Significantly cutting down an organization's physical paperwork workload for both their customers and the employees themselves by at least 50%
2. Giving the customer peace of mind by providing a tracking system of any changes (both by date & time) that would prove to be critical/important for future documentation and final decision making purposes.
in other, and fewer words, making the entire organization's (again, both the customers and the employees) life much easier.