Microsoft Power Apps Reviews

We use the solution as part of Dynamics 365 Online. Within that, we use Power Apps and we've integrated something on the on-prem database.

The app is located within Dynamics 365 Online. It draws data from an on-prem data source. We use it to perform certain actions in Teams, so we have Dynamics 365 and Teams integration.

We've created an email reader using Power Apps.

The solution is pretty easy to create and deploy apps.

You don't need a very high level of technical knowledge. Of course, you do need some level of technical knowledge, however, a normal developer can easily learn and deploy Power Apps.

The initial setup is very simple.

The solution scales well. 

They need a bit of RPA functionalities. There are other competitive products such as ServiceNow and Automation Anywhere. They offer exhaustive functionalities. Power Apps as a platform maybe need some ready-made templates that could be deployed. That would help.

There are occasional performance challenges. 

The product could do some integrations with third-party providers. That can be still expanded. They do have a decent number of integrations and connectors available, however many of those connectors only offer the basic functionalities. I'd like to see better, wider connectivity.

I've used the solution for six to eight months at this point. It's been less than a year.

In general, the product works fine. That said, there are occasional challenges in performance and when you actually have Power Apps working with other products on Power Platform, such as the Power Automate, et cetera. By and large, however, it's pretty stable. 

We have about 300 users on the solution currently. We do have approximately 700 plus users on Dynamics 365, however, not all of them are using Power Apps.

The solution is pretty easy to scale. 

We pretty much use this solution on a daily basis. It's used a lot.

We reached out to technical support just once where Power Automate wasn't actually triggering an event. Apart from that one ticket, it's been working fine. We haven't really dealt with technical support too much.

We have normal support. We don't have Premier Support. Of course, the response time was about average when we used them. In the end, the issue was something to do with the core product, so they have actually had to take it up with the product engineering team at Microsoft as well.

I'm aware of ServiceNow and Automation Anywhere. 

The initial setup is very straightforward and simple. It's not complex or difficult. 

There was some background development involved during the deployment process. 

The is no maintenance required.

We did not need any outside assistance from consultants or integrators. We handled it in-house ourselves.

The pricing is pretty good. Microsoft offers very good value for money.

Apart from the licensing, storage is actually the costliest part. One needs to actually look at how to optimize the use of storage as ultimately it's on the cloud. It's part of the Dataverse storage now, with Dynamics 365, Power Apps, et cetera. That bit of the offering is the costliest part.

The product license and platform licensing are good. That's definitely value for money compared to some of the other vendors. Microsoft is placed well. It's just the storage, as I said, that's costly. 

We are customers and end-users.

We are using the cloud version, and therefore we are going with whatever is the latest available functionality.

At least for the regular day-to-day work, one can build very useful apps with minimal investment. One can start fast. The only thing is, you need to have people actually experiment on this. Other than that, it's a good platform.

Currently, I'd rate the solution at a seven out of ten right now, as there's continuous improvement that's happening and, once that happens, in the future, I will likely be rated even higher.

We are an IT consulting company. We provide IT solutions to other companies.

We have had a few different requirements, one requirement was to create a simple online form that can be used by the clinics. When patients arrive, they will be given a TAB, to complete the form, which will be printed directly to the receptionist, once they complete the form.

Another application was supply chain management. Using PowerApps, we replicated the entire supply chain management. The corporate users will send the requisition to the purchasing department for review and approval, after which it will be distributed to prospective vendors.

Vendors will then submit their quotes for review. Multiple quotes can also be reviewed concurrently. This is all done with PowerApps. After they have reviewed them, they can select a vendor and process the PO.

In the third scenario, we developed a public relations system that you would find here in the UAE.

PROs must manage and obtain visa permissions in the United Arab Emirates. We have documentation with a two-year expiration date. As a result, we've developed a document management system that uses a Power Automated workflow system to view the alert and process the documents for all employees.

These are the workflows that we have worked on recently and have been created using Microsoft PowerApps and Power Automate.

Because there is no need for lengthy code, applications can be created quickly. That's the beauty of PowerApps in general, whether I'm using Power Automate or PowerApps for UI development. And the UI is very user-friendly.

