Microsoft Power Apps Reviews

It's for building custom apps, which is very similar to APEX. We also use it to build small business applications related to any Microsoft products.

In Power Apps, it's the native integration with Microsoft products. This is definitely the most powerful feature.

There is always room for improvement in stability. 

It was three years ago when Power BI started to develop. But for Power Apps, we have a special center of excellence, and I am not part of it anymore because it's too bothersome.

I would rate the stability an eight out of ten. There is always room for improvement. 

I'm not aware of any issues with Power Apps' scalability because maybe we didn't use it so heavily.

I personally never used Microsoft support, but based on references from other colleagues, they're quite satisfied with the Microsoft support team. 

We had some cloud-based platforms for development. Microsoft Power Apps is a low-code application. One of the beauties of Power Apps is the fact that it's low-code, so you don't need high-skill development experience to build. This is my opinion.

The initial setup is straightforward. From a setup point of view, I know that Microsoft provides quite great capabilities.

The deployment time varies and depends on the environment. It's a cloud solution. It's a private cloud, part of the Microsoft 365 tenant.

I would rate it a seven out of ten. It's stable, reliable, and easy to implement.

Microsoft Power Apps has quite great AI capabilities. They can embed the functionality of Copilot, and all the AI capabilities of Microsoft 365 can be easily used in Power Apps, as per my knowledge.

We are a construction company, and we use the solution for a lot of project management tasks and to make some relevant tools for the business.

The solution's most valuable feature is integration. It's highly beneficial because you can bring data from many different places to it. It's an easy, pluggable solution that everyone can use. It can make a very user-friendly solution, and you can show your data from it. The solution has a new, modern look and feel and is integrated with Microsoft Power Automate and AI technology.

Microsoft Power Apps must be more robust when integrating with Microsoft Power BI. It should be a more connectable solution so that it works in a better way.

I have been using Microsoft Power Apps for five years.

Sometimes, the solution faces network failure, slows down, and does not fetch things correctly. It has some limitations in showing the number of data, which is understandable since it's a low-code tool.

I rate the solution’s stability a six out of ten.

I think the solution's scalability is growing faster, and it was a long wait for such a tool with Microsoft. It's been improving for the last five years, so the progress is good, and people are using it. People like the tool because it has good scalability. More than 1,000 people are using the solution extensively in our organization.

I rate the solution’s scalability a seven out of ten.

We raise a ticket through Microsoft for any issues. Sometimes, the support is good, and we get call center support. Other times, we have to fix the issues ourselves. The technical support from Microsoft is not consistent.

Neutral

We previously used Microsoft .NET, which took many months to develop the system. We switched to Microsoft Power Apps because it is easier, requires fewer people, and requires less time to deploy.

The deployment time depends on the situation, but deployment is pretty easy. You can fix things and deploy the tool within two hours. We have different environments from test to production. We move, set up a package, deploy the package, and change the connection strength. Around two to three people were involved in the solution’s deployment.

On a scale from one to ten, where one is difficult and ten is easy, I rate the solution's initial setup a seven out of ten.

We implemented the solution through an in-house team.

The solution has helped grow our organizational value by converting tasks from manual to automatic.

Microsoft Power Apps is not an expensive solution.

On a scale from one to ten, where one is cheap and ten is expensive, I rate the solution's pricing a five out of ten.

I'm a consultant and a customer of Microsoft Power Apps. The solution is automatically updated, and I'm using the recent cloud version of Microsoft Power Apps. Two to three people are enough to maintain the solution. Microsoft Power Apps supports our mobile workforce or remote operations well.

Overall, I rate the solution seven and a half out of ten.

Initially, we used it mainly to wrap up Power BI reports for BetterView, creating very simple apps. About a year ago, it evolved into more robust apps for collecting information, particularly for logistics. We developed apps to streamline workflow and gather data for specific operations. We then built a more advanced app that allowed us to communicate with customers—connecting workflow issues, creating problem reports, and sharing shipment updates via SharePoint, which integrates easily with Microsoft Power Apps.

Currently, Power Apps is used mostly locally, within one or two departments. Each app is developed locally, and it’s not really used for enterprise-wide purposes. In our organization of about a thousand people, around six people are developers working with Power Apps. There are likely a couple of hundred users in total across all apps.

