Microsoft Power Apps Reviews

The solution is a low-code platform that quickly develops solutions for general business processes. Companies can integrate it with their existing systems, access data flows, and deploy applications within a matter of days or even a couple of days.

The tool helps simplify tasks like conference room bookings, onboarding new employees, managing documentation processes, or handling form submissions; PowerOps can adapt to various use cases. Its ability to develop templates and seamlessly integrate data makes it a valuable tool. It can be integrated with Microsoft Copilot. 

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.

I have been using the product for one to two years. 

I rate the tool's stability a six to seven out of ten.

Microsoft Power Apps is a scalable solution. 

We contact Microsoft architects for assistance if we don't get the help we need through the normal support channels.

The tool's deployment is straightforward. Deployment doesn't take much time, usually just a couple of days.

The product's value and benefits vary depending on the solution being built. Some solutions may simplify employee tasks. However, ROI cannot be much since it is an internal process. 

I rate the overall product an eight out of ten. I recommend starting with exploration because it's a low-code/no-code solution that anyone, even without a technical background, can learn. Set up the flow and template, and you're ready.

The solution is for rapid application development software.

There is a specific environment, in part a platform of PowerApps, in which you can just deploy the solutions and then you share the link with the users and they are able to open them using iPads or mobile devices, or even a computer.

We have been working to build a maintenance events app for assets, it's an app to manage and show all the assets that have been working or down for maintenance in an operation, inside one bigger mining company. They have many trucks and many other, let's say, machines in the operation and sometimes they have to put these machines just through a maintenance mode, to see what's happening, or to change some part specifically, or even if the machine is having some kind of issue. That's due to the fact that if it's down, they have to manage how long it's down and what was the part that was the issue, the cause of the issue. They have to change the parts and everything's very costly in terms of money for the company when we have one specific asset that's down.

Previously, they were using a board in a room, just to manage all these statuses.  Instead of this, now we have one specific app that is working in live modes in almost real-time. Just getting the data from the services and showing it on a big board in PowerApps can show what's happened, what's the status, and what's the reason for the issue. This app allows for adding some comments. It's a collaborative app where many people can just go there and add comments and notes about what's happening with the machine.

There are many things there that I like about the solution. I like the galleries, which are really powerful. I like the way that we can build forms very quickly. 

In terms of timing to develop, PowerApps is very fast. We can integrate with Power BI. You can just show the Power BI report embedded in PowerApps, and it works really nicely.

In my experience, the solution's deployment can be tricky.

In my experience, it was not good as it was giving errors around the tables and I couldn't find what was happening. I had to break it down into different solutions - one solution containing all the tables and the second solution containing the application, plus the power domain that I had for this particular application. It's something that's not good, in terms of the way that things work. 

When I added Power Automate into the solution, for some reason it disappeared from my Power Automate page, as it was added inside the solution. It was very, very weird. It may be a bug. 

There's a primary interface and integration feature and we build some HL processes there. However, suddenly after adding this part, and automating the solution to deploy it, it was just not available for me anymore and I had to go inside the solution and open the MS files from there instead of the usual place where all the Power Automates are created. It was like a bug and also. In terms of the issues that I have with the solution feature inside PowerApps, I didn't like it. I've seen this too complicated. It's something that Microsoft has to improve.

The speed and performance could be better. PowerApps sometimes gets stuck, gets slow and I don't have any reason for why it's happening. Suddenly you are trying to see the rows on your screen and you just have a wait to get the results back, then there's nothing happening. These things look like an environmental issue, however, I don't know if it's something about the localization or something else.

We'd like our option in terms of licensing that can be paid by the app and not by users. That could be something good. Just the way that they charge the license, it's too much. There are not many options. They could give a little bit more flexibility to choose in terms of options for a license.

I've used the solution for six months. 

It's stable, however, sometimes it is slow.

There are no issues about the connection falling. Just, when you are using it, suddenly the page is broken. There is no issue yet, sometimes it gets a little bit frozen and you're waiting a little bit more time to gather results. The table is not a big table with many, many rows, so why is it taking so long, so much time to get the answer back from the app? That's the main issue. There's a performance problem. It's not a stability question.

It's scalable if we're talking about the database, about data warehouse, however, not about PowerApps. PowerApps is not scalable. It's scalable, in the sense that the app you can share for many users, however, you have to pay by user. Scalability isn't really applicable.

