Microsoft Power Apps Reviews

My primary use case for Microsoft Power Apps are mostly demos for my customers and in trainings. I am a Microsoft Registered Trainer.

The most valuable feature is the completeness of the concept. It is not restricted by where you are allowed to use it and that is its greatest strength.

There is room for improvement in error handling and debugging. I would appreciate it if Microsoft created something like the social network graphs Facebook sometimes shows you (potential connections). It would be great for Microsoft to take a similar point of view regarding the data and data flow in Power Apps. It would help us see which field is changing and which is influencing the follow-up field or display or workflow, etc.

As a chief financial officer, I would like to see the mark of chain retracement and where the money flows. Imagine dropping a little drop of ink onto a handkerchief and seeing the ink sucked into the fibers of the handkerchief and distributing itself. Similar things happen to money if you put it into a small market and a chief financial officer needs to have that information. 

I have been working with Microsoft Power Apps since 2018. 

Microsoft Power Apps is definitely stable. It is as stable as SharePoint and this app model has been in place since 2013. Essentially, it requires you to put code onto a SharePoint site which is not executed there, but rather on a client or on specific workflow codes, which are client. If code executions are well work-flowed, it is capable of saving your script and of the global resources. That capability to take off where you left off, including external resources, is a great strength.

Microsoft Power Apps is scalable. SharePoint is a farm. It is a big forest of machines interconnected by a messaging system, Windows Azure Service Bus. It can be understood as a telepathic network between the machines. As long as one machine is running, the system's running and as soon as more machines are adding the capabilities, the load is distributed automatically.

Microsoft's technical support is at a high level. 

We did previously use a different Microsoft workflow operating system, but it was complicated to program and difficult to provide interactions with the users. All of that is much easier now that we use SharePoint platforms like Teams. Microsoft has the best of all worlds. I am confident that it will rock the market.

I have an MSD end subscription; it's a flat rate subscription.

My advice for anyone looking to implement Microsoft Power Apps is: please have a closer look at the Azure infrastructure and do not underestimate the complexity of Azure Active Directory and SharePoint. I recommend spending a week or so letting someone informed like me introduce you to the complexity of Azure Active Directory, SharePoint, and Windows Azure. Not having this information is like driving a car without having put oil into the motor and air into the tires. In other words, it would not be wise.

We use Microsoft PowerApps for the typical use cases including website creation and a work portal, covering all the operations involving the manufacturing side of my customers.

There are three app-building interfaces available in PowerApps. Canvas is model-driven. Power Pages, which was Power Portal, which has more low-code, no-code capabilities and makes web design easy for the everyday user to create a website. Lastly, Power BI reports, or Microsoft DataWorks, which we have integrated with our data provide us the option to work collaboratively.

Most of the people in our organization using this solution are business people. They are not experts in technology and are not familiar with how to use the application. They use Excel and other documents to collaborate. Moving Excel to the application helps them access different data sources. It allows us to provide all the information in one single place. Everyone can view the data based on their role or access level.

The most valuable feature of Microsoft PowerApps is the ease of use to create an application. For example, if you use the Canvas app, there is a feature that you can upload an image, and it will easily identify it and convert it into the application.

The solution is convenient for using Power Effects so we can write customized business logic.

Microsoft PowerApps is not responsive in nature. For us to make an application responsive, it requires some effort. We need to work with CSS, HTML5, or JavaScript.

I would also like to see improvements made to the integration with other data sources, including Azure Databricks or Spark. When we connect from DataWorks, CDS, SharePoint, or OneDrive where the actual Excel file is kept, it is easy. However, if we connect with other data sources, we need to do a no-data filter, particularly when there are in-built integrations available. 

Out-of-the-box connectors, like dataflow, would help to load the data from those data sources into CDS.

For future releases, Microsoft PowerApps should add more templates that help bring more experiences to the websites.

I work as an IT analyst. I have been using Microsoft PowerApps for two years.

In our organization, PowerApps is used by program managers, IT engineers, IT analysts, assistant consultants, and delivery partners.

The initial setup of Microsoft PowerApps is straightforward. 

