Microsoft Power Apps Reviews

The most valuable features are low-code and fast development.

Microsoft is evolving constantly.

PowerApps is still a bit new compared to a slightly more mature product such as OutSystems.

OutSystems has many features that are still not available in Power Apps.

Simple things like navigation are better with Outsystem without much coding.

The key is the licensing; the fees could be reduced, especially at the enterprise level.

I would like to have more usability, with more fanciful navigation. More like what you would find in Outsystems BI. They offer more drag and drop navigation, and more advanced navigational options around the drag and drop lists and hierarchical navigation out of the box is literally a drag and a drop.

It can be done in Power Apps, but you need to do a bit of coding to achieve the same thing. It's lacking in features.

We are in the evaluation phase and have been using PowerApps for three months.

We are using the latest version of this solution.

To be fair, we are relatively new to this solution. It's stable but at the moment in terms of stability, the enterprise version is more sustainable.

The version that I am using is not at an enterprise level. If you want to increase in size you have to purchase more licenses. It's scalable as long as you purchase the license.

We have more than 100 users in our organization.

I have not contacted technical support. We haven't had the need to.

I am currently working with Microsoft Power BI and Power Automate, which goes hand in hand with Microsoft Power Apps.

The initial setup is quite easy, it's as simple as turning it on.

It took us two weeks to deploy it and to come out with the first prototype.

The licensing fee at the enterprise level is expensive.

We are currently doing a proof of concept with Microsoft, we are evaluating some of their products.

I would recommend Microsoft Power Apps to anyone who is interested in using it.

As of recent Microsoft has been evolving the Power Platform rather aggressively. 

For example, I'm using Power BI, and every month they have a rollout of new features, and with Power Apps, when you compare to one year ago has evolved quite a bit, and so has Power Automate.

Microsoft is on a journey of evolving. 

It's a good tool now, but it will be a great tool soon.

I would rate this solution a seven out of ten.

I am not a PowerApps user, but recently I have been evaluating and scoring no-code to low-code platforms (for developing mobile apps). The score chart is divided into sections, such as usability and features like the ability to test and multi-platform. Due to these evaluations, I learned the systems well enough to be able to build a sample application on all of these platforms and then fill in my evaluation.

I like the fact that Microsoft PowerApps it a self-contained solution; I could build everything and then deploy it. I liked the UI designer that they had for building the screens and also defining the flows. Of all of the solutions I evaluated, it was the easiest to use and deploy.

Microsoft PowerApps is not intended for customizing what's generated in a major way. You have these little windows where you can enter your script and such, but there is no script debugging, nothing like that. You build and you auto-generate the code. From there, if you want to customize it too much, then it's going to get difficult — OutSystems was more intended for that; you can do a lot more customization after you build your solution.

The stability is pretty robust. I didn't encounter any crashes or anything unexpected.

I did have a negative experience with customer support. I contacted them and was connected with an automated messaging system; It was hard to get to talk to someone. That was definitely a concern for me.

For me, the initial setup was very simple and smooth-flowing.

I was using a free version. The company has a subscription where you can use certain features for free, but there are features that require a premium subscription to use. I am not certain, but I suspect they would be expensive.

On a scale from one to ten, I would give this solution a rating of nine.

We’ve been setting up an invoice processing system using the tool's document automation reference model. I’ve also been customizing the document automation reference app to create workflows for our organization.

Microsoft Power Apps has helped us handle our fairly complex invoices, including filing and reviewing them manually. We’re working towards automating our invoice processing, labeling them according to organization accounts, and developing an entirely digital workflow. The tool uses customizable AI models for your organization's documents, so it supports AI-driven projects well.

The solution's deployment is complex. 

I have been using the product for a couple of months. 

I rate the solution's stability a nine out of ten. 

Microsoft Power Apps is scalable. My company has two users for it. 

We get limited support if no payments are made for additional support. 

Neutral

I rate the tool's deployment ease a six out of ten. 

My company has non-profit licensing, and hence, it is affordable. Pricing depends on usage. 

I rate the overall solution a nine out of ten and would recommend it to others. 

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 most valuable feature of Microsoft PowerApps is the user interface.

Microsoft PowerApps could improve the speed of Power Automate, it is not very fast.

