Microsoft Power Apps Reviews

The solution is used internally in my company.

Flexibility, easy setup, and fairly quick results are valuable features of the product.

The fact that we couldn't share that with our other organization or outside of the organization, consisting of our colleagues in the joint ventures, was a weakness of the solution. So, it is an area that needs improvement.

I have been using Microsoft Power Apps since 2018 or 2019, so it's four or five years. Also, I am using the solution's latest version. I mainly use the cloud version. I am a customer of the solution.

Regarding stability, with the normal version of the Canvas app and Power Apps, and for fairly simple apps, it's perfect. But if you need a more nested or layered system in your app, setting them up takes a little time. And it also takes a lot of manual maintenance of the items in your product.

Stability depends and varies from case to case. So, what I do is mainly internal and feedback collection and everything to manipulate how the data comes in, which is great. The interface or setting could be better, but they would have compromised all the other things, including the lead time for development. So, for that level of work, the performance would be about eight on a scale of one to ten.

Scalability depends on the knowledge and skill set of the users. My user community has been in range from seventeen hundred to five.

Given the size, I think that support from the technical team is acceptable. I have had problems with SharePoint, including stalling and throttling of the back end and everything. It took me quite a long time to get an answer from Microsoft, which I understand, as they are big companies, and so they are not going to fix it for you the next day even when they know something, so I would say it's considerable and understandable. There are things that are up there, and they probably are not such a technical hassle to be developed or to be resolved. Now, considering the fact that they have already been around for a few years, it can be a bit disappointing. But, well, given the user community and the forums and everything, I think that it is forgivable.

I use Mendix. Mendix has more of everything in one place, and you can see your process actually as in a flow instead of ready code or work with the objects in the front end. So that's definitely a pro of the solution. The problem is that it's much less configurable with the other solutions than Power Apps. Power Apps by itself is not configurable, but it is pretty much configurable when connected to a database, Azure or SharePoint.

The solution is deployed on a corporate cloud, so it is for the organization's private use. The time taken for deployment depends on the complexity. But, when I was working on Power Apps, it took me days. When they were responsive or needed to form a table, I needed to manually add blocks on top of each other, including everything in that, and that was taking a long time.

Usually, the free licenses of Power Apps come to normal corporate users for free. If you do not use the premium workspace and are employed in a big company already using E3 or E5, then Power Apps would be something for free, and that's a trick. For normal users within a corporate firm with licenses, it's totally favorable. But I don't know how it would be if you were outside a company or using it yourself.

The overall performance of the solution depends on the use cases. So, Microsoft Power Apps is perfect for smaller things or smaller assignments. For very big things, the solution's overall performance also depends on the education level of the people using it. But if you want it to be super reliable and whatever, I would say that it has some constraints. And I was using a version of the solution with SharePoint and all. I was still working on the database and things like that. I understand that they will probably be performing much better. The normal version is not a super reliable tool.

Microsoft Power Apps has been very useful. With Mendix, I have been a user of the developed solutions, but because of the tool and the license you need to get or the training you need to get before starting with the development, it has been hindering, so I cannot really say. Overall, I rate the solution an eight out of ten.

Power Automate is like process automation.

Any task which you do on a recurring basis or a daily basis, you can simply automate. For example, if you have a use case where every day when you go home you need to book a cab. What I can do is I can automate that task through Power Apps at a scheduled time every day. If I'm leaving at about four o'clock in the evening, by 3:30 I can run that Power task and book a cab every day.

With Microsoft, the main benefit that we get is it's easy for a layman to understand it. That's the advantage of it, it's user-friendly. 

The way it integrates with the other applications is very good. The experience is seamless; there are no hurdles. Connectors are easily available, which can help you connect with some third-party apps if required. 

The initial setup is easy.

It is stable and reliable. 

We can scale it. 

They probably need to improve intelligent document processing. In terms of reading the documents, whether it's a Word document, an Excel, a PDF, an HTML, or a webpage. Identifying the key things with its own intelligence is something that Power Automate and Power Apps need to improve.

I've used the solution for close to a year now.

It is quite stable.  It gives you that assurance since it is from Microsoft. The stability, the reliability is definitely there.

