Microsoft Power Apps Reviews

We use the product for sales and customer service features.

The platform has valuable features for opportunity and finance management. It has all the essential features for customer service.

Sometimes, the opportunity includes two products, and the outcome for each product is different. It would be beneficial to have a feature that allows users to split the opportunity into separate logs for each product.

We have been using Microsoft Power Apps for more than 15 years.

We never encountered system downtime issues.

It is a scalable platform.

We contacted the technical support services in case of functionality unavailability during the trial version phases.

We used Microsoft 365 Dynamics CRM earlier. Later, we switched to Microsoft Power Apps for faster speed and availability of on-cloud infrastructure.

The initial process is simple. We need to create a trial and start working. It takes half an hour to complete. Later, we can purchase the licenses further.

The product is inexpensive. I rate its pricing a three to four out of ten.

We evaluated ServiceNow. We decided to use Microsoft Power Apps, as we already used the Microsoft platform. It was easier to onboard the product into a trial environment, and premium support was also available.

I rate Microsoft Power Apps a nine out of ten.

We use this solution to integrate our apps, and send processed data via the different connectors it provides.

This solution has allowed us to offer our customers to integrate with our platform platform to send documents, and for them to be processed with a digital key network solution, without having to use the platform directly.

We like that this solution allows us to fully define our test environments, and link them using different code. This means we can do different tests, but with one basic structure, and then export the data and use it in other platforms.

We would like to see the period for viewing executions within this solution to be extended beyond its current limit of 28 days.  We would prefer to be able to offer our customers an infinite amount of history to search.

We have been using this solution for nearly a year.

We have found this to be a generally stable solution, and have only experienced issues when there are a large amount of registers involved.

This is a very scalable solution.

We did not previously have a single solution, but instead we used a component that worked using Java.  We switched to this software because it was less complex to maintain.

The initial set up of this solution is fairly straightforward.

We implemented this solution using our in-house team.

We would advise organizations that this solution has a high-price point. However, the cost is justified for how comprehensive the package is, and all components of the solution are available under the standard license plan; there are no hidden costs involved.

We would rate this solution an eight out of ten.

We use this solution for workflow automation.

Power Automate has been the most valuable feature. 

The set up of the solution could be simpler. 

We have been using this solution for three years. 

I would rate the stability of this solution an eight out of ten. 

The customer support for this solution could be faster. 

Positive

The initial setup is fairly straightforward. I would rate it a seven out of ten. 

The whole life cycle takes two months to develop, test, implement and deploy.

It is possible to make use of free licences for the sake of a POC. 

Overall, I would rate this solution an eight out of ten. 

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

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.

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.