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 had a new requirement from a business in the clinical domain and the business wanted to identify risk at a study or site level. We created an application using PowerApps, which works well as we usually interact with the SQL Server on Azure.

I did some POC for another application. We’re expecting we'll get it in a new project in the near future. It is a really good tool. We can run programming knowledge, we can learn the PowerApps and we can interact with applications.

It is user-friendly. Anyone can easily learn and work on this tool.

The solution is easy to implement.

It’s a stable product.

Not much coding is required.

I don’t have much hands-on experience with PowerApps. I’d need more time with it. As of now, I can’t think of an area for improvement.

We did a POC with the solution. We’ve used it for the last 12 months.

It’s very stable. It’s reliable. There are no bugs or glitches. It doesn’t crash or freeze.

I cannot speak to how scalable it would be. However, it may work best with a lesser amount of data.

We might have about 100 people on the solution.

I don’t have any experience using any other tool.

It’s straightforward to set up the solution. It’s not overly difficult or complex.

We did the integration ourselves. We didn’t need the help of any consultants or integrators.

I don’t have any details in relation to the pricing or licensing.

The tool was suggested to us, and we decided to try it. We did not evaluate other options.

I’m not sure of the exact version number. However, we are using the latest version.

I’d recommend the solution to others.

I would rate the solution an eight out of ten. There may be other tools that are easier to work with. However, I’m not sure. In general, it works well, and we have been happy with it.

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.

The solution is for rapid application development software.

There is a specific environment, in part a platform of PowerApps, in which you can just deploy the solutions and then you share the link with the users and they are able to open them using iPads or mobile devices, or even a computer.

We have been working to build a maintenance events app for assets, it's an app to manage and show all the assets that have been working or down for maintenance in an operation, inside one bigger mining company. They have many trucks and many other, let's say, machines in the operation and sometimes they have to put these machines just through a maintenance mode, to see what's happening, or to change some part specifically, or even if the machine is having some kind of issue. That's due to the fact that if it's down, they have to manage how long it's down and what was the part that was the issue, the cause of the issue. They have to change the parts and everything's very costly in terms of money for the company when we have one specific asset that's down.

Previously, they were using a board in a room, just to manage all these statuses.  Instead of this, now we have one specific app that is working in live modes in almost real-time. Just getting the data from the services and showing it on a big board in PowerApps can show what's happened, what's the status, and what's the reason for the issue. This app allows for adding some comments. It's a collaborative app where many people can just go there and add comments and notes about what's happening with the machine.

There are many things there that I like about the solution. I like the galleries, which are really powerful. I like the way that we can build forms very quickly. 

In terms of timing to develop, PowerApps is very fast. We can integrate with Power BI. You can just show the Power BI report embedded in PowerApps, and it works really nicely.

In my experience, the solution's deployment can be tricky.

In my experience, it was not good as it was giving errors around the tables and I couldn't find what was happening. I had to break it down into different solutions - one solution containing all the tables and the second solution containing the application, plus the power domain that I had for this particular application. It's something that's not good, in terms of the way that things work. 

When I added Power Automate into the solution, for some reason it disappeared from my Power Automate page, as it was added inside the solution. It was very, very weird. It may be a bug. 

There's a primary interface and integration feature and we build some HL processes there. However, suddenly after adding this part, and automating the solution to deploy it, it was just not available for me anymore and I had to go inside the solution and open the MS files from there instead of the usual place where all the Power Automates are created. It was like a bug and also. In terms of the issues that I have with the solution feature inside PowerApps, I didn't like it. I've seen this too complicated. It's something that Microsoft has to improve.

The speed and performance could be better. PowerApps sometimes gets stuck, gets slow and I don't have any reason for why it's happening. Suddenly you are trying to see the rows on your screen and you just have a wait to get the results back, then there's nothing happening. These things look like an environmental issue, however, I don't know if it's something about the localization or something else.

We'd like our option in terms of licensing that can be paid by the app and not by users. That could be something good. Just the way that they charge the license, it's too much. There are not many options. They could give a little bit more flexibility to choose in terms of options for a license.

I've used the solution for six months. 

It's stable, however, sometimes it is slow.

There are no issues about the connection falling. Just, when you are using it, suddenly the page is broken. There is no issue yet, sometimes it gets a little bit frozen and you're waiting a little bit more time to gather results. The table is not a big table with many, many rows, so why is it taking so long, so much time to get the answer back from the app? That's the main issue. There's a performance problem. It's not a stability question.

