We performed a comparison between Appian and Microsoft Powerapps based on our users’ reviews in five categories. After reading all of the collected data, you can find our conclusion below.
Comparison of Results: Based on the parameters we compared, Microsoft Powerapps seems to be the superior solution. Our reviewers find that Appian’s need for integration improvement makes Microsoft Powerapps the better choice.
"What I found most valuable in Appian is that it lets you drill down on multiple things through the structure of the reporting and UI side. It's also low-code, yet it results in quick deliverables."
"The agile manner that we require to create our workflows. This is probably the most critical part of our solution and the time it takes to start processing the solution."
"In terms of interface, it's very good. In terms of infrastructure, it's amazing and already using multiple tools behind the scenes. It's a low-code platform, so it's very easy to implement."
"The initial setup is easy."
"Appian also has very flexible local integration."
"The most valuable features of Appian are workflow management and the ease with which you can build the UI."
"It has created executable requirements and speeds up the SDLC process greatly."
"This is the most complete solution of its kind."
"It is very easy for us to implement. We have a Microsoft ecosystem, and this solution has many components for integration."
"The most valuable feature is that PowerApps can be used by most business users. It is not only for programmers."
"The scalability is good."
"Can design apps quickly and can connect to any database."
"We like that this solution allows us to fully define our test environments, and link them using different code. This means we can do different tests, but with one basic structure, and then export the data and use it in other platforms."
"I can have a SharePoint list and connect with users through PowerApps to present the information."
"Overall the solution is reliable."
"You can easily connect Power Apps with other databases, like Excel, SharePoint, SQL, etc."
"There are some restrictions with respect to using external components within Appian. So, for example, if we do not have a particular feature available, there's a long cycle of getting approvals and all of that. That does not offer flexibility, which definitely can be improved on."
"There are four areas I believe Appian could improve in. The first is a seamless contact center integration. Appian does not have a contact center feature. The second is advanced features in RPA. The third would be chatbot and email bot integration—while Appian comes with chatbot and email bot, it's not as mature as it should be, compared to the competition. The fourth area would be next best action, since there is not much of this sort of feature in Appian. These are all features which competitors' products have, and in a mature manner, whereas Appian lacks on these four areas. I see customers who are moving from Appian to Pega because these features are not in Appian."
"The solution could use some more tutorials to help brand new users figure out how to use the product effectively."
"One room for improvement is the ease of UI UX development, like in OutSystems and Mendix."
"Appian could include other applications that we could reuse for other customers, CRM for example."
"The documentation needs to be improved."
"I wouldn't say their response time is long, but it could be quicker."
"Appian could improve their customer-facing initiatives."
"You can't add too many filters onto anything you build, otherwise, it will be very slow and it will affect your performance."
"The user interface is pretty good, although it is a little bit clunky and can be improved."
"I have always felt that you need an IT background to use this solution."
"I recommend improving Microsoft Power Apps' licensing model. I've encountered challenges related to licensing complexity, which has led some customers to opt for traditional solution development and deployment methods instead."
"The solution needs a bit more refinement in general."
"Integration with databases and other tools needs to be improved."
"We'd like to see more integration capabilities in the future."
"In my experience, the solution's deployment can be tricky."
Appian is ranked 6th in Rapid Application Development Software with 58 reviews while Microsoft Power Apps is ranked 1st in Rapid Application Development Software with 78 reviews. Appian is rated 8.4, while Microsoft Power Apps is rated 7.8. The top reviewer of Appian writes "Low resource consumption, easy setup, and stable". On the other hand, the top reviewer of Microsoft Power Apps writes "Low-code, low learning curve, and reduces manpower". Appian is most compared with Camunda, ServiceNow, OutSystems, Pega BPM and Mendix, whereas Microsoft Power Apps is most compared with Oracle Application Express (APEX), Mendix, ServiceNow, Microsoft Azure App Service and Salesforce Platform. See our Appian vs. Microsoft Power Apps report.
See our list of best Rapid Application Development Software vendors and best Low-Code Development Platforms vendors.
We monitor all Rapid Application Development Software reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.