Over time, it became a key part of our operations, and we've developed around three or four apps in total. However, the main use case remains displaying Power BI reports. By wrapping reports within Power Apps, we can present them in different formats to create better dashboards, making the process more efficient.

In my experience with Microsoft Power Apps over the past two years, the best feature is its seamless connection with the Microsoft ecosystem. It integrates well with Microsoft Teams, and you can use it with minimal programming, which is typical for low-code and no-code apps.

A downside is that Power Apps is primarily designed to work within the Microsoft ecosystem. It’s not suited for publishing apps outside of the network, so you need additional Microsoft technologies for broader use. While it’s very scalable for simple apps, it's not ideal for large-scale enterprise applications.

I’ve been using Microsoft Power Apps for about two years.

In terms of pricing, Power Apps is cost-efficient.

Overall, I’d recommend Power Apps for its ease of deployment and supportive documentation. However, it's not suited for complex, enterprise-wide applications. I’d rate Microsoft Power Apps an eight out of ten overall.

We use Microsoft Power Apps to support some IT processes and for employee evaluation. Sometimes, we use the solution to prepare electronic forms where we cannot use Microsoft Forms. We also use Microsoft Power Apps to prepare small custom applications.

I like the solution's ability to approve some tasks electronically. When we use Power Automate to build workflows, one of the steps is the approval process. It is very convenient to have the possibility of accepting some activities.

Because we have a lot of data and users, achieving an appropriate level of security and privacy is sometimes difficult, especially for sensitive data. I do not mean that the system is lacking in this area; rather, we need very competent people. I believe we don't have enough people to appropriately secure our data and control the transfer of this data.

I have been using Microsoft Power Apps for three years.

I rate the solution a nine out of ten for stability.

I rate the solution’s scalability a nine out of ten.

In some cases, it's very difficult to get very competent reactions from the support team regarding our tickets.

Neutral

The solution’s initial setup is easy.

We have seen a return on investment with Microsoft Power Apps regarding time savings.

On a scale from one to ten, where one is cheap and ten is expensive, I rate the solution's pricing a six out of ten.

Microsoft Cloud can integrate with on-premise infrastructures, but this requires additional licenses. These additional licenses are expensive for us because we have 8,000 employees. Integrating cloud services with on-premises systems is not easy for us. This is mostly not because of technical problems but because of the cost of such integrations. I would recommend the solution to other users.

Overall, I rate the solution an eight out of ten.

I use Microsoft Power Apps and some other tools in my company. Sometimes, we use just Test Studio. In general, we just use Microsoft-based software in our company.

The solution's most valuable feature revolves around its low code capabilities. Coding work is less in the tool.

The controls are not available in the tool by default, so it needs to upgrade their controls, like gallery controls and some other controls, so that they can be made more usable.

I have been using Microsoft Power Apps for more than ten years. I am just a user of the tool.

The tool sometimes fails because of connectivity problems or something, but it is generally stable.

Depending on the users or according to projects, my company secures the tool's licenses, and we use it. Around ten people use Microsoft Office 365.

The product's initial setup phase is easy.

The solution is deployed using Azure's cloud services.

The tool is neither cheap nor expensive. The tool's cost is manageable.

I recommend the product to those who plan to use it.

It can be easy for a beginner to learn to use the tool.

My company uses the product with AI features, and it is easy to use.

I rate the tool an eight to nine out of ten.

We use the solution to implement new Teams apps. Some customers want apps on every mobile phone in their company. This is implemented using Dynamics or SharePoint, with a list of plan data displayed on the mobile phones. Everyone enters the data and plans when holidays or machines, like magnetic resonance scanning machines, are to be used. Everyone enters this data and coordinates using that Blackboard application. It is for enterprise resource planning or HR planning.

Microsoft Power Apps is the building block for creating applications, similar to how children use different types of blocks to build structures. 

Power Apps is a part of the Microsoft Power Platform suite, enabling users to build custom applications using various components. It is more akin to SharePoint in creating web pages and applications. It allows integration with SharePoint, connected web services, data files, and more.