It is scalable. We have a lot of ground for it to scale it up, and add more and more apps or users can be added as per our business requirements.

It's being used widely by many people, in fact. However, it's hard to pinpoint the exact number of people who benefit from it. Anyone can quickly learn how to use it as well. 

I'm aware of UiPath and Automation Anywhere which take a longer time to implement. 

It's very easy to set up. You should have all the licenses available. It's quick and easy to implement, and you can get your hands on it immediately. It doesn't take too much time to get up and running. In contrast, its contemporaries like UiPath and Automation Anywhere are not so quick and easy to implement.

The cost depends on which bundle you get from Microsoft. For example, if you go with the standard Office 365 with the other packages around it, it's good enough. However, if you go for anything specific, you'll have to think about it and customize your requirements. If you go for 365, your cost would be less. If you go for Dynamics 365 with Azure, then it's a complete package that will be expensive.

We are Microsoft partners. 

My advice for those people in tersted int eh product would be to try it if they are looking at implementing something very quickly with minimum cost and minimal training. If these are their objectives, then Microsoft Power Platform is a very viable solution.

I'd rate the solution eight out of ten.

Initially, we used it mainly to wrap up Power BI reports for BetterView, creating very simple apps. About a year ago, it evolved into more robust apps for collecting information, particularly for logistics. We developed apps to streamline workflow and gather data for specific operations. We then built a more advanced app that allowed us to communicate with customers—connecting workflow issues, creating problem reports, and sharing shipment updates via SharePoint, which integrates easily with Microsoft Power Apps.

Currently, Power Apps is used mostly locally, within one or two departments. Each app is developed locally, and it’s not really used for enterprise-wide purposes. In our organization of about a thousand people, around six people are developers working with Power Apps. There are likely a couple of hundred users in total across all apps.

Over time, it became a key part of our operations, and we've developed around three or four apps in total. However, the main use case remains displaying Power BI reports. By wrapping reports within Power Apps, we can present them in different formats to create better dashboards, making the process more efficient.

In my experience with Microsoft Power Apps over the past two years, the best feature is its seamless connection with the Microsoft ecosystem. It integrates well with Microsoft Teams, and you can use it with minimal programming, which is typical for low-code and no-code apps.

A downside is that Power Apps is primarily designed to work within the Microsoft ecosystem. It’s not suited for publishing apps outside of the network, so you need additional Microsoft technologies for broader use. While it’s very scalable for simple apps, it's not ideal for large-scale enterprise applications.

I’ve been using Microsoft Power Apps for about two years.

In terms of pricing, Power Apps is cost-efficient.

Overall, I’d recommend Power Apps for its ease of deployment and supportive documentation. However, it's not suited for complex, enterprise-wide applications. I’d rate Microsoft Power Apps an eight out of ten overall.

We use the solution to integrate with enterprise solutions like SAP and other enterprise solutions. It's highly integrated and highly secured. 

Externally or internally, we have several business processes that need to be automated. We write evaluations and also evaluate business procedures to see how they can be simplified. Power Apps is one of the solutions that we mostly use in our company to automate processes. We also have several clients who use it to automate SAP processes. This is the most critical business function in clients' core mission.

It's easy to use. We create great user experiences.

The track-to-use function is great.

It is easy to design automation processes.

The initial setup is mostly pretty simple. 

Users don't have to have any technical competence in order to begin creating automation. 

We'd like to have access to previewed content and preset options. If we could preview content for specific software, that would be ideal.

The user experience could continue to be improved upon. 

We'd like more features and less to no coding. 

I've been using the solution for three to four months. 

It is s stable product and I have found the performance and reliability to be good. It doesn't crash or freeze. 

The solution is scalable. It's also adjustable. 

We have around 200 people using the product.

We do plan to increase usage. 

The product is fully supported by Microsoft. We have a ticket for tracking issues. There's also a community around it that can assist. They are quite responsive. 

Positive

We've also used Blue Prism and UiPath. Since most of the automation processes are based on Microsoft technology like Excel and other Microsoft-related solutions, and Power Apps is based on Microsoft technology and is highly integrated with those solutions, it made sense to switch.

It's a stand-alone solution and uses connectivity to the software we want to automate. It's not hard to set up or to start automating things.