It's scalable if we're talking about the database, about data warehouse, however, not about PowerApps. PowerApps is not scalable. It's scalable, in the sense that the app you can share for many users, however, you have to pay by user. Scalability isn't really applicable.

We're still not running it fully. We're just prepared to start testing. 

We've dealt with technical support in the past. 

We had some little situations where we couldn't get the help as we needed, however, that was a limitation in the tool - it was not an issue with them.

For the most part, they are really good.

Positive

IN terms of the initial setup, we have to choose which kind of approach we are going to use in PowerApps, as PowerApps has different strings. You can choose PowerApps Canvas, or you can choose a driving app, and that's a little bit different. In my case, I chose a PowerApps combo as I needed a little bit more in terms of flexibility and in terms of how I build this topic they screen. 

In terms of the development, it's quick, really it's quick, however, it's not the fastest way to develop and there are some other solutions in the market that are faster in some ways. In terms of deployment, in my experience, when you're going to deploy perhaps an application, you have to build a solution and a solution and it's a little bit tricky. You have to add all the components to the solution and, after that, you have to export the solution and import the solution into the production environment. We have an environment for development and a second environment for production.

The application is deployed, however, it's not in use yet. They are just preparing to start testing the application and once they finalize the test, the app is going to go live.

After I passed over all these little issues that I had, it was quick to deploy. It was just a question of minutes. When we export the solution and import the solution back, it's easy. However, all the processes to be able to finally get over these issues and everything, it took me four weeks just to realize what was going on and handle it. 

I was the one that deployed the solution. 

In terms of ROI,  I didn't see any. However, if you look at the cost of building an app, the coding costs would be much higher without this solution. You can save months of development time and the money needed to deploy the solution. In that sense, the ROI is awesome. 

The licensing is restrictive and can get expensive as you have to pay per user, not per app. It's a range of users. For example, if you go above 50 users, you need to pay more. 

If you compare it with competitors like Google, they are more expensive than Google. Google has another option that's a PowerApps competitor called AppSheets and AppSheets is cheaper than PowerApps.

We are Microsoft partners. 

I'm using the latest version of the solution. 

I'd rate the solution eight out of ten.

There are some things that need improvement in some ways to make the tool better. However, it's very powerful and it's very fast to deploy something. It's great.

We use the solution to integrate with enterprise solutions like SAP and other enterprise solutions. It's highly integrated and highly secured. 

Externally or internally, we have several business processes that need to be automated. We write evaluations and also evaluate business procedures to see how they can be simplified. Power Apps is one of the solutions that we mostly use in our company to automate processes. We also have several clients who use it to automate SAP processes. This is the most critical business function in clients' core mission.

It's easy to use. We create great user experiences.

The track-to-use function is great.

It is easy to design automation processes.

The initial setup is mostly pretty simple. 

Users don't have to have any technical competence in order to begin creating automation. 

We'd like to have access to previewed content and preset options. If we could preview content for specific software, that would be ideal.

The user experience could continue to be improved upon. 

We'd like more features and less to no coding. 

I've been using the solution for three to four months. 

It is s stable product and I have found the performance and reliability to be good. It doesn't crash or freeze. 

The solution is scalable. It's also adjustable. 

We have around 200 people using the product.

We do plan to increase usage. 

The product is fully supported by Microsoft. We have a ticket for tracking issues. There's also a community around it that can assist. They are quite responsive. 

Positive

We've also used Blue Prism and UiPath. Since most of the automation processes are based on Microsoft technology like Excel and other Microsoft-related solutions, and Power Apps is based on Microsoft technology and is highly integrated with those solutions, it made sense to switch.

It's a stand-alone solution and uses connectivity to the software we want to automate. It's not hard to set up or to start automating things.

I'd rate the solution a four out of five in terms of ease of setup. It's not overly difficult. 

We were able to deploy the product in about a week. 

We have 50 to 100 people maintaining the solution. 

I handled the implementation myself as I started out using it for testing purposes. I did not have outside assistance. 

I don't handle the licensing aspect of the solution. It's handled by another team. 

It's my understanding we pay around $150 to $200 USD per user. 

We're using the latest version of the solution. 

I'd recommend the solution. It works so well with other Microsoft solutions. It also could reduce the workforce and release employees from redundant daily tasks.