You need to be familiar with Microsoft Power Apps' infrastructure. If you understand Power Apps, it becomes easy to use; otherwise, it may seem challenging. SharePoint can be a complex product, but if you have someone guiding you or showing you how to use the apps with online checkpoints, then it becomes much easier.

To utilize Microsoft Power Apps effectively, it's essential to grasp its integration with SharePoint. I recommend considering a structured course instead of relying solely on YouTube videos, which can be time-consuming. Whether managing a Spanish restaurant, an Indian restaurant, or any other business, investing in formal training is crucial for efficiently getting your business up and running. This approach saves valuable time compared to piecing together information from scattered online sources like YouTube or random articles across the Microsoft ecosystem.

Microsoft Power Apps allows companies to efficiently manage and utilize measurement or scattered data in competitive environments. While existing solutions are available, understanding how to leverage these solutions effectively is crucial. Power Apps provides an intuitive interface to seamlessly implement measurement data from an open environment such as a bakery or similar establishments.

Microsoft provides excellent technical support. They are known for their competence and respond within a few business days.

Positive

The solution usually takes half an hour to start. However, getting the simple apps running might take days, and some alerts take one or two days. The most difficult part is accessing the data needed within your ERP or HR system.

The license costs around 20$ per user per month. While it is an expensive piece of software, users are willing to pay for it.

SharePoint has been used since its inception in 2001, leveraging web service proxies and the initial framework where any web service could provide authenticated and authorized access. Custom connectors are required to access data. The connected infrastructure does not significantly affect the authentication and authorization requirements. This flexibility allows seamless integration with infrastructures like Google, SharePoint, SAP, and others.

It allows you to integrate ideas like viewing the inventory of used machines or any other inventory-based business scenario. These apps can be accessed on your mobile phone or laptop and displayed within Teams, making them interactive. It serves as a versatile platform for various business logic needs. Additionally, you can build and program apps without Teams using a standard browser, though many customers prefer using it alongside Teams.

It is a development environment that simplifies application creation, though, like any programming, it is susceptible to errors. When integrating systems such as banks, credit card companies, or health insurance providers, ensure proper authentication, authorization, and accurate data transmission. Understanding the origins and significance of your data is essential, often requiring collaboration across departments to align on business data definitions—a resource-intensive process. Developing sensitive applications in such environments can be challenging, especially regarding data protection compliance.

I recommend Microsoft Power Apps to small businesses, such as Spanish restaurants. If you have a small medical practice, like a dental office, you might experience regular service issues, especially in Germany. However, despite these issues, if you need to store data and to interact with it using mobile phones, I recommend Microsoft Power Apps.

Overall, I rate the solution a nine out of ten.

We use the solution for collaboration modules within our company. For example, we use Power Apps to handle requests when investing in projects abroad and needing approval.

The solution integrates quickly with our organization's existing systems.

We're running a campaign to encourage users to utilize the Power Apps. This is particularly challenging as we incur licensing costs, and some individuals do not use the applications.

I have been using Microsoft Power Apps for three years.

There were no stability issues.

250 users are using this solution. We have some projects for next year that we will use to increase the usage of Power Apps.

When we need support, Microsoft helps us immediately.

Positive

Deployment is easy and takes three months to complete, depending on the project. When we start using their programming, they understand easily and faster.

The solution has increased productivity due to automation. We can automate and save 30% on costs. Power Apps allows us to allocate or invest time in other activities when the apps handle certain processes.

The product is cheaper.

The solution's maintenance is easy. It is easy to use, understand, and manage.

Overall, I rate the solution a ten out of ten.

We use the solution to create applications. We were getting ideas, fine-tuning, and putting them in different queues that are available to the whole organization.

We have been utilizing the tool for very long. We can easily build a very small application or a large database with the tool. It also provides integration with SharePoint. Anyone can easily build a very basic application using the solution. If anyone wants to create an application to put SharePoint lists, it can be easily built using the product with a few clicks by any user.

The product's usability and the ability to fine-tune are really good. It is easier to work with compared to AgilePoint. The product is very user-friendly.

The solution must provide more integration with third-party applications.

I have been using the solution for the last eight to nine months.

