Microsoft Power Apps Reviews

We predominantly use the product for a lot of intake forms. There is a lot of data collection and a lot of intake forms. We use Power Application for validation rather than using spreadsheets. It's good for automation, where we need a data repository of the input, which we get from the resource.

It's extremely user-friendly. It's easy to use. Of course, it's a local tool, however, if you're aware of some of the basic Microsoft products, you can really get on with it. That's something which is really wonderful. 

Even a beginner can set up a Power App and run with it. That's one of the most important features when it comes to the adoption of Power Apps.

The solution becomes easier the set up once you get used to it.

It's a stable product.

The solution has the potential to scale. 

I would like to see some of the connectors which they have right now to be more basic. The ones they have right now, they claim, are premium connectors. They should make that a little more affordable and have it in the free version. Some of the basic databases like SQL should be part of their normal connectors, and it should necessarily be premium.

It can be a bit more difficult to set up the first time.

They have a feature that integrates well with Power BI, however, it is not seamless. We'd like a better, more seamless integration with Power BI in the future. 

They need more of a font selection. If I'm in Excel and I'm using a particular font, I'm limited in terms of which I can use. It should allow for use of any fonts under Microsoft 365.

We've been using Power Apps for the last two years or so.

The solution is stable and reliable. There are no bugs or glitches. It doesn't crash or freeze. 

It is scalable if we integrate with other applications like Power Automate and connect it with some other applications or some other databases like SQL. That said, in the current arrangement with SharePoint, we have some limitations. The moment the data increases, if we're able to integrate Power Automate, then surely it becomes a scalable application. Right now it can be scaled, however, it's not something that we are looking to do. 

There are maybe 60 to 70 users at this point of time actively giving us data, however, there could be other applications that people are using.

In terms of technical support, we do have a governance team. The IT governance is a security team who helps us navigate through issues. We raise requests internally within our organization to help us see where the issue is, and they will escalate as required. They might reach out to Microsoft support to kind of get it sorted. That said, we have not found any major issues so far. If we do, our internal team is the first team to go to.

We previously used mostly manual consolidation using Excel, emails, and things like that. There was no other tool before. That said, we used normal Office productivity tools like Excel and Outlook. We went with Power App since we were already using Microsoft and Office 365, which helps us to integrate multiple other Microsoft solutions. That's the reason we thought Power Apps would be the best way for us. It also integrates with SharePoint and is easy to build in. 

The initial setup was not straightforward, however, once you get a hang of it, then it's pretty simple to create things. From a documentation perspective, it's kind of a good guide that they have as far as Power Apps is concerned. It's easy to get started. Like any tool, you have to spend some time understanding and navigating around it. There is just a normal learning curve that is required as with application. You won't really find it that difficult if you are ready to invest the time to learn the tool. There's a moderate level of complexity.

It was not that effort-intensive, yet it definitely took us close to three weeks to create our first app on Power Apps, which was mostly SharePoint driven and had pretty decent complexities. It was not a very straightforward application. It took a fairly decent time. It was not a very long-term project, it was short-term, and we could manage to do it in three weeks.

We have not found it difficult to maintain Power Apps. It's pretty straightforward. We haven't had any challenges so far.

Everything was handled in-house. 

Right now, we are using an enterprise license without the premium connectors at this point. For Power Automate, we are definitely going to need some licenses which we're exploring. 

Depending upon the user requirements, we're still exploring the licensing requirement. Most of the applications that we leverage are without any cost other than the normal license which we are paying for as part of Office 365. We'll take additional licenses depending on the solution and the need.

We have performed a lot of other projects on the Power platform, which is a Microsoft product. So we have used Power App and Power Automate to do many of our automation initiatives.

We are working with the latest version of the solution. 

I'd advise potential new users to have the UI designed well in advance. Articulate the flow in which you want to create your Power Apps so that you can save time. Then, do a dry run using Excel as well. It's important when you're using Power Applications, to have your UI design and the BRD clearly articulated, otherwise it might take a little longer to implement Power Apps. Once you have everything in readiness, it will be easy. 

I'd rate the solution eight out of ten.

We use Microsoft PowerApps for very small use cases. For example, conducting internal surveys, or say some of the key business stakeholders want day-to-day reporting. Using PowerApps, we are creating such reports for those executives.

We connected PowerApps to the relational database, which generates the report. 

Also for contract review and approval of these types of use cases. Those are, in my opinion, very simple use cases. There are no complex rules or decision-making processes, which is why PowerApps was designed.

It offers integration with several Microsoft products, including SharePoint and Outlook, in my opinion, is a huge plus. 

It can also integrate with Microsoft SQL servers, which makes it easy, and you can send reports and create business applications from it.

In terms of workflow automation, I believe that capabilities for creating the entire business process are required, or, at the very least, the option to model the business process, define complex business events, handle them, and route them to appropriate business stakeholders.

Those, I believe, are the critical areas that require improvement. 

For the time being, it is only an application development platform. I am not counting a business processing management platform, only working on capabilities with business process management.

