TrustRadius Insights for Power Apps are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.
Pros
Tight Integration: Users have consistently appreciated the seamless integration of Power Apps with a variety of technologies, including Microsoft's Power Automate, Teams, and SharePoint, as well as non-Microsoft platforms. This integration has provided users with a diverse set of options for developing applications tailored to their specific needs.
Low-Code/No-Code Feature: The low-code/no-code functionality in Power Apps has been widely praised by users for its ability to empower them to create sophisticated enterprise solutions without requiring extensive coding expertise. This feature has significantly reduced barriers to entry for app development and enabled users across different skill levels to build robust applications efficiently.
Abundance of Sample Apps: Many users have specifically highlighted the wealth of sample and example apps available within Power Apps. These resources have proven instrumental in jumpstarting projects and expediting the development process for users by offering practical templates and frameworks for building their own solutions.
I used the Power Apps tool mainly for two processes: one for employee performance tracking and the other for NACH form creation and management for a project POC. In both cases, this tool was perfect because our organization uses Microsoft Teams and Outlook for main communication. As a result, the integration, tracking, and everything else were easy for us. Moreover, it can integrate with Power Automate, and a single click in Power Apps can trigger an entire Power Automate process, which attracts me even more.
Pros
Seamless integration with Microsoft ecosystem
Easy development of Ui and easy to give controls
Cross platform compatiability is a new
Cons
need to improve UI improvement options like styling. Currently I personally feels like using HTML without CSS
Sometimes it produce different outputs for same formula, may be it was a but that I encounter.
What if I want to integrate with non-Microsoft tools. I feel diffuculty in integrating with other apps
Sometimes app's response was weird. It simply stuck in same page for long time.
Likelihood to Recommend
It well suits for some kind of internal process tracking, automation and other works. We can simply integrate, automate, analyze and display. Its low-code solution and rapid development option suits well for internal purpose even a beginner can create app with Power Apps. In out organization we used it for employeeperformance tracking and it currently works well. I don't recommend it for ui that requires highly attractive design and more complex ui controls. And other is applications using high data transaction and advanced data processing.
Power Apps are used to develop low-code web apps, publish them, and deploy them quickly across the organization. It supports integrating all the standard Microsoft applications like SharePoint list, etc., using various built-in connectors. As most of the data is stored in SharePoint, it is extremely easy to link it with power apps while creating an application. Most features can be easily added to the development canvas with drag and drop, and anybody with basic programming knowledge can develop an end-to-end application.
Pros
Supports connectors with most of the Microsoft applications like SharePoint/SQL Server, etc.
It can be easily published and deployed with a simple button, and the version of the deployment can be easily viewed.
Cons
Power apps need to improve the process of changing data sources. For example, if I want to change the source of a share-point list that is linked to certain fields in my development canvas, I need to rebuild and link them back, which is time-consuming and additional effort.
Likelihood to Recommend
Power apps are highly recommended for developing basic web applications as the learning curve is shorter. All resources to build a web app are available online, and the cost of development is almost 0 as the license comes bundled with Microsoft 365. unless the paid connectors are used, a web app can be easily developed with a very low budget.
We take advantage of the low-code features to enable business partners and junior developers' participation in the creation of enterprise-level business solutions. PowerApps is mostly used in relation to content in SharePoint Online Lists and Dataverse tables -- providing quick multi-screen apps for data entry, display, and manipulation. Since PowerApps is the out-of-the-box way to enhance SharePoint forms, it is an easy step to go further and add business logic. We extend the effectiveness of the solutions by integrationg with Power Automate to provide complete user-interactive logic and "back-end" business process automation.
Pros
Tight integration with other technologies such as Power Automate, Teams, and SharePoint - as well as many non-Microsoft technologies.
Low-code\No-code that can produce enterprise-level solutions
Vast number of sample and example Apps are available to kick-start a solution.
Cons
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.
Likelihood to Recommend
PowerApps is well suited for "quick-wins" and fast prototypes of business solutions. It also is beneficial for situations where business partners and developers work together - it allows the business folks to provide a "quick-and-dirty" prototype which is then fleshed-out by developers that are trained experts on the platform. The interactive and easy to understand representation of the solution allows business partners to "see" the solution and add, remove, or correct aspects of it themselves. It provides a common view and understanding of the actual solution across business units and tech teams.
PowerApps, being a low-code\no-code platform is not well suited for business processes that require many complex computations or large amounts of custom code - such as solutions that are better architected as Web Site or "full-blown" desktop solutions. There are solutions that are just not easy or quick to accomplish in a low-code\no-code platform. Enterprise Architects should know the difference, however business partners often try to create a solution and only when stuck because it becomes too complex do they engage a tech team for assistance - at which point there are sunk-costs involved and hinderences to re-platforming the solution.
I'm currently utilizing Power-Apps to fix our quality assurance issues. I've created multiple QA forms out of Power-Apps that help our department capture important information about errors in our cases and capture data from multiple sources (individuals) and sort that information by the manager, case type, error type, etc. I have also used it for other issues such as a reference tool to prevent multiple emails and case requests for situations that do not need a case.
Pros
Data capture.
Sends information to multiple places (i.e. SharePoint).
Creative flexibility.
Multiple uses.
Cons
Some situational formulas that seem easy to figure out are more complex than would be expected (such as using If functions, but it just takes a bit of research to figure out what you want to do).
Likelihood to Recommend
Power-Apps can be used for virtually any type of situation. I've seen it used for an office reservation tool, especially during COVID, where that has been extremely useful. I currently use it a lot for various quality assurance forms for various teams who need different things to review for each team that calculates scores, as well as sends the information I need from various sources to SharePoint for analysis later. People can use it for mobile apps or canvas apps - I prefer canvas apps, but you can really create pretty much whatever you want and there are so many different tools and items to use for each app (scanner, signature insert, etc.). So really the sky is the limit.
We create alot of our own programs in house and we have recently sought the need to build apps for what we do. The Power Apps program is very user friendly for us to start the app building process. Our IT Team is able to utilize it to build apps for our employees to make certain job tasks more efficient and effective. We always need help with getting different program platforms to communicate with one another. We also need data that we have stored to be accessible to our employees as they move freight every day. Building an app for that has helped immensely.
Pros
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.
Cons
I think more formats would be helpful.
I think having more customizability with current formats.
Likelihood to Recommend
When building a data pulling app from one of our current programs we ran into trouble with the current program having the ability to communicate to an app without losing restrictions on the program. It did require communicating that out with the program provider. There are times where you will have to figure out solutions to make the app work that our outside of the Microsoft program.
We started using PowerApps when the pandemic hit. We used it regularly for answering COVID-19 screening questions and to book a particular lab area to ensure that we were socially distancing and not crowding in the same lab space.
Pros
Scheduling
Organization
Customization
Intuitive
User friendly
Cons
Maximum upload size is low.
Item restrictions.
Likelihood to Recommend
Based on my experience, PowerApps is highly suited for organizing, scheduling, and planning. Highly useful to keep records and create events. We really benefited from using the PowerApps when we were undergoing a phased opening of our labs during the pandemic. We were to operate on limited capacity, and scheduling our workday through PowerApps helped ensure smooth functioning in the interest of everyone's safety and health and avoid chaos.
PowerApps was primarily used to create basic user Interfaces and to guide workflows so that less technically savvy employees were not having to manually interact with sharepoint lists.
Pros
Fetching data from Sharepoint.
Manipulating items in the Dataverse (MS's SQL thing).
Guided user interactions.
Cons
The editor takes Forever to load a full project for editing. for more complex projects, I have to open it first thing in the morning, go make a coffee, handle all of my new emails, take a coffee break, then come back and pray its ready to use
Formulas - I'm not sure why it seems to require the sacrifice of a live chicken to get PowerApps to accept a complex formula that is syntax-correct, but it seems to help!
Field reference. if you are mapping to data in a SharePoint list or dataverse, being able to grab the correct fields is akin to Sorcery.
Likelihood to Recommend
Powerapps is the lesser of 2 evils. It lets to restrict what people can see and how they can interact with it, but it has the potential to be a bit of a dragon when trying to implement it in more-complex workflows.
VU
Verified User
Engineer in Information Technology (10,001+ employees)
We use PowerApps for Forms in Workflows, for Apps and SharePoint Forms. Business problems: Our focus is a paperless office. So we need a tool for digital forms like Microsoft Power Apps. In former times we used Nintex Forms but the prices of the Nintex Cloud were not attractive for us anymore, because Microsoft implemented a good workflow and forms solution with PowerAutomate and PoweApps. We try to exchange old paper-based processes with new modern digital processes without paper by using PowerApps.
Pros
WYSIWYG Editor with easy Drag & Drop.
JavaScript for additional functionality.
Integration in SharePoint Online.
Integration in Teams.
Cons
More complicated to understand in comparison with Nintex Forms.
Complicated to find errors.
Using PowerApps for SharePoint Forms is a bit complicated by setting up the start and load scenario with a lot of JavaScript.
Load values, change them by code, and save them back could be easier. Actually quite complicated to handle a lot of variables.
Likelihood to Recommend
PowerApps is good, but not perfect. There is a lot of room to improve. Nevertheless, you can get a lot of functionality out of the box and you have the possibility to program with JavaScript additional functionality. I wish the usability would be improved. Nintex is much more user-friendly and easier to understand but may be more limited. In my opinion, PowerApps is a mighty platform and well-integrated in the Office365 suite.
VU
Verified User
Manager in Information Technology (201-500 employees)
We are able to build business apps with PowerApps on Azure SQL. We are able to develop budget-friendly applications for various domains of our organization. The coding part is relatively easier when we have the structure in place. We are using it to do inventory management and support which has reduced the burden on us and we are able to have proper stock and do purchases accordingly. The scope of the use of PowerApps is quite huge in small businesses as well as large organizations as it provides a standardized structure that can be customized according to the needs of the organization.
Pros
Application development.
Query building.
Integration of apps.
Front end and back end integration.
Database management.
Cons
Use of graphical user interface.
More graphical representation.
Instruction based application development.
Likelihood to Recommend
PowerApps is well suited in organizations with less complex structures. It is easy to use when the organization has a centralized decision-making system and decisions are readily taken. It may create issues among multiple decision-makers as they may have disagreements on certain issues which may cause a backlash among themselves on issues pertaining to just-in-time inventory management or throughput time of the process to be completed. Organizations can overcome these issues with the centralization of decision-making power to making power.
We utilize the PowerApps platform to run a built-in-house application for inventory control. The tool is built on the M365 cloud platform to connect seamlessly to our databases as well as to be available across all of our facilities without the need for heavy infrastructure support. The business's workflows and Standard Operating Procedures are always changing, with PowerApps we can control the nuances and change management in-house vs waiting for an external firm to make the necessary changes on their development roadmap. PowerApps has solved the problem of waiting on vendors, leaning out infrastructure requirements, and bringing in efficiencies for inventory control through with PowerApps automation vs paper and pen model. The tool requires little support and little change, it has really been a game-changer for a start-up company in growth mode.
Pros
Automate manual processes.
Quick and easy setup.
Can scale very quickly.
Can be customized.
Easy to learn and manage.
Cons
UI can be a little confusing if not technically savvy.
Licensing is complicated.
More integrations to other platforms and processes.
Likelihood to Recommend
PowerApps is best suited to automate any workflow or standard operating procedure that requires paperwork and data intake. Specifically, this app can build an automated process to do anything you do manually with data. It allows you to connect other platforms together for seamless transfer of data, as well as making mundane processes easy with GUI.
VU
Verified User
Director in Information Technology (51-200 employees)