The solution is relatively more stable. Loading is also good. It gets a little slower when we load large amounts of data sets. However, it is good when it comes to downtime.

The solution is very scalable. I rate the scalability an eight out of ten. Around 50,000 to 60,000 people are using the solution in our organization. It is accessible to the whole organization.

I did not contact support because I could get most solutions to my problems on Google.

The solution is deployed on the cloud.

The tool is not that difficult to maintain. We have a separate support team taking care of maintenance. The team works on tickets and closes them. People have built many applications using the solution.

Power Apps is relatively cheap compared to other low-code and no-code systems like OutSystems and Mendix.

Power Apps is more scalable than AgilePoint. It is also easier to deploy things using Power Apps. We can use the tool to deploy smaller solutions without much coding knowledge. If we use Microsoft products like SharePoint, we can integrate them easily with Power Apps.

There are buttons available in SharePoint that enable us to create and publish an app with just one click. The documentation on Microsoft's site and the learning platform of Power Apps is good compared to AgilePoint. AgilePoint has limited videos because it does not have a large working base.

The tool is good. People should definitely try it out. It can be a perfect solution for the whole enterprise. Overall, I rate the product a nine out of ten.

The one that we currently have is only to SharePoint Online as we want to be able to have analysts be able to maintain data, and we want a graphical user interface, a GUI front end, to do that. Especially if it's interfaced with PowerBI, it allows analysts to have a research tool to identify what data needs to be updated right there, and to then be able to do that through PowerApps is a huge benefit. Right now, we're only able to write back to SharePoint Online.

Right now, it's only write-back to a SharePoint Online list, however, I have proof of concepts. I've got a business case that I'm currently trying to get pushed through. I've got other services within our organization that I need to get buy-in from so that we can get this business case approved and get the funding.

The write-back capability right now is just SharePoint Online, however, hopefully, we'll get the funding and subscriptions so that we can get write-back to our SQL server database. Of course, this is for our analysts within business architecture so that they can maintain the metadata, the relationships, and the mappings. Those are the biggest things that we need to have analysts able to do - the research, analysis to identify what data needs to be updated for those relationships and giving them a front end, a form to go in and edit, either create rows or modify existing, whatever needs to be done to the table.

We're one of the administrations within a governmental organization and I wish that they would make it and just provide it to those environments that are still on-premise for their relational databases, which we are. We're stuck on this on-premise environment, however, we don't have the premium connectors subscriptions for those. It's something we require.

As far as dealing with SharePoint, it'll allow you to ha manage up to 2000 rows, however, performance-wise, they're recommending that you just keep it at the default of 500 rows. Beyond that though, I don't know too much about its limitations. Having to do export and import from SharePoint Online and then in the SQL server, the solution is obviously there, if you can get the premium connection.

I'd much rather have the gallery set in a tablet or a normal computer, more of a landscape setting than what you would think you would see for a cell phone.

We just started pursuing the solution with our write-back capability. We have not used it for more than three months. We've actually put a proof of concept together.

The solution works great and is stable. My obstacle is being able to demonstrate it and show its value to other leaders within the organization. I don't have issues with it crashing or freezing, for example.

While we're still in the early days and need to develop it more, I'll be asking for 30 subscriptions initially. Within business architecture here, we're probably going to be somewhere between 10 to 15 analysts. Right now, we may only have ten as we are still building the business case.

It's unlimited where you can implement this. The scalability just depends. With the continued support within an in-house setup, you can make it what you want. It's my understanding that the scalability is really unlimited.

We have an office within OIT and they have office hours. They've got a site, however, it's specifically for PowerBI. I don't know that there has been a whole lot of movement to get support for PowerApps, maybe since the value hasn't been realized we haven't really explored support options.

If more people saw how you could utilize PowerApps integrated with PowerBI to maintain data, we might have more questions and need more support.

BISL is the name of the support group we use. They have weekly meetings and office hours and are more focused on PowerBI. They've got a contract with Microsoft personnel that support this BISL team and specifically PowerBI. I don't know if they're going to expand that level of support and also include PowerBI. I would hope so. 