We're still not running it fully. We're just prepared to start testing. 

We've dealt with technical support in the past. 

We had some little situations where we couldn't get the help as we needed, however, that was a limitation in the tool - it was not an issue with them.

For the most part, they are really good.

Positive

IN terms of the initial setup, we have to choose which kind of approach we are going to use in PowerApps, as PowerApps has different strings. You can choose PowerApps Canvas, or you can choose a driving app, and that's a little bit different. In my case, I chose a PowerApps combo as I needed a little bit more in terms of flexibility and in terms of how I build this topic they screen. 

In terms of the development, it's quick, really it's quick, however, it's not the fastest way to develop and there are some other solutions in the market that are faster in some ways. In terms of deployment, in my experience, when you're going to deploy perhaps an application, you have to build a solution and a solution and it's a little bit tricky. You have to add all the components to the solution and, after that, you have to export the solution and import the solution into the production environment. We have an environment for development and a second environment for production.

The application is deployed, however, it's not in use yet. They are just preparing to start testing the application and once they finalize the test, the app is going to go live.

After I passed over all these little issues that I had, it was quick to deploy. It was just a question of minutes. When we export the solution and import the solution back, it's easy. However, all the processes to be able to finally get over these issues and everything, it took me four weeks just to realize what was going on and handle it. 

I was the one that deployed the solution. 

In terms of ROI,  I didn't see any. However, if you look at the cost of building an app, the coding costs would be much higher without this solution. You can save months of development time and the money needed to deploy the solution. In that sense, the ROI is awesome. 

The licensing is restrictive and can get expensive as you have to pay per user, not per app. It's a range of users. For example, if you go above 50 users, you need to pay more. 

If you compare it with competitors like Google, they are more expensive than Google. Google has another option that's a PowerApps competitor called AppSheets and AppSheets is cheaper than PowerApps.

We are Microsoft partners. 

I'm using the latest version of the solution. 

I'd rate the solution eight out of ten.

There are some things that need improvement in some ways to make the tool better. However, it's very powerful and it's very fast to deploy something. It's great.

In the complete Microsoft Power platform, there are four components: PowerApps, Power Automate, Power Virtual Agents, and Power BI. We use all these four so we can make a complete solution, e.g. a visualization dashboard, automated chat bots, and the rest we can achieve using PowerApps.

Microsoft PowerApps has three types of applications. One is the canvas app. Another one is the model-driven app that is business specific and data specific. Another type of app we can use is open source, e.g. open projects that are called "portals". We can achieve the same thing when developing a website and when doing it in the portal. These are what we can achieve using Microsoft PowerApps and the Power Platform.

Microsoft PowerApps provide the user interface and functionality, e.g. we can create a normal app that is used on web or mobile. Microsoft PowerApps is similar to a form where you perform whatever you want to do. Some look and feel controls are also found in this solution.

Power Automate, on the other hand, is where we automate the backend processes, e.g. the notifications, data extractions, etc. For something that needs calculation, we use Power Automate, while building the user interface and user experience, we use Microsoft PowerApps.  

What we like about Microsoft PowerApps is that it allows us to simplify business processes and user experience. We can also create responsive applications and canvas apps through this solution.

If we need an app that is more specific to what the business requires, we can create model-driven apps through Microsoft PowerApps. We can also create a reusable component which we can use in this solution, through the power component framework, which is a recent development model from this product.

We also love that this product is a low-code tool which has drag and drop controls, so building apps is simplified.

This solution can be more costly for small teams or organizations.

Both Microsoft Power Automate and Microsoft PowerApps are stable products.

Microsoft PowerApps is a solution that can be easily scaled up.

I had no issues with the technical support for this product.

The pricing of Microsoft PowerApps is neutral, because it's completely based on user requirement. If your requirement is simple or less complex, then the basic licensing model can work, e.g. the free model, or else, you need to go for some premium features or model. The cost will be completely based on your product, and what app license is going to work for you. If per user license is going to work, then you can go for that.

Microsoft PowerApps is not that expensive, but for a small organization, getting the license could be tough, because if you have a team of five people, then it's going to cost you.

I'm working as a developer, particularly the main power platform developer with Microsoft technology as a senior consultant. I'm working with Microsoft PowerApps and Power Automate.

