Microsoft Power Apps Reviews

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.

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

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.

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.

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.

I'm working for a company that provides services and develops projects for our clients. I am a solution architect and I use Microsoft PowerApps.

In Microsoft PowerApps the most valuable features are the fully customizable design that we can control everything that we would like to control. For example, the integration between Microsoft and third-party services through pre-built connectors, and the functionality to create custom connectors.

The solution could improve by having more connectors for different solutions in a way to create custom connectors. Additionally, they should make HTTP Connectors free again because it was not always a premium feature. These HTTP connectors allow you to send API requests which can be important.

I have been using Microsoft PowerApps for approximately four years.

The performance and the stability of Microsoft PowerApps are great because it is based on the Microsoft platform. We are able to use a lot of other features, we have no problems with the performance.

The technical support from Microsoft PowerApps is quite good because they respond in a few hours. They provide comprehensive support as well. If you do not buy any support package, SLA agreement, et cetera, and only have a standard license, you are able to raise a ticket with them and they will support you.

The initial setup is very easy.

There are areas of Microsoft PowerApps that can be improved. For example, the license policies are expensive to purchases the premium connectors. If a company would like to use the premium features, they have to pay a lot of money. The Microsoft PowerApps portal could be easier to use when there are a lot of external users because if a company has 1,000 external users, it is too expensive to use the Microsoft PowerApps portal.

I would recommend people to pay attention to not only the documentation of the solution but Microsoft provides a lot of video and text documentation. They give step-by-step guides on how to use different features and how to start and complete the implementation. Microsoft documentation is a good way to start for non-familiar people to Microsoft PowerApps.

I rate Microsoft PowerApps a ten out of ten.