We used asp.net. The main platform we are using has asp.net, Cascading Style Sheets, CSS, Hypertext Markup Language, HTML5, jQuery, and JavaScript Library. It's a high code solution. Having to put an IIS web and app server and develop all this and HTML and C# and all these other languages that you would end up having to learn, it's a huge learning curve compared to putting something together in PowerApps. The learning curve for PowerApps for whatever you're trying to do is going to be under two weeks, whereas trying to learn ASP.net, that environment and all the other suite of stuff that you have to have and get resources too and all that, you're talking months. There are a lot of costs involved when it's so high code, and a lot of time. Using PowerApps would save time and money. There's also the risk that if the person you assign a task to goes away, you lose all of their work or cannot continue it. 

There's a learning curve with any new tool, so it's going to be somewhere between a three and a four out of five in terms of ease of setup. It just depends on the person's experience and working with these types of tools, as to how well they understand and are able to work through that.

Once you have a concept of what to do, I'd say it takes less than two weeks to implement. With that initial building out of your very first PowerApps set of forms to accomplish what you're trying to do, you're going to tweak and enhance in the end. I just put this filter or search capability and sort capability on a couple of columns. Implementing new features and adding additional buttons, et cetera, will be something you are going to be doing along the way. You're going to continue to enhance it when you discover new capabilities you want to implement. It's a work in progress to roll it out and it's continual. That said, for the initial rough draft of something, from concept to actually putting it together, it's going to be just a week to maybe two weeks to do.

There is a learning curve for the initial cost of doing it. That said, I would definitely consider this a low-code job. It's definitely not high code. There's low to mid-level coding involved.

We're very limited in terms of users for deployment and maintenance. Staff within my office that would actually develop the PowerApps forms and implement and train up the other analysts are only going to be somewhere between three and four. They are program analysts themselves. They aren't IT.

We handled the initial setup ourselves in-house. We didn't use any outside assistance.

We have not yet witnessed any ROI. It is early days. Not until we're really up and running with it will we be able to look at that aspect.

That said, if I were to compare it to other solutions, I'd rate the potential for ROI five out of five. The workload and what you save on manpower will likely be impressive.

We're a federal entity, so we've got a government rate, and this is per user, which is unlimited apps for PowerApps. 

Typically, it's $20 per user, per month, commercial. For the government,  on a per user basis, what we were looking at is $11.23 per month.

I'd rate the pricing five out of five in terms of affordability. It's way cheaper than the commercial price. That said, I know if that's just an introductory price to get you into it. Then they're going to boost the price up. It won't stay at $11.23.

I'm not aware of any other costs above and beyond the licensing. 

We are a customer and end-user.

We're likely using the latest version. We just started using the product a few months ago and then we likely also have the IT team keeping everything up to date. 

I'd advise new users to not be in an on-premise environment; be in the Azure Government Cloud.

I'd rate the solution ten out of ten. 

If you're looking for a GUI front end to maintain your data, that interfaces with PowerBI, this has to be up there in terms of best options. And the learning curve is low. It is very compatible with whatever you're doing in the Power Platform environment.

We have built a couple of apps ourselves, but mainly, we are building the apps for our customers.

The best aspect of Microsoft Power Apps is its time-to-market efficiency. Unlike traditional programming, it doesn't involve lengthy coding processes, allowing for rapid deployment. You can input your requirements and get started without writing millions of lines of code.

The product is expensive. It costs around 20 euros per month.

There is no stability concern from clients. It could be faster, but it's stable. When it is on your infrastructure, it takes more time to work than the public cloud.

Microsoft support is not solving your problem. They're closing the ticket and telling you to open a new ticket. When you're writing back, they're not answering. When you are calling, they don't hear you. Microsoft support is the cheapest support.

The initial setup is easy because you don't need to write a million lines of code.

Microsoft Power Apps runs only on the cloud. There is no on-premise possibility to run it. You can run a connector connecting your on-prem infrastructure and the cloud. We are developing on Azure Active Directory. We're also using it because our clients also use Azure. We have big and small Azure clients. Everything is in the cloud.

If you have a Microsoft 365 subscription. You already have access to Power Apps. You can utilize pre-built apps and even create your own without needing additional data apps.

The solution is fast to adapt.

Overall, I rate the solution an eight out of ten.