When I am developing any user UI, it gives me complete flexibility. I can manage in any way I want.

It is constantly being improved. I've been using it for three years and have noticed that upgrades are happening on a regular basis, and it's becoming more and more user-friendly, both for developers and for users.

We can now also share it on Microsoft Teams. As a result, it is becoming increasingly powerful.

It is very easy to use.

A web interface is one thing that I don't see. I can create an interface for mobiles and tabs but only for PowerApps.

If you can have something like Power Web with it, that will be a classic because we are developing user interfaces, but we cannot access those user interfaces using a browser.

If we can get into that mode of publishing for the public users, which is something different, and I am not sure how that can be done, but I'm sure we can come up with something.

We occasionally have some issues where we can't grant access until and unless a user is created in Active Directory. This is something that should be worked on, and when it is, it will be powerful.

When it comes to PowerApps, debugging can be difficult at times. It would be beneficial to simplify it.

I have been working with Microsoft PowerApps for three years.

We are working with the latest version.

We have not had any performance issues, or any other issues, because it is on the cloud.

We are completely satisfied with Microsoft PowerApp's stability.

Because almost everyone uses Office 365, it is very simple to scale Microsoft PowerApps.

Our company has five developers among its users. Our clients, on the other hand, vary; we have one client who has over 500 users.

I've spoken with technical support, and they're fantastic. They provide you with a very good response from the moment you launch your ticket.

On a few occasions, when I launched a ticket, I receive full support and they were able to help me with everything.

We use Office 365 online which includes Microsoft PowerApps, Power Automate, and Power BI.

The initial setup is extremely simple for me. I am an IT professional, but it is easy, even for others.

I have worked with many who have been using other tools and when they were introduced to PowerApps, they expressed that it is amazing.

It didn't take long for me to install, only a couple of minutes, because I've been using Office 365 since 2013, but I've never used PowerApps before. I started only recently, in 2018.

One of my clients asked me to create a small app in PowerApps for him. That's where we began. I had a PowerApps application ready in a week.

We don't require any maintenance as it is on the cloud.

Microsoft's pricing is comparable with other similar solutions.

I had evaluated Mendix. We prefer Microsoft, we have used Microsoft from the beginning.

I am a VB developer. I began my career in 1995 or 1996. I'm a die-hard VB developer, and I love PowerApps because, I used to write a lot of code, but now with PowerApps, things are so simple and easy, we can have customized applications for end users in no time at all.

Aside from standard ERP and solutions, businesses still have a high demand for customized or tailor-made user interfaces. That is where I believe PowerApps is extremely useful.

As an IT company, I would strongly recommend this solution to anyone who is interested. It is one of the best tools available. If you are a Microsoft fan, you will definitely enjoy this product.

As IT consultants we have provided support and trained a couple of customers who are using it and also enjoying it.

I would rate Microsoft PowerApps a nine out of ten.

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

The solution is quite stable.

The product integrates well with other Microsoft products.

Technical support is very helpful

The initial setup is not complicated.

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

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

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

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

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

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

We also use Appian. We use both products simultaneously.

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

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

The pricing could definitely be lowered.

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

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

We have a Microsoft partner that we work with.

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

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

Overall, I would rate it at a seven out of ten.

This is a low-code solution that I am using for making applications.

The most valuable feature of this solution is the Model-driven or Canvas application-making platforms. The power of the two gives us exactly what we are looking for.

In an upcoming release, I would like to see custom APIs, better integration with other solutions, and more connectors available.

I have been using this solution for approximately eight months.

The solution is stable.

We have plans to scale the solution in the future and it is very scalable.

We have approximately 35 people users using the solution in my organization and we plan to increase that number to 75.

The customer service has been very responsive and has always given us the help we required. Alternatively, there is a large PowerApps community that can help anyone find a solution for their problems. The overall support is excellent.

The initial setup was easy, we had no problems. 

We have a small team that does the maintenance of the solution.

I pay nine dollars monthly for the subscription to this solution and the price of the is reasonable.

My advice to others is to review their use case and if it fits then I would recommend they try this solution.

I rate Microsoft PowerApps a ten out of ten.

