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
Figma
Score 8.9 out of 10
N/A
Figma, headquartered in San Francisco, offers their collaborative design and prototyping application to support digital product and UI development.
$15
per month per editor
Power Apps
Score 8.0 out of 10
N/A
PowerApps is a low code / rapid application development product from Microsoft that allows users to quickly build apps.
$20
per month per user
Pricing
Appian
Figma
Power Apps
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 surpasses Microsoft PowerApps because of how much easier it is to code. I found Appian easier to code than the competitor because of how you could access the code behind the scene (SAIL). This allowed for even greater customization and helps with debugging when you have …
I think Appian has all major features and my Manager gives this 2 tools to choose one from that. I found Power Apps is easy to learn and develop, but I feel Appian is realy complex. I strugles to learn something in Appian but that didn;t works well. Power Apps gives me …
Power Apps is great for rapid app development and internal business solutions. It helps build user-friendly applications quickly and is a great, cost-effective option for existing Microsoft customers like us. Even non-developers can get started on using Power Apps without much …
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.
I would recommend if you need to start from scratch a product UI or any customer journey that you need to implement that requires designing and visualizing different steps to complete a process. I would recommend that any design/UI/UX team brainstorm and make proposals that they can compare and discuss in a visual way.
Power Apps is ideal for scenarios that are neither too complex nor too large. It is easy to begin development in Power Apps, as it is one of the best tools for low-code development. Power Apps can be implemented for complex scenarios as well, provided there is strong knowledge of the tool and ample time for planning. Our applications benefit from Power Apps' cross-platform support, making it easy to use on any device, including desktops, laptops, and mobile devices.
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.
Figma allows us to create universal content. This means that if multiple designers want to re-use a piece of content, and if everyone's content should be dynamically updated from time to time, we can easily accomplish this by turning design elements into a universal instance. Then, if an update is needed, we can push the change out to all assets at once. It's very efficient and ensures we're all updating content accordingly.
Figma also allows us to set parameters for the company's brand guide and share them across various designers. This way, we can easily pull from approved brand fonts, colors, and more, which allows our assets to remain unified across multiple touchpoints.
Figma also allowed us to create and install our own plugin, which we use to export every slide we have in a frame at one time, versus the default export feature, which limits you to one slice at a time. This is particularly useful for us when we're working on email templates, since we tend to have a ton of slices in any given series.
Power Apps has formats that are pre-built that don't require any coding which makes it easier to achieve your vision. This does become a challenge if your App needs don't fit into that format.
We deal with a ton of data so the fact that you can connect to any data source in addition to their pre-stablished data connections makes the process a breeze.
The online learning resources and tutorials are helpful as well for those who are tech savvy.
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.
It will be great if Figma will consider having the Pages where interactions can be stitched together among the Pages and not just one page with so many Frames to create the stand-alone clickable prototype that can be used to simulate the intended UX
Bring back the Inspect Mode tab right on the right-side panel of the main workspace instead of hiding behind the Dev Mode.
Figma Slides feature could be improved quite a bit more in order to be easier to assemble slides into a presentation deck and having pre-built templates for slides can be useful too.
Sometimes the cost of solutions is greater than the benefit. Licensing is expensive relative to the scope of some business user-created personal or team-level solutions.
While there is a starter-kit for Governance, it is complicated to stand up and requires dedicated resources to provide on-going governance operations. Many organizations are not going to be able to dedicate resources to governance and this causes the sprawl, solution duplication, silos, unneeded and unplanned licensing expenses, and a general "wild wild west" environment.
There needs to be better direction and best practices given around Power Platform Environment utilization and optimization.
The accessibility to the platform and ease for business partners to independantly create solutions is both a benefit and a negative. When the business outcome needed is a good fit for PowerApps it is a quick win, but when not a good fit it becomes a frustration for the business partner attempting to make the platform do something it is not well-suited for. The business partner entangles tech teams in the effort which drains resources and provides a lack-luster solution. All of this to say, it would be beneficial to have some tools that business partners could leverage to determine\understand if the type of business outcome they need is well suited to PowerApps or not.
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
Figma is a pretty cool tool in many areas. My team almost uses it on daily basis, such as, brainstorming on product/design topics, discussing prototypes created by designers. We even use it for retrospectives, which is super convenient and naturally keeps records of what the team discusses every month. Furthermore, I do see the potential of the product - currently we mainly use it for design topics, but it seems it is also a good fit for tech diagrams, which we probably will explore further in the future.
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.
There's a bit of a learning curve, but generally I think it's both more powerful and intuitive that other UX design tools. Most of what I need to do as a designer can be done in this platform, from basic wireframes to creating a design system, to creating pixel perfect designs, to prototyping to dev handoff.
PowerApps is a great solution and I have spent the last year familiarizing myself with the platform and building custom applications to complete a whole range of tasks such as asset management, custom invoice generation, and item restriction tracking. We as a company have barely begun to scratch the surface of what can be achieved with PowerApps.
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 used their support lately but in the past, they had a chat that I used often. They often responded in a few hours and were able to give a satisfactory solution. I would imagine it's less personal now but the community has expanded drastically so there are more resources out there to self serve with a bit of Google magic.
The community forums are extremely responsive to questions asked, there is a good body of online documentation and many community posts to draw from. Although the platform has changed, which means some of the posts are out of date and the solutions provided aren't relevant. Of relevance, I read over 400 articles plus documentation to get this first app built in SharePoint, move it to SQL and make it work exactly the way it should.
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.
In-person training has its own benefits - 1. It helps in resolving queries then and there during the training. 2. I find classroom or in-person training more interactive. 3. Classroom or in-person training could be more practical in nature where participants can have an hands on experience with tools and clarify their doubts with the trainer.
Online training has its own merits and demerits - 1. Sometimes we may face issues with connectivity or the training content 2. The way training is being delivered becomes very important because not everyone is comfortable taking online training and learning by themselves. 3. With the advancement of technology online training has become popular but there is a segment of people who still prefer class-room training over online one.
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]?
Miro is more user-friendly than Figma, but is less robust in terms of web prototyping and graphic design. While Figma isn't made to be used as a design tool, our team has taken to using it as such because it's richer in functions and personalizations compared to Miro and Figma.
1. PowerApps functionality comes with E1 over E3 License without adding extra costs 2. For Nintex you pay (at the beginning) for each workflow, so my intention would be, to do no workflows to prevent additional costs, but I want a platform with a fair price that allows me to create workflows without thinking about the price for each workflow and we use only some workflow and relative easy workflows and forms as a medium-sized company. 3. PowerApps provides a lot of functionality without needing to invest in premium features directly.
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.
