Microsoft Power Apps Reviews

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.

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.

I'm working for a company that provides services and develops projects for our clients. I am a solution architect and I use Microsoft PowerApps.

In Microsoft PowerApps the most valuable features are the fully customizable design that we can control everything that we would like to control. For example, the integration between Microsoft and third-party services through pre-built connectors, and the functionality to create custom connectors.

The solution could improve by having more connectors for different solutions in a way to create custom connectors. Additionally, they should make HTTP Connectors free again because it was not always a premium feature. These HTTP connectors allow you to send API requests which can be important.

I have been using Microsoft PowerApps for approximately four years.

The performance and the stability of Microsoft PowerApps are great because it is based on the Microsoft platform. We are able to use a lot of other features, we have no problems with the performance.

The technical support from Microsoft PowerApps is quite good because they respond in a few hours. They provide comprehensive support as well. If you do not buy any support package, SLA agreement, et cetera, and only have a standard license, you are able to raise a ticket with them and they will support you.

The initial setup is very easy.

There are areas of Microsoft PowerApps that can be improved. For example, the license policies are expensive to purchases the premium connectors. If a company would like to use the premium features, they have to pay a lot of money. The Microsoft PowerApps portal could be easier to use when there are a lot of external users because if a company has 1,000 external users, it is too expensive to use the Microsoft PowerApps portal.

I would recommend people to pay attention to not only the documentation of the solution but Microsoft provides a lot of video and text documentation. They give step-by-step guides on how to use different features and how to start and complete the implementation. Microsoft documentation is a good way to start for non-familiar people to Microsoft PowerApps.

I rate Microsoft PowerApps a ten out of ten.

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. 

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. 

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 usability, in terms of low-code applications, is a feature we have found most valuable. We just do development and then distribution.

Improvements to the capturing of geographic locations and integration with maps would raise my score of the product from seven point five to its maximum of ten.

We have been using Microsoft PowerApps for around two years.

So far, the product has shown stability.

The product is scalable.

I am making use of the product in my own company.

I would rate it an eight out of ten.