Appian is a low-code development and business process management platform. It features drag-and-drop design for app building, automated work processes, unified data management, and cloud-based deployment.
$0
Kissflow
Score 8.1 out of 10
Enterprise companies (1,001+ employees)
Kissflow is a low-code platform for custom application development tailored to business operations. Kissflow empowers process owners and IT developers to automate and build processes and applications for internal business operations.
$1,500
per month 50 Users
Visual Studio
Score 8.8 out of 10
N/A
Visual Studio (now in the 2022 edition) is a 64-bit IDE that makes it easier to work with bigger projects and complex workloads, boasting a fluid and responsive experience for users. The IDE features IntelliCode, its automatic code completion tools that understand code context and that can complete up to a whole line at once to drive accurate and confident coding.
$45
per month
Pricing
Appian
Kissflow
Microsoft Visual Studio
Editions & Modules
Appian Community Edition
$0
Application - Input-Only
$2
per month per user
Application - Infrequent
$9
per month per user
Application - Standard
$75
per month per user
Platform
Custom Quote Priced per user with unlimited apps.
minimum 100 users, no maximum
Unlimited
Custom Quote Priced per development with unlimited apps.
unlimited
Platform
Custom Quote Priced per user with unlimited apps.
Minimum 100, no maximum
Unlimited
Custom Quote Priced per development with unlimited apps.
Appian works great for automating manual processes and integrating multiple systems through its toolset. It gives great flexibility for establishing rules for approvals, routings, escalations, and the like. Because of the low code toolset, it's very easy to deploy and make changes as needed as processes evolve and as the organization learns to utilize the system better. Minimal maintenance is required to support the applications build on the platform. Some of the automated testing integration with tools like Jenkins is limited so that may be an issue for some.
We've used Kissflow [School Cloud] in order to track parent requests for transportation in the SpEd department. It has been user friendly for parents to input a request and staff to review, double check school sites and locations, and set up specific routes to meet the needs of students and communicate the info back to parents.
When working with base C# code for desktop and web projects, then Microsoft Visual Studio is ideal as it provides the libraries and interfaces needed to quickly create, test and deploy solutions. It is when slightly more complex scenarios are required that issues can arise. The built-in integration for things like PowerBI Paginated Reports and dashboards is far from ideal.
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.
They know what they are. You aren't going to get a Workflow program that also wants to be a CRM. You will get the equivalent of an electronic assistant going from station to station, taking care of business and giving you the end result.
Paper. It reduces the amount of paper needed for menial tasks tremendously. You can automate an entire process. As an educational institution, you may still need paper copies, but you aren't waiting for John Doe to sign Line 3, then Jane Doe to initial, and so on and so on with a paper form.
Tracking. If you need to know where things are in the process, the fact that this program is dedicated to workflow makes it incredibly easy to identify where people are in the sales flow.
Customer appreciation. When your workflow is stronger, faster, and better, the customers feel it. They feel like you are right there with them and getting things moving.
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.
Workflow Design: There isn't a copy/paste function when creating the workflow, and you can't move a workflow task between parallel branches. This becomes a pain point when an item has 98% of what you need, but you can't copy it and place it in another branch to make the last tweaks. Instead, it needs to be completely recreated
Interface: While I like the current design features, which make it easy for an end-user to find their tasks and items, it would be nice to also have some flexibility within the platform. Things like being able to groups apps under a category or tailoring the look and feel of the page a little more would be a welcome addition.
We recently renewed our license with Appian. We are convinced that its flexibility, relative ease of use, the support they provide, there mobile advancements and their general willingness and desire to see us succeed all contributed to our reason to renew our agreement with Appian
VS is the best and is required for building Microsoft applications. The quality and usefulness of the product far out-weight the licensing costs associated with it.
Appian is a low code environment, because of this, a very good visual interface is required. Appian is providing a feature-rich dashboard [that] we can use for building the dashboards and other interfaces. Appian also provides patches and releases to enhance these features. A developer can start off development just by going through a basic course from the Appian learning community.
The system has room to grow as it's limited by not being able to edit POs after they've been approved. The system is great for registrations and syncing to other systems while including the attachments. The reporting from Kissflow is also easy to setup to link to other platforms such as Looker
I love the overall usability of Microsoft Visual Studio. I’ve been using this IDE for more than 20 years, and I’ve seen it evolve by leaps and bounds. Today, with AI and code-suggestion/completion features, developers no longer need to remember countless libraries, methods, or language syntax, or invest a huge amount of programming effort to complete a project. It truly offers everything a developer needs to program, debug, test, and deploy in a single IDE.
Appian is one of the leading low code business automation platforms that support RPA, decision rules, case management, workflow automation, and machine learning all in a single bundle. But it is also harder to implement and replace the traditional business process.
I haven't encountered a need for support with KiSSFLOW. It's not a perfect platform, but it's functional, dependable, and reasonably intuitive. I can't fault a support team just because their product works!
There are many resources available supporting Visual Studio IDE. Microsoft whitepapers, forum posts, and online Visual Studio documentation. There are countless demonstration videos available, as well. If users are having issues, they can call Microsoft Support, but depending on the company's agreement with Microsoft, the number of included support calls will vary from organization to organization. I've found that Microsoft support calls can be hit or miss depending on who you get, but they can usually get you with the right support person for your issue.
As analyst I participated in a developer boot camp. At times it was hard to keep up but most of the time it made sense. Trainer took the time to explain and slowed pace down to answer questions etc.
IT is very complicated to understand all the functions that the environment has if you are not familiar with this type of development environments. It is important to select a good in-person training to achieve to understand all the possibilities and the capacity of the application. In this case, you will be able to develop a lot type of different applications.
If you are not accustomed to develop in this type of development environments it would be complicated to follow all the parts of the course because if the course does not include a great tour with all the concepts to develop you will not have the option to understand all the functions.
Appian has enormously transformed and keeps on updating the product every quarter to meet the latest needs of the world with new innovations & technologies being integrated within the platform. What gives more pleasure than a product that keeps on continuous[ly] improv[ing]?
KiSSFLOW is much easier to set up, less coding and easier to explain to those that are being trained. The company already had SharePoint, but it is a very difficult system to set up. A class had to be taken, along with getting books in order to understand the process of the workflow. With KiSSFLOW, it is simple to understand, the helpdesk is quick with their response, help topics are laid out simply and you can even talk with someone on that side to ask your questions. Overall, KiSSFLOW is a much easier workflow and system to use.
I personally feel Visual Studio IDE has [a] better interface and [is more] user friendly than other IDEs. It has better code maintainability and intellisense. Its inbuilt team foundation server help coders to check on their code then and go. Better nugget package management, quality testing and gives features to extract TRX file as result of testing which includes all the summary of each test case.
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.
The only real hard number savings that we have had with KiSSFLOW is the money we have saved in forms being printed, especially multi-part forms. So for a small college like us that it probably in the $5000 to $10000 per year range. We have certainly saved money in increased efficiencies of the processes that we have moved to KiSSFLOW. But that is harder to calculate.
Using the integration between Visual Studio and our source control service, the cost of re-work and losing code is drastically reduced.
Paid versions of Visual Studio enable developers to be so much more productive than hacked-together open source solutions that it's hard to imagine developing in Windows without it.
When combined with support subscriptions and the vast array of free online help options available, Visual Studio saves our developers time by keeping them coding and testing, not wasting their time trying to guess their way out of problems or spend endless hours online hoping to find answers.