For deployment, we use the ALM CoE kit, and GitHub through the pipeline. It is done through the team, creating a Dev environment for each pre-Dev and production environment. When we have completed testing and validation, we proceed with staging and then production.

We have not implemented using an automatic deployment through Azure Pipeline as there are a lot of bugs. We are still doing the implementation manually.

Deployment is done by our customers' teams. They are handling the pipeline activities.

The ROI is always positive. Our customers who use this solution can quickly create and circulate through a group. For example, for an innovative idea, you can create an idea zone, QC, or something similar. You can create a form and circulate it via email through PowerApps.

PowerApps has been adopted by all major partners and Microsoft is widely used. We use Microsoft Teams to collaborate. You need to have licenses. E1 plus Intune or E1 plus licenses is enough for everyone to use PowerApps as it's free, even if you are using data sources like SharePoint.

If you want to deploy something with RPA or Power Virtual Agents, you will need to think about the licensing model and the capabilities of the AI builder. AI can deploy the AML model, so you can use the capabilities, meaning you need the licensing.

For an organization looking to implement Microsoft PowerApps, they should consider the timeframe required and the experience they would like. 

Responsiveness is a concern with PowerApps. If you want to build an application for your desktop, tablet, or mobile, the application needs to be responsive on all screens. PowerApps is not responsive to these requirements. If responsiveness is not a concern, then I recommend this solution.

I would rate this solution a seven out of ten.

We use it as part of our analytics offering. We are basically into analytics. Maybe sometimes we use it to build small apps to instrument the research process. That's what we do.

I am from the sales side, so I really do not know the technical aspect of it.

It's my understanding that it has been issue-free.

We have pretty easy integration options.

Technical support is great.

The solution is stable and reliable.

The scalability is good. 

I don't have any notes for improvement. It does what it says it does. 

We'd like to see more integration capabilities in the future. 

We've been using the solution for about three years. 

The solution works well. It's stable. the performance is good. there aren't bugs or glitches and it doesn't crash or freeze. 

We use it for a very specific purpose, and therefore scalability is not really a factor for us.

We have about ten clients using the solution currently.

Technical support has been fine. We are satisfied with their level of service. 

We use the cloud version of the solution. There isn't an in-depth deployment process. 

We handle the projects and the implementation for our clients. 

I don't have any comments on the cost or licensing. It's fine. It's cheap compared to other RPA tools. It was about $40. There are people that are lower than that, however, they don't give you the features.

We use a lot of Microsoft products. We use Microsoft Power BI, Power Platform, and Azure Patch Solutions.

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

I'd recommend the solution to others. 

I would 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. 

We are user integrators and partners with Microsoft. 

One of the valuable features of PowerApps is the ability to generate QR codes and scan barcodes, as well as take an image. Integration is good; the solution is low code and easy to deploy. It's great that you need to create a unique verification, it's a feature that helps a lot. 

We had issues with the syntax during the build. Writing quotes could be simplified. Customization, in general, is somewhat complicated.

I've been using this solution for a couple of months. 

As with most Microsoft products, it's scalable. We recently deployed in a company in Burundi where they have 50 users. It requires two, sometimes three people for maintenance. Once the solution is set up, there's not much required. We'd like to scale nationwide but it ultimately depends on the cost. 

I haven't had contact with Microsoft support regarding this product. 

I think for the first-time user, the initial setup takes more time. Other tools like Automate are easier to deploy. PowerApps requires so many things to click and customize, it's really detailed. Building the system takes a little bit more practice than with other solutions. The deployment was done in-house and we had a couple of people working on it. The implementation took about a week. 

The solution is quite expensive because if you have, say, 100,000 users or more, that can add up. Licensing works on a tier system but I don't have the details. 

Building is the simple part of this product, it's the costing that needs to be checked. It can often be overlooked when you build a solution. 

I rate this solution seven out of 10. 

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.

Microsoft Power Automate is primarily used to update some legacy systems for our client, as well as government compliance systems and web-based reporting systems that don't have APIs. Microsoft PowerApps has the same use case. It's the front end and is the part that is interacting with the client and interacting with the collected data.