I'd rate the solution eight out of ten.

With Power Apps, we create some of the collaboration forms for our employees to use during the pandemic. We can record our employees' status health daily, and start a database of the information. After that, we can track using Power BI if there are any symptoms or if the risk is low, high, or medium. We use it basically for self-declaration forms.

The solution offers good integration on the Microsoft Power platform. You can use and develop apps, local apps using Microsoft Power Apps. It helps automate processes. We can do the monitoring and tracking of the Power BI app in Microsoft. 

It's very easy to set up.

The solution is stable.

The scalability is good.

The flexibility of the user interface could be better. Currently, they are using the Microsoft OMS, Management System. It would be ideal if we could customize the layout of the user interface.

I've used this solution for one to three years. 

The solution is very stable. We haven't dealt with bugs or glitches. It doesn't crash or freeze. It is reliable. 

You can easily scale the solution as needed. 

We have 500 people that use the solution. We use it quite regularly. We do not, however, plan to expand usage at this time. 

Technical support has been good. They're also very supportive. When we have any problem or issue, we can reach out to them and they will reply.

The initial setup is not complex or difficult. It's easy to set up. It's very straightforward. 

It took us about four to five months to set everything up. The apps vary in how long it takes to develop and release them.

We develop everything in-house. We handled the setup in-house as well. We didn't need any outside assistance. 

We have not yet seen any ROI.

I cannot speak to the exact pricing of the product. We are, however, heavily affiliated with Microsoft.

We're users and Microsoft partners. We use a lot of Microsoft products.

It's my understanding that we are using the latest version of the solution. 

I'd recommend the solution. Everyone would be able to use it as it is not overly technical. 

I'd rate the solution eight out of ten. 

I use it for internal purposes and also to advise our customers. 

Everything that includes PowerApps is very interesting, especially the late editions in direction and mixed reality.  

The way you create applications and the nature of language processing are great. The ideas feature that has been added lately has been wonderful. All these types of additions are really cool.

It's a stable product. 

It uses a lot of AI, which is helpful, especially during the setup process.

The pricing is reasonable.

Technical support is good. 

I'm looking forward to further improvements of what you can do with mixed reality capabilities.

I would like to see more improvement, for example, in direct collaboration. There is something currently, however, it's still on a preview mode. I'd like to see more. 

What I'd also like to see is to be able to use, for example, another tool for sketching mock-ups or the design of the applications and being able to transport the sketches directly into, let's say, a PowerApps container so I can design the app somewhere else, and then I can transport everything in PowerApps designer, and I can get started with inserting logic in the mock-ups that I have already designed somewhere else. This is something that I'd really like to see in PowerApps.

The experience could be a bit better improved and be consistent throughout all parts that form components. For example, the same experience we have in PowerApps is something that should also be in other PowerApps platform products.

In general, the environments in the workspaces are a bit faster than in the cloud.

I've been sung the solution for two to three years. 

It's a stable product.

We have 200 to 300 people using the solution currently.

Technical support depends on what channels you communicate through, however, largely, we are satisfied.

Positive

This is the first general code solution I'm using.

The initial setup is AI-infused. If you start working on an application, AI works for you in the background and tries to provision everything you need. I would like it to be a bit faster. Sometimes the designer just breaks and you get an error notification. 

I've seen ROI and I would rate ROI at three and a half out of five, however, I would like for Microsoft to think of ways where we as partners are better supported to have a higher return on investment.

The cost is fair, based on everything you get. I'd rate it at a four out of five as I see that the customers raise constraints. They sort of say it's a bit expensive. I don't know how expensive the other platforms are, however, from what I heard, it's a fair price for PowerApps considering what it comes with.

We did not evaluate other options. We are a Microsoft gold partner and for us, the journey was set as we were using Dynamics 365 CRM systems, which basically had PowerApps. It was pretty clear from the outset that we were going in the direction of PowerApps.

I'm a team lead for the PowerApps platform in general and PowerApps is the product of the platform. I'm not sure which version of the solution we're using. 

I'd advise others to start with a short hands-on evaluation so that you understand what it looks like when you create on the platform. That will give you a feeling about the components. You get a feeling about what the platform offers and can build slowly up from there. The best way would be perhaps to seek support in the beginning, for example, from partners. If you decide that PowerApps is the way, then consider governance from the beginning on.

There's always room for improvement, however, I would rate the solution an eight 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.