Every automation nowadays is using Microsoft PowerApps and Microsoft Power Automate.

Microsoft PowerApps is best for medium to large enterprises.

I'm recommending Microsoft PowerApps for low-code projects. In the past, developers have to work a lot. They needed to use their technical skills, e.g. for developing codes. They needed to learn different languages to perform a simple mission. For web development, they need to use HTML, CSS, and JavaScript. Today, it's about using the Microsoft Power Platform, as it has low-code, no-code tools.

Microsoft PowerApps is a low-code solution, which means that we can now simplify things through drag and drop controls. We can also use different rebuild models through this solution. We can use different rebuild connectors that calculate to connect to different systems easily. Earlier, only developers were responsible for developing apps. Now, citizen developers can also make apps with the help of Microsoft Power Platform, because it's a low-code, no-code solution.

My rating for Microsoft Power Automate is an eight out of ten. I'm giving the same rating for Microsoft PowerApps: eight out of ten.

I belong to a consulting company that develops applications using PowerApps.

I like how fast I can develop an application and put it in production with PowerApps. I think the integration is also excellent. The platforms is growing, so they are constantly adding more connectors on all these things.

I would like it if PowerApps stored the code differently. For example, it would be nice if it were held in our GitHub repo or some other place, and we could version it to evolve it more easily. Another thing I'd like to see is more collaborative features so that more than one person could develop several things in PowerApps at once. For example, you could have creative technologies doing stuff for the visual design while the developers are doing the different things that they have to do to make the application run.

Microsoft could streamline monitoring and management. In addition, it should be easier to put the solution in different environments. For example, you should be able to move from a dev environment to a production environment seamlessly. 

We've been using PowerApps for three years give or take. 

PowerApps is totally stable. 

I don't have so much experience at this point, but I don't think we can do much about its scalability. I believe it scales by itself, but we cannot modify many properties or configurations to allow that. We are a multinational that operates globally, but I work at a regional office in Iberia. There are 700 people working in the company here in our region, but my company has around 20,000 employees globally.

Setting up PowerApps is easy, and I can do it by myself.

I rate PowerApps eight out of 10. 

Our sales reps use it in the field on a daily basis. I get the data from there and then analyze it for my needs. We are also developing an application to start using Microsoft PowerApps. I would assume we have the latest version. 

We get feedback on a real-time basis, which is actually very useful for us.

It is not enough user friendly. It also doesn't integrate very well with SQL Server.

I have been using this solution for almost a year and a half now.

I would say, overall, it is not bad.

We haven't gone that far yet, so I'm not sure. We have almost 500 sales reps who use it.

They are good. We get a pretty good response and support from them. I had to talk to them on a couple of occasions, and it was a good experience. I would rate them a nine out of ten.

We didn't have anything before.

The initial setup was straightforward, but if you want to put more options, it gets complicated.

It is definitely a useful product. I would absolutely recommend it.

I would rate Microsoft PowerApps an eight out of ten because there are still some issues that we are addressing, specifically related to its integration.

Our primary use case is for the three locations in our company. We use it mainly for setting up meetings in our various conference rooms. Numerous choices need to be made - size of room, number of phones and projectors, date, time, number of participants. It's a great way to keep track of everything. We have 200 users. We're gold partners and I'm a lead consultant in our company. 

We can design apps quickly and we can connect to any database. We can connect to any technology, like Microsoft Analytics or SAP. It requires less code from our side and is available on cloud. Updates are done automatically, which is a valuable feature. 

If they would reduce the price, that would be an improvement, and they should also improve their customer service support, because the last time I contacted them it took one week to resolve the issue. That's not right.

I would like to see improvement in terms of implementation. Sometimes the application is a little slow. If I want to load the data from Power Apps, it generally takes time to take the data from experiential Power Apps, but in this case it takes longer compared to other technologies. I've written to them about this.

I've been using this solution for six months.

It's a stable product. 

Scalability is good. 

Initial setup is not very difficult. Even with minimal knowledge it's easy to understand. Deployment took somewhere around half an hour and it required one person to implement. We have four people in the company maintaining the solution. 

If I want to use Power Apps with Singalab, then I have to pay $10 per month. But if I want to have unlimited access to Power Apps that is $40 per month per user. Prices may have changed.