I had to upload a form, an invoice, specifically, and then using an Azure function, I had to get that form from the Dataverse database and feed it to an Azure form recognizer and write the data back to the Azure Power App.

I like that you can quickly click together a user interface. For all no-code platforms that let you create a front end, you can click together something very quick. 

My problem with solutions like Power Apps and Betty Block blocks and probably with every no-code platform out there is that, as soon as you want to do something custom, something that's not provided by the environment you're using, it gets really tough. You have to work around the constraints of the platform. No-code platforms have constraints. I'm a developer myself, so I tend to not use no-code. I tend to code a lot. 

The notion people have is that no code equals no knowledge, and that's simply not true. Even though you don't have to write codes, you still have to know what you're doing.

I had some trouble interfacing with the Dataverse database. If I could, I'd make the couplings with other software easier. The integration with other software could be better. Any developer who had to work with an application made in Power Apps would find that useful.

There are limited use cases. 

I've used the solution within the last 12 months. 

The solution is a lot more stable than Betty Blocks. I haven't had any crashes or lost data or anything. That said,  haven't used it thoroughly. While I say it's pretty stable, I can't say how it performs under heavy use or big projects.

I've never had to reach out to technical support in the past. 

I've also used Betty Blocks. With Power Apps, you can quickly click together a user interface, that's also the case with Betty Blocks. However, both being no-code have constraints. For example, Betty Blocks was using jQuery one, and at the time we had jQuery three. I wanted to use a front-end framework. That was just not possible since it would mess up the Betty Blocks designer. And that's also the case with Microsoft Power Apps.

The ease or difficulty of the initial setup varies. For me, it wasn't that hard. However, I already had an Azure subscription and a Microsoft account. If you don't have any of that, it's not that easy - especially if you're not very technically inclined. It can be a daunting task.

I'd rate the ease of setup six out of ten. 

The deployment is fast and takes almost no time at all. I developed the application, and I pushed the publish button, and it was published.

I handled the initial setup myself. I did not need outside assistance. 

The license for the solution comes with my professional license, so I'm not sure actually if you pay by the user. For me, it was free to develop with a professional license, which is about 70 euros a month. That said, if you get a lot of users using it, it's not included. I don't know how much that would cost.

Whether it is worth the cost or not depends on the use case. 

We initially chose the solution as it was a customer specification. They wanted to use a Microsoft Power App.

I'm an end-user. 

I have been using the latest version of the solution. However, I don't even know if you can switch between versions.

If you want a complex system with lots of custom work done, then it is not ideal, as you are going to have to face the limitations of the platform. If what you want is a simple tool where you just need to upload some files, or you need to store some data to make a custom CRM application, then it's very easy to use.

It's certainly not a replacement for actual development work, and it's not a replacement for developers.

I would recommend the solution to others. 

I'd rate the solution seven out of ten. In terms of no-code, it's pretty good, especially when you use it with a Logic App, which is part of the Power platform. When I compare it to Orbis or Betty Blocks, it's just a really good product. It has a small learning curve, however, it should be really easy for people who have no previous experience.

We use this solution to provide a cloud-based platform for our clients to develop, connect, and store data from across the full Microsoft suite.

We particularly like the workflow connectors in the forms, for information introduction purposes.

Our customers appreciate the fact that the licensing for this solution is also connected with Office 365, making it a it's less expensive overall system.

It is also very user-friendly in terms of learning curves; it can be picked up very quickly by new users and provides good interoperability between Teams, Outlook, and other solutions from Office.

We would like to see some improvement in the cost of the solution when an organization has a more complex network structure. The advanced connectors are very expensive, which discourages our customers from implementing it.

We would also like to see a more robust library of uses for different system roles to be built into this solution, such as for authorizations.

We have been working with this solution for nearly three years.

The stability of this solution is okay, and really depends on the clients architecture and infrastructure.

When the solution is properly designed at the implementation stage, the scalability is incredible, and the only limiting factor is the cost involved with scaling.

The initial setup for this solution is very easy.

We would recommend this solution to organizations of all sizes. However, the level of investment needed may mean that it is better suited to medium to large organizations.

We would rate this solution an eight out of ten.

We primarily use the solution to create apps for business users which navigates them from within our platforms.

There are lots of good videos on Youtube that are available to help users train themselves on the product and understand its intricacies. They have a workshop that allows you to learn the product in a day.

As a business person, I design a lot of screens. The solution really resonates with me. Their design is amazing.

You are able to create a screen app within a day once you get the hang of everything. 

There are great templates on offer that make creating apps easy. They have galleries that help you pick predefined templates. You can also standardize these. It's low effort and low code. However, if you want to code more and have code validation or mobile, you can do that as well.

They have a web version of the solution, as well as a version for tablets.

The solution is pretty difficult to understand. You need to educate yourself on the product in order to be able to effectively use it.

The solution needs a bit more refinement in general.

It's still a new product. There's a lot of improvements that can be made from a useability perspective. 

There needs to be better guides and documentation available for new users in order to help them properly understand the product and how to use it.

I started using the solution after Power Automate, and therefore I started learning more about Power Apps probably last year in August. I would estimate I started on it in or around July and August of last year.

The solution is definitely stable. I haven't had any issues with it in that regard. It doesn't crash or freeze. There are no bugs or glitches. It's good.

Scalability-wise, I haven't put any complexity behind my apps yet. I haven't really experimented with scaling them up. From what I can see on the tutorial videos I've found, it seems to be possible. However, I have not directly attempted to scale anything so far. I couldn't speak from personal experience on the matter. I'd love for it to be possible.

I do plan to increase usage in the future. There are a few people who have seen my apps who have definitely reached out to me and said, "Oh, this is great." I help them understand how you can use Power Apps themselves as not many people knew about the product before they saw my work. 

More and more people are using it within the organization. I'm not sure of the exact numbers, however. I still have not set up any session for Power Apps for training. I've done sessions for Power Automate, Excel, Word, and SharePoint. There just needs to be more training for awareness. This is a relatively new product. Maybe that's why it doesn't yet have the visibility.

I don't really use technical support at all. All my questions when I reached out to technical support, were directing me to Power Apps In a Day - the training session. I did that and they'd answer all my questions. I did have a few questions based on a few functionalities, which I went on the Microsoft site to find answers to. I basically found two blogs. I understood that those functionalities are not yet there. I put down my feedback in terms of it should be there or not. Then that was it. 

I don't really directly communicate with Microsoft technical support. You need to go out and find your own answers online.

We did not previously use a different solution. 

There isn't an implementation process for the product. It is on the cloud. Everything is pretty automatic. In that sense, it's rather straightforward. It's not overly complex or difficult. It's on the user accounts. I just go ahead and start creating my app from there.

I'm not sure of the cost of the solution. That's not an aspect of the solution I handle.

I am using the latest version of the solution. I'm unsure of the exact version number.

I'd recommend the solution to other organizations.

In general, I would rate the solution at a seven out of ten. We've mostly been satisfied with the product, however, it is still immature and needs time for tweaks and advancements.

The solution is a low-code platform that quickly develops solutions for general business processes. Companies can integrate it with their existing systems, access data flows, and deploy applications within a matter of days or even a couple of days.

The tool helps simplify tasks like conference room bookings, onboarding new employees, managing documentation processes, or handling form submissions; PowerOps can adapt to various use cases. Its ability to develop templates and seamlessly integrate data makes it a valuable tool. It can be integrated with Microsoft Copilot. 

I recommend improving Microsoft Power Apps' licensing model. I've encountered challenges related to licensing complexity, which has led some customers to opt for traditional solution development and deployment methods instead.

I have been using the product for one to two years. 

I rate the tool's stability a six to seven out of ten.

Microsoft Power Apps is a scalable solution. 

We contact Microsoft architects for assistance if we don't get the help we need through the normal support channels.

The tool's deployment is straightforward. Deployment doesn't take much time, usually just a couple of days.

The product's value and benefits vary depending on the solution being built. Some solutions may simplify employee tasks. However, ROI cannot be much since it is an internal process. 

I rate the overall product an eight out of ten. I recommend starting with exploration because it's a low-code/no-code solution that anyone, even without a technical background, can learn. Set up the flow and template, and you're ready.