I'd rate the solution a four out of five in terms of ease of setup. It's not overly difficult. 

We were able to deploy the product in about a week. 

We have 50 to 100 people maintaining the solution. 

I handled the implementation myself as I started out using it for testing purposes. I did not have outside assistance. 

I don't handle the licensing aspect of the solution. It's handled by another team. 

It's my understanding we pay around $150 to $200 USD per user. 

We're using the latest version of the solution. 

I'd recommend the solution. It works so well with other Microsoft solutions. It also could reduce the workforce and release employees from redundant daily tasks.

I'd rate the solution eight out of ten.

We primarily use the solution as a general business process improvement. We use it as more of a digital transformation to eliminate some archaic manual processes that the business has built up over time. We're working to make everything more streamlined.

The solution has allowed us to remove a lot of manual redundancies and to update and streamline our processes.

It's easy to use due to expert UI. It is great.

The initial setup is easy.

There's a lot of online knowledge on the solution, to the point where new users can basically teach themselves how to use the solution.

The solution is limited in a very specific way. One of the major problems with it is what PowerApps calls the delegation warning. Regardless of what platform, data source, et cetera, that you're using, you can't retrieve more than 2000 records.

I connect to an Oracle server that has well over 150,000 records that business users want to see or could use at any given time. The only thing that I could surface in the app is a portion of up to 2000 records at one data call.

Due to this limitation, I have to build in options for the user to refine the search, to go back out to the server, and then pull back records that match that search as opposed to offering all 150,000+ records. You need to filter quite extensively. Microsoft refers to is as a "delegation issue".

I've only been using the solution for about a year. It hasn't been too long as of yet.

The stability has been very good. We've been pretty satisfied with it. It's not buggy. It doesn't crash.

You cannot scale with PowerApps. PowerApps is still very much a point solution. The size is the size.

We've dealt with technical support in the past. Everybody that we've worked with at Microsoft is phenomenal. They are always willing to help troubleshoot and get to the bottom of issues. That said, with PowerApps and even Power Automate, sometimes the teams at Microsoft still don't know why some issues occur or how to work around them.

I joined the company a year ago in September. I don't think they used anything prior to that beyond the citizen developer level. There might have been a solution that the actual coders used, however, I can't recall the product's name. It was a pretty standard Microsoft application in any case. It may have been Visual Studio.

The initial setup is not complex. It's quite straightforward.

For me, just using it on my own, I just used Google searches or YouTube to figure out how do this or fix and tie items together. After about a month of learning and experimenting, I had a pretty good handle on how PowerApps works.

The company as a whole used Microsoft consultants to set up a center of excellence. 

The solution is free if you have a Teams account, or Office 365. 

If you start to use any premium connectors that are not stored in a SharePoint list or on an Excel workbook, then it costs $4 per user per month. If you want unlimited, it's about $16 per month for unlimited apps and unlimited connectors.

There might potentially be a few other extra fees, however, I'm not sure what they are. Microsoft is one of those organizations that manage to nickel and dime its customers on everything.

We're just a customer. We don't have a business relationship with Microsoft.

We are most likely using the most recent or updated version of the solution, however, I'm unsure of the exact version number.

While Microsoft is an option, I'd recommend users check out OutSystems first and see if it makes sense for them to use that before looking into Microsoft.

Overall, I'd rate the solution six out of ten.

We had a new requirement from a business in the clinical domain and the business wanted to identify risk at a study or site level. We created an application using PowerApps, which works well as we usually interact with the SQL Server on Azure.

I did some POC for another application. We’re expecting we'll get it in a new project in the near future. It is a really good tool. We can run programming knowledge, we can learn the PowerApps and we can interact with applications.

It is user-friendly. Anyone can easily learn and work on this tool.

The solution is easy to implement.

It’s a stable product.

Not much coding is required.

I don’t have much hands-on experience with PowerApps. I’d need more time with it. As of now, I can’t think of an area for improvement.

We did a POC with the solution. We’ve used it for the last 12 months.

It’s very stable. It’s reliable. There are no bugs or glitches. It doesn’t crash or freeze.

I cannot speak to how scalable it would be. However, it may work best with a lesser amount of data.

We might have about 100 people on the solution.

I don’t have any experience using any other tool.