It's very easy to use this solution, you can do integration, there's no need to write much code. I would suggest that Power Apps is for all ERP people.  If you want to connect to SPL on-premises, it requires one gateway. That's the bridge between Power Apps and the on-premises SPL. 

The Power Apps tool is relatively new technology. Not many people are using it yet so whatever problems they are facing, they will be posting to WordPress or something similar. If I need an answer I can go there.

I would rate this solution a nine out of 10. 

We primarily use the solution for in-house management.  For example, for human resources and warehouse management. 

We are a small business. We keep up all sales and duties within our organization. One day someone might be part of the development team, however, next week we want him on the sales team to directly involve them in a small project that we've done for the client. We don't have to go to a different person from an agency or organization or have someone that is always dedicated to a position. We need to be flexible in order to move our employees from here to here. And this solution allows us to change or play around with our own system to reflect the changes of our personnel.

The solution is very straightforward. Its context is obvious and everything is easy to understand.

Compared to previous applications which developed by Visual Basic, we can quickly update the whole business process without spending weeks or a month dealing with those aspects.

I can't think of any features that are lacking.

The pricing could always be less.

I have heard from developers that there is documentation missing in the reporting.

It would be useful if Power Apps were capable of providing more flexible reporting to allow the developer to really to manipulate the data, and get into more details - for example, why it's being changed and how it's been changed. If there was a way they could comment right in the reports, that would be very helpful. 

There should be more document management capabilities.

We've been using the solution for a year and a half at this point.

The stability is pretty good from a business point of view. It was reliable and easy to understand and work with.

We haven't really tested the scalability, however, we've noticed that, since everyone is working from home, it's much slower than if everyone works from the office.

With everything going on, we don't really have the right scenario to really test for scalability. That may happen in the future. COVID-19 has put a lot of plans on hold.

We currently have 12 people using it. They are mostly project managers and developers. We also have two sales people and the CEO on it.

We've never had to reach out to technical support. That's a good thing. It means we haven't had any issues.

The last solution we used was old and it was built in-house. It was time to retire it, which is why we adopted this product.

Although I'm not the person who handles the initial setup, my understanding is that it's not too difficult and pretty straightforward.

Deployment typically takes two months. The last deployment we did started in May and was completed by July.

There isn't a lot of maintenance needed. We have one developer that's dedicated to the maintenance and changing the environment as needed. It's pretty hands-off though.

We handled the implementation ourselves. We didn't need any outside assistance.

The solution is subscription-based, however, I don't handle billing, and therefore don't have insights into the costs. We don't have any extras that we pay for. We just have a standard subscription package.

I'd recommend the solution. Overall, I'd rate it eight out of ten. If the reporting and pricing were better, I'd rate it higher.

I've definitely learned about the power of the cloud. Before everyone used to use the VPN connection to the head office. When we pushed into the cloud and everyone can just see everything and the system is very sound. It also allows our developers to see what they can change. It's been great.

I'm not sure which version of the solution we're using.

My organization deals with the implementation of PowerApps and Salesforce. We are currently scaling up our capacity in low-code, no-code platforms. Essentially, this solution is for building forms from a front-end loan application and quickly rate a particular application.

The model that allows you to establish flow automation is getting a lot of traction from the customer side. It offers a lot of flexibility.

The availability of templates needs to be improved. I understand that the ecosystem around it is still developing, but we need more templates. I would like the entire ecosystem around it to improve.

I would recommend adding AI components. Even though we can always connect to Azure for AI components, they should slowly start looking at adding some AI components to PowerApps so that out-of-the-box learning can be applied to process flows. Salesforce has the Einstein layer that works along with license platforms. PowerApps should also have something similar.

We have been using PowerApps for the last six months in our organization.

I haven't come across any issues. I have not faced any issues with my existing deployment.

It is quite straightforward.

We have our own team for the maintenance side.

One of the main things about this solution is the price. The cost for Salesforce is $35, $25, or $10 per user per month. PowerApps costs much less than that. It is at a good price point. It may change in the future, but at this point, its price is pretty fine.

I would recommend this solution for people who are looking for flexibility. PowerApps offers more flexibility than SalesForce. I would advise others to use a local platform to build and test first and fail fast. 

We are still exploring a few features, but based on what I have learned and seen, I would rate PowerApps an eight out of ten.