In a feature release, any additional features would be beneficial.

I have been using Microsoft PowerApps for half a year.

The stability could be better when it comes to performance.

Microsoft PowerApps is simple to install.

The price of Microsoft PowerApps is reasonable compared to other solutions.

I rate Microsoft PowerApps a nine out of ten.

The performance is showing signs of improvement. 

Technical support is okay.

It is good for using for small apps and automation on Microsoft Office items.

The stability of this solution could be better. It's getting better, the performance. However, it's not there yet.

We'd like to be able to leverage more reuse of the code we are implementing in the apps.

I've been using PowerApps for two years.

The solution needs to improve stability and performance. However, they are working on it. 

Technical support is okay and we are mostly satisfied with it. 

Neutral

I'm a customer and an end-user.

I would advise other users to try out the product. We've had a largely positive experience. It's good for using for small apps, and automation specifically for Office stuff. If a company needs that kind of specific usability, I'd suggest they use PowerApps.

It was used to collect or gather information from the requests, assess requests, and evaluate the requests for a new potential project. 

I am a consultant for developers and architects. People to whom I give consultation use it.

It is a cloud solution. Data can be cloud-based or on-premises, but it is mostly cloud-based.

The most valuable feature is that PowerApps can be used by most business users. It is not only for programmers.

Its performance is also valuable.

In some cases, PowerApps would have some limitations in terms of the data, the number of transactions, and so on, but for a normal solution, it would be enough.

I have used it for more than one year.

I have not heard about any issues with its stability.

It is scalable. It is used by more than 200 people with different roles, but only two people directly work with it. 

People use different solutions for different projects. The previous project was on another technology. They switched because it was more simple, and they knew similar technology for developing the project. They were already using other solutions, such as Power Automate and Power BI, from the Power platform.

It doesn't require any installation. PowerApps works on the Microsoft cloud on the server, and you have two options for using the data. The data is possible on-premises or on the cloud, but PowerApps is only on the cloud.

It depends on the subscription of Office 365 that customers have. With some subscriptions, it's possible to use PowerApps.

I would recommend this solution to others. I would rate it an eight out of 10.

PowerApps is mostly a front end. It's a form where users can input information, and it gets goes into a database.

If you want something that you can use for cellphones, multiple tablets, and things like that, you can use PowerApps for the front end. It gathers all the information, and the information goes somewhere else. 

PowerApps can't do a lot of things that users need now. For example, it can't handle signatures. 

We just started using PowerApps last year.

I don't know if PowerApps is suitable for the enterprise level. When we need an enterprise solution, we don't use PowerApps because it's too complicated for the users and creates too many headaches for IT.

It's hit or miss. Microsoft makes changes so fast that even their support engineers are confused. Sometimes I'll change my settings, and then I'll go back to my settings the next week, and I can't find it. Finally, I realize that Microsoft changed something, and this particular setting is now integrated into another part of the menu. They keep doing that. It confuses the admins and even their own people.

Microsoft had a solution called InfoPath that they discontinued and replaced with PowerApps. I still like it much better because of the licensing issues. PowerApps' use case is more general. Microsoft took InfoPath's functionality and made it more complicated in PowerApps. 

They did the same thing when they introduced the new version of Power Automate. Microsoft took away the best workflow feature. Without that particular one, it's hard to create general workflows for somebody else. Many people don't know how to create workflows, so they rely on IT to do that for them.

Setting up PowerApps isn't straightforward. We allow users to be citizen developers, as they call it, and around 95 percent of the time they end up going back to us, saying, "Hey, we can't use this. We don't know what to do. Help us!" As IT, we're spending a lot of time creating these forms for them instead of users doing it themselves.

There are better solutions like Jotform, which is a complete form solution. We're now using Jotform instead of PowerApps because the workflow is simplified. It can accept signatures, and there are many widgets you can use. Jotform has drag-and-drop functionality. However, even with drag and drop, many users still can't build forms and need help from IT. 

It's just a matter of which will make the best use of your time. If it takes a long time to create something in Power Apps and half the time to do it in Jotform, I would make it in Jotform and be done with it. We also use Microsoft Forms for simple forms instead of PowerApps.

I rate PowerApps four out of 10.