It is extremely stable. 

The apps that we created were not particularly complex. We did not thoroughly test PowerApps to determine their true capabilities. It was similar to tactical applications built as part of the POC to ensure what capabilities of the PowerApps could be used.

It was not used for any critical business application.

I believe it should be scalable. 

However, in our organization, we only have approximately 15 to 20 people who are currently using it.

The initial setup is straightforward. It does not take long.

Maintenance is minimal. It is only one or two people who keep it running.

I believe it simply depends on the complexity of the business process. If you are serious about implementing a complex business process, I believe you should use a platform like Appian or Pega.

In terms of low code automation, I believe those two platforms are quite mature. They also develop capabilities such as robotic process automation and process mining. That's where the most value is because business users don't just want one thing; they want several things at the same time.

I believe it is preferable to use a platform that is robust in nature. Appian and Pega, in my opinion, would be better for them. However, if you only have a simple application that does not require much scaling, I believe you can use PowerApps, such as a simple three or four screens or forms. That should suffice for Microsoft PowerApps, in my opinion.

We are Microsoft partners and resellers.

I would rate Microsoft PowerApps a seven out of ten.

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.

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.

We're not in production yet. We're still very much in the early stages of this solution.

The cloud aspect has been great. We don't have to do a lot of research in order to begin integrations. It's so easy to integrate with other solutions.

The solution works well with Microsoft Teams. We used to use Skype for Business, and now we rely on Microsoft Teams Enterprise E5. 

There's great integration with Dynamics 365, Office 365, and more. It's great that everything is easily connected.

We can use the solution from cell phones, tablets, or computers. It works on every platform and in every environment. 

The solution does work a bit differently on cell phones and tablets.

We still have information on our SQL server and we need to migrate things over. The timing of doing that is going to be a little tight.

We're not in production yet, so we're still working through some issues. However, by the time we are in production, I'm confident this solution will be ready.

I've been working with the solution for about six months at this point.

The stability of the solution is quite good. Of course, if we run into any issues, technical support is right there to help us, and they are very helpful.

We have more than 1,500 users in our organization. There are other users that will also be able to access the solution from the outside. With this particular solution, in terms of maintenance and direct work on it, we started off as a team of four, however, now we are a team of ten. We needed some more people to maintain the surrounding software. However, overall, it's been good.

We're not a small organization. We're pretty big. It's easier to focus on smaller projects rather than trying to implement something that's large scale.

We've found the technical support to be very good. They are always right there, ready to assist. We can open tickets 24 hours a day. If they are critical, they are dealt with quickly.

Our company is quite large. With 1,500 or so people, changes take a while to implement. It's not like a small organization where you can do everything quickly. You need to make sure people know how to use it.

In general, the full deployment took a few months.

I don't have too much information on licensing It is likely per application we use, or per machine. I don't deal directly with billing and therefore don't have the exact pricing.

We have a very good and very close relationship with Microsoft.

I started working more on PowerApps as we were making a comparison with Salesforce. We decided on PowerApps mostly due to the fact that Salesforce would not work. 

We have to maintain our current environment, so at some point, it's not that we are 100% in these new tools. Right now we have more than 60% of our time in these new tools and try to not develop any coding. We do make some code in JavaScript, however, it isn't too much.

It's a good solution. There is some coding needed for customization aspects, however, it's a pretty solid product.

There's still a lot that I need to learn about the solution. Therefore, currently, I'd rate it at a seven out of ten. We're not in production yet, and therefore it's hard to gauge many aspects of the solution.

From an architecture point of view, the architectural criteria are the most valuable aspect of the solution.

The solution is quite stable.

The product integrates well with other Microsoft products.

Technical support is very helpful

The initial setup is not complicated.

Microsoft is not cheap. The pricing could be lowered for their customers.

It's not easy to integrate the solution with other products that aren't Microsoft-related.

I've been using the solution for about two to two-and-a-half years.

The solution has proven to be quite stable. There are no bugs or glitches and it doesn't crash or freeze. I find the solution to be reliable.

We have about 1,000 users on the solution currently.

Technical support has been very good. It's definitely helpful. We are a big, big, big company. We have a relationship with them, and we find that the service is good. We get pretty much good support from them. We're satisfied with the amount of attention we have when there are issues.

We also use Appian. We use both products simultaneously.

The initial setup was very easy and quite straightforward. I would not describe the process as overly complex or difficult. A company shouldn't have any issues with the implementation.

We have a Microsoft partner we deal with. They assisted us with the implementation.

The pricing could definitely be lowered.

We pay an annual license fee to Microsoft. We do not pay monthly.

I cannot speak to the exact cost our company pays yearly in order to be able to use this product.

We have a Microsoft partner that we work with.

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

I'd advise people to consider working with the product. It works very well with the other products of Microsoft in general and integrates with Microsoft Teams and other apps, which is helpful if you use a lot of Microsoft. I'd highly recommend it. It's easy to integrate.

Overall, I would rate it at a seven 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 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.