We really like Microsoft PowerApps. When compared with Microsoft Power Automate, it is a bit more mature, and we're able to build things pretty rapidly.

It's a different paradigm to build around, and it's a different programming paradigm. It's more like Excel in that you build formulas and pieces, but we've been able to build some fairly sophisticated business logic inside of it. As a result, we believe that is much more mature. I'd say that's around an eight, eight and a half, out of ten.

I believe, Microsoft PowerApps is still in its early stages. I believe it is far more mature and integrated. I would say the programming language, because the drag and drop, low code, no code, its nice to get started, but you really want to be able to work as a programmer with an IDE and real code, and we've been able to start to do that a little bit and integrate a lot of JavaScript with RPA, with Power Apps I haven't been able to do that. I believe there is a way to do it by putting the data into Git. I just haven't used it yet, and haven't needed to.

As it's a cloud-based app, the development environment has some really nice parts and some that are a little clunky, but overall, I'd say it's a good product.

We have been using Microsoft PowerApps a bit longer than we have been using Microsoft Power Automate.

We haven't fully launched a product yet, but I will say that development is quick and we can make changes quickly. I can't speak to the app's scalability just yet.

I've only used it through an RPA. We either did it for many years, or we did it by hand with JavaScript. We would use some tools to actually grab for web-based things, not desktop-based. We wrote tools that would allow us to take control of the website and then modify it on the fly while automating these processes.

We did it all with secure JavaScript, which is a lot of work and custom code, and it's difficult to maintain, so having a tool like an RPA tool, where we can take that business logic, put it in there, and then somebody who knows the stuff can come around after us and go, okay, I see what they did there, would be great.

We believe we have exploited the tool and pushed it to its limits, and we are still learning about its strengths and weaknesses. It definitely has room for improvement, but when I give it a seven, I mean it's functional. I can get the job done, but it's far from ideal.

When I say Java, what I mean is that when we were doing automation, we were primarily working on web automation. My phone is dying, so that's why I cut off.

We would write a lot of JavaScript code to automate, automate, and update these external websites that didn't have APIs, that we would read from. We are now reading from spreadsheets and updating data for them, then retrieving data from the results, and this simplified things significantly.

We wanted to see what people were doing with UiPath. I'm not really using it yet. I've looked into it a little bit, but it just hasn't been a driver for this project yet.

I am just using the product. I evaluated a problem and a solution set for a client, and I just evaluated these tools and said, despite their youth, these tools look like they are good. We looked at UiPath, but the price tag was expensive for a nonprofit, so money was an issue. We had a very limited budget from a grant, so we had to work with a toolset that wasn't on par with the Fortune 500. So far, we're pleased with the solution, and it's working. There are days when it is frustrating, but I've been doing this for 40 years and there are always challenges with tools. We do not have a relationship with Microsoft.

I would rate Microsoft PowerApps an eight out of ten.

We're using it for our business processes. We have applications for expenditure requests, travel requests, and accident reporting.

I am using the latest version of the solution.

It is easy to use.

Most of my training for what I do has been by watching or learning in the community. There needs to be better training on either one of these. 

We started implementing it in February 2020.

It is stable.

It is scalable. About 150 to 200 people are using it. 

In terms of our plans to increase its usage, I'm moving to a different department and starting over. We might be scaling up in my new department. In the current department, they still need to figure out what they're trying to do.

If I'm dealing with the community, technical support is incredible.

We were paper-based before switching to PowerApps.

It was easy. We started in February, and everything had to be up and running in March because of the pandemic of 2020.

I did it, and there was no reseller. We're a university, and the university was not going to pay for us to have this deployed by an outside partner.

I also take care of its maintenance.

I don't have that information. We work with a procurement office that deploys it for our university.

We looked at ServiceNow because some of the departments in our organization were using ServiceNow.

Deployment has to be supported from the top down because if you're trying to get things supported from the bottom up, you run into a lot of interference. This has not been the easiest.

PowerApps is incredible, so I would give it a nine out of 10.