It’s straightforward to set up the solution. It’s not overly difficult or complex.

We did the integration ourselves. We didn’t need the help of any consultants or integrators.

I don’t have any details in relation to the pricing or licensing.

The tool was suggested to us, and we decided to try it. We did not evaluate other options.

I’m not sure of the exact version number. However, we are using the latest version.

I’d recommend the solution to others.

I would rate the solution an eight out of ten. There may be other tools that are easier to work with. However, I’m not sure. In general, it works well, and we have been happy with it.

We are a construction company, and we use the solution for a lot of project management tasks and to make some relevant tools for the business.

The solution's most valuable feature is integration. It's highly beneficial because you can bring data from many different places to it. It's an easy, pluggable solution that everyone can use. It can make a very user-friendly solution, and you can show your data from it. The solution has a new, modern look and feel and is integrated with Microsoft Power Automate and AI technology.

Microsoft Power Apps must be more robust when integrating with Microsoft Power BI. It should be a more connectable solution so that it works in a better way.

I have been using Microsoft Power Apps for five years.

Sometimes, the solution faces network failure, slows down, and does not fetch things correctly. It has some limitations in showing the number of data, which is understandable since it's a low-code tool.

I rate the solution’s stability a six out of ten.

I think the solution's scalability is growing faster, and it was a long wait for such a tool with Microsoft. It's been improving for the last five years, so the progress is good, and people are using it. People like the tool because it has good scalability. More than 1,000 people are using the solution extensively in our organization.

I rate the solution’s scalability a seven out of ten.

We raise a ticket through Microsoft for any issues. Sometimes, the support is good, and we get call center support. Other times, we have to fix the issues ourselves. The technical support from Microsoft is not consistent.

Neutral

We previously used Microsoft .NET, which took many months to develop the system. We switched to Microsoft Power Apps because it is easier, requires fewer people, and requires less time to deploy.

The deployment time depends on the situation, but deployment is pretty easy. You can fix things and deploy the tool within two hours. We have different environments from test to production. We move, set up a package, deploy the package, and change the connection strength. Around two to three people were involved in the solution’s deployment.

On a scale from one to ten, where one is difficult and ten is easy, I rate the solution's initial setup a seven out of ten.

We implemented the solution through an in-house team.

The solution has helped grow our organizational value by converting tasks from manual to automatic.

Microsoft Power Apps is not an expensive solution.

On a scale from one to ten, where one is cheap and ten is expensive, I rate the solution's pricing a five out of ten.

I'm a consultant and a customer of Microsoft Power Apps. The solution is automatically updated, and I'm using the recent cloud version of Microsoft Power Apps. Two to three people are enough to maintain the solution. Microsoft Power Apps supports our mobile workforce or remote operations well.

Overall, I rate the solution seven and a half out of ten.

We use Microsoft Power Apps to support some IT processes and for employee evaluation. Sometimes, we use the solution to prepare electronic forms where we cannot use Microsoft Forms. We also use Microsoft Power Apps to prepare small custom applications.

I like the solution's ability to approve some tasks electronically. When we use Power Automate to build workflows, one of the steps is the approval process. It is very convenient to have the possibility of accepting some activities.

Because we have a lot of data and users, achieving an appropriate level of security and privacy is sometimes difficult, especially for sensitive data. I do not mean that the system is lacking in this area; rather, we need very competent people. I believe we don't have enough people to appropriately secure our data and control the transfer of this data.

I have been using Microsoft Power Apps for three years.

I rate the solution a nine out of ten for stability.

I rate the solution’s scalability a nine out of ten.

In some cases, it's very difficult to get very competent reactions from the support team regarding our tickets.

Neutral

The solution’s initial setup is easy.

We have seen a return on investment with Microsoft Power Apps regarding time savings.

On a scale from one to ten, where one is cheap and ten is expensive, I rate the solution's pricing a six out of ten.

Microsoft Cloud can integrate with on-premise infrastructures, but this requires additional licenses. These additional licenses are expensive for us because we have 8,000 employees. Integrating cloud services with on-premises systems is not easy for us. This is mostly not because of technical problems but because of the cost of such integrations. I would recommend the solution to other users.

Overall, I rate the solution an eight out of ten.