Microsoft Power Apps Reviews

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.

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. 

We use the solution for making forms for Office 365.

The solution is easy to use and map.

The solution should have more integration with other platforms. 

The licensing price could be better. 

We have been using Microsoft PowerApps for five to ten years. 

The solution is definitely stable. 

For sure, the solution is scalable. 

As the solution is deployed on-cloud, there is no need for installation. 

The price for the license could be more cost-effective. 

Customers have the option of monthly and yearly subscriptions. 

The solution is deployed both on-premises and in the cloud. 

I would recommend the solution to others. 

We deal with around 15 customers. 

I rate Microsoft PowerApps as an eight out of ten. 

Our primary use case for the solution is collecting business data and checking for initiative ideas to collect information.

The speed of the solution is valuable.

The solution can be improved by including codes that can speed up aggregates for our project development applications.

We have been using this solution for about a year, and we are currently using the latest version. It is deployed on Azure Cloud.

We currently use a different solution as our ERP.

I rate the solution a six out of ten. The solution is good but can be improved to cater to complex developments.

We are into software consulting. We have been developing various solutions and leveraging PowerApps to do it.

What I like about it is that it is coming from Microsoft. It is very easy for us, our techno-functional consultants to spin an application in days, not in months. 

This is easily integrated with native systems including the Microsoft stack. If we have to integrate with other products such as SharePoint, we can leverage any services using Azure or the same platform.

In terms of scalability, it can scale quite well. It's so scalable with forthcoming technologies. We can develop something in PowerApps, and that can easily be scaled to a bot. We can quickly make a bot there and make it work in conjunction with applications.

We had it integrated earlier with voice channels. You can manage an omnichannel kind of scenario between Voice, Teams, WhatsApp, social integration platforms like Twitter, Facebook, et cetera. 

The RPA is very closely integrated onto the same platform and BI as well. It's great.

The initial setup is very easy.

The product is very stable. 

I have found the technical support to be helpful.

When we talk of integrating with external applications, that's one area where, even today, I had to loop in my code developers. If this area can be streamlined so that my techno-functional consultants, who are on-site, can immediately start working on something without the assistance of developers, that would be ideal.

I've used the solution for four and a half or five years. 

The stability has been great. There are no bugs or glitches. It doesn't crash or freeze. It's reliable.

It's so scalable. We can scale to all the latest technologies and we can integrate with the social platforms. We can integrate with the document management system (SharePoint). We can integrate with the Active Directory exchange server. It's limitless.

It is so much more scalable once you have everything available over in the Dataverse so that you can write triggers and automate a lot of the BPM. Once you have everything with you, you can spin any dashboards, reports, schedules, and then those can go through mail alerts. You can schedule alerts through WhatsApp messages. You can schedule it through voice IVRs. You name a thing, or you can schedule it. You build it over here and then schedule it over there. 

My experience with technical support has been very, very hood. They've been very supportive. The only thing is that you have to have the right support plan. If you have one, they adhere to the SLA quite well.

The initial setup is not overly complex or difficult. It's pretty simple and straightforward. 

I have done the initial setup multiple times for the various installations. I can handle it on my own and do not need outside assistance. 

The pricing is a subjective thing. Whenever we are positioning PowerApps to an enterprise that is already into Dynamics 365 ER PCRMs, it is very easy to position it as they have already made initial investments there. It is just simply that the number of users that are based on the number of applications and it can be scaled. For them, I've never faced any issues. For example, for a hospital with it, we were already reaching out to, say, 40 units. When they wanted to scale to their smaller units, the 70 of them, it was a cakewalk. Then we had a plan to extend it to their pharmacies, say, 50 of them. That, again, was a cakewalk as they were already on that platform.

However, when I go and reach out to a smaller business SMB segment, the challenge over there is that we are faced with competition - with other software which has been built on PHP. If we host it on-prem, of course, then that discussion of cloud versus on-prem and those fundamental discussions creep in and then there is the minimum unit price per license, meaning per user or per app. When you look at it that way, an SMB will see it as expensive compared with open-source options.

I'd rate the solution at a nine out of ten. If the external integration process was easier, I would give it a perfect ten. 

The most valuable feature is the compatibility with other Microsoft components, the connectivity to Microsoft databases, the connectivity to other components on the Microsoft Azure environment, the connectivity to Office 365 and the connectivity to teams and the overall environment.

Microsoft should combine both the web and the mobile environment with all of the layers of development into one package. Currently, it's separated because Microsoft Power Apps does not cover all of these issues, so you have to connect to two different solutions. With Mendix for example, with one environment, the developers can create either a mobile app or a web app — it's an all-in-one environment. Microsoft Power Apps is not a service. For instance, if you want to connect to a database, it will be done via a database platform. 

Microsoft PowerApps is both scalable and stable. 

Microsoft PowerApps has a good support community.

The initial setup is no more complicated than similar solutions. I'd say it's pretty straightforward. 

Overall, on a scale from one to ten, I would give this solution a rating of eight.

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.

We are currently piloting the solution, we are checking it with our workflow.

We were impressed with the functionality of the solution.

The pricing structure needs to be improved, the current information is confusing.

I have been using the solution for a few months.

The install is not a problem at all, it did not take very much time.

We did the deployment and we have a few employees for maintenance. 

The pricing is too expensive and the licensing system is complicated. There are many pages of instruction on how to do the calculations for the price.

We are considering other products at this time because of the cost.

We have just started using the product, it is unclear if we will continue to use it after taking into account the unclear pricing structure.

I rate Microsoft PowerApps a seven out of ten.