Microsoft Power Apps Reviews

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. 

The primary use case for this solution for us is building in-house applications rather than having to purchase them. We build fairly basic applications and we would rather use Power Apps to deploy them or create them in-house.

The way this solution helped us improve is by allowing us to collect data by combining it with phones and the tools Microsoft uses to send out surveys and also use it for a number of automation and requests. It creates forms with which people can make requests or respond to surveys and those are worked on the backend. The whole process is done using Power Apps.

The features I find the most valuable are the 365 and Microsoft applications integrations and the automation.

The area where this product can be improved is the documentation. When we get stuck it's with the documentation when we are not able to find the codes we need. The solution requires a lot of codes and understanding of the scripting language. Most of the time I end up going to forums to get them. I would like to see Microsoft come up with a knowledge base for Power Apps.

In the next release, I would like to see more integrations because there are some that are not available and we end up having to get adjacent script to work on to work with that.

I have been using this solution for two years now.

My impression is that it is very stable. I would rate it a 10, on a scale of one to 10, with one being not stable at and 10 being very stable.

We rarely scale when it comes to Power Apps. Once you deploy the application, that's it. So if you need to scale something more robust you probably have to deploy a new one.

Currently, there are over 500 users of Power Apps in our company.

We plan on expanding because it saves us a lot of cost in terms of the application that we currently use this for.

I am not even aware if there is any technical support for Power Apps because most times we have to go through online communities and forums to get what we want. I think the support for Power Apps should be something Microsoft could look into.

The initial setup was straightforward because they have a quite number of templates that you can pick from. The deployment does not take long as it comes with the Office 365. If you have Office 365, you have the Power App enabled in your directory.

The ROI is visible considering the number of applications we have been able to use it to build.

The Power Apps comes included with the Office 365. When you purchase a business standard license, the Power Apps comes included.

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.

I am not a PowerApps user, but recently I have been evaluating and scoring no-code to low-code platforms (for developing mobile apps). The score chart is divided into sections, such as usability and features like the ability to test and multi-platform. Due to these evaluations, I learned the systems well enough to be able to build a sample application on all of these platforms and then fill in my evaluation.

I like the fact that Microsoft PowerApps it a self-contained solution; I could build everything and then deploy it. I liked the UI designer that they had for building the screens and also defining the flows. Of all of the solutions I evaluated, it was the easiest to use and deploy.

Microsoft PowerApps is not intended for customizing what's generated in a major way. You have these little windows where you can enter your script and such, but there is no script debugging, nothing like that. You build and you auto-generate the code. From there, if you want to customize it too much, then it's going to get difficult — OutSystems was more intended for that; you can do a lot more customization after you build your solution.

The stability is pretty robust. I didn't encounter any crashes or anything unexpected.

I did have a negative experience with customer support. I contacted them and was connected with an automated messaging system; It was hard to get to talk to someone. That was definitely a concern for me.

For me, the initial setup was very simple and smooth-flowing.

I was using a free version. The company has a subscription where you can use certain features for free, but there are features that require a premium subscription to use. I am not certain, but I suspect they would be expensive.

On a scale from one to ten, I would give this solution a rating of nine.

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

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