Microsoft Power Apps Reviews

We use the solution for, production orders, and for statement classification expenses for a family company. 

The support is the most valuable feature.

The incorporation of AI to construct a no-code application is an advantageous feature. However, I believe it is an unfulfilled promise. I think it will eventually be implemented, but ultimately, we will require the assistance of a programmer to guide us through the process.

There is room for improvement with the amount of code required to implement the expense classification app.

I have been using the solution for three years.

The solution is stable.

The solution is completely scalable when we are also using Microsoft Dataverse.

The technical support is quick to respond.

The initial setup is not complex, but there were some areas that we struggled with, such as the gallery limitation. Nowadays, we are able to pull more than two thousand records, but if we do so, we have a lot of problems with the performance of Microsoft Power Apps.

The pricing is complicated to understand.

I give the solution a seven out of ten.

We use this solution for process authorization in our company.

It is very easy for us to implement. We have a Microsoft ecosystem, and this solution has many components for integration.

It would be good if this solution supports standard BPM notation. We are thinking of switching to a BPM solution next year because it is not a BPM solution.

I have been using this solution for a year.

It is stable.

Its scalability is very good. This solution is in Microsoft cloud, so we don't need to worry about scaling it.

We didn't use technical support. I have only used online documentation, and it is very good. There are good videos out there.

We didn't use any other solution.

The initial setup is very easy because it is a SaaS solution. We don't need to implement any server in the company. We just use the SaaS solution.

In terms of the implementation strategy, we take a small business use case in the financial area and do a proof of concept to evaluate a solution. 

We did it on our own.

We use the Office 365 package, and Microsoft PowerApps is a part of the package. We don't pay any separate price for this.

There are no additional costs. We just pay for the Office 365 package.

I would recommend this solution because it is an easy solution for the Microsoft ecosystem.

I would rate Microsoft PowerApps an eight out of ten. We are happy with this solution.

The primary use case of this solution is to automate the interaction between documents and departments. For example, it's a flow for someone who has to validate a request, a file, or to review another file. A flow is put in place to avoid email communication.

I like the status of the flow and the dashboard, with all of the flows that are running and showing the stages of them.

If you are accustomed to Microsoft technology, then it's quite easy to learn, but if you are new around the whole online platform of Microsoft, then it takes time. Even if you are familiar with Microsoft products then there is still a learning curve on the use.

Previously with Microsoft, they were offering hands-on exercises or labs. I think that should be put back in place. Also, a few years ago Microsoft had an MVA program. It was called Microsoft Virtual Academy, where you could learn a lot about technology, but now it's deprecated and that's why it takes time to learn the new platform.

I have always felt that you need an IT background to use this solution.

I would like to see more regarding the help element of the program itself. More courses around the usage and of the technology features, more training, and guides.

I have been using this solution for six months.

Normally, our downtime is planned, and we are aware of it. However, on one or two occasions we have experienced unplanned downtimes. As it was on our end, and not problematic, it was disregarded.

At this time we have three to five users.

We are using this solution once a week, as we have only just started using it.

We have not needed to contact technical support b. Microsoft has a tool located in the portal where we can see the service, help, and stages. This includes all of the help for Office 365.

The initial setup was very easy. It's a cloud solution. Because we were already using Microsoft products, we only had to enable the license and just start using it.

At this time, we are still learning the basics and the setups while discovering the entire product and how to best use it internally.

I would suggest investing in the training of the product. 

It is very important to know the capabilities of the product to be able to address any questions a customer or user may have for you.

I would rate this solution a seven out of ten.

Microsoft has come at the right time. To come out with a RAD (Rapid Application Development) tool where you can develop your apps on the cloud much faster, and deploy them for multiple devices, whether it is mobile, cloud, laptops, or desktops. It is similar to Oracle APEX or Oracle developer tools where you just drag and drop into your application within minutes.

The primary use case of this solution is case management reporting. If, for example, you have a set of engineers who have been assigned a particular case or project they will need to record all of their activities and their visits. Using the application created in PowerApps, they report everything, then it goes through a workflow. 

The workflow goes from recording the daily activities of the team for the specific project. The project then goes through a series of approvals and gets logged, completed, and the report is generated. 

Expenses are also being logged. 

We have Power BI as well, and it moves the data from the source to the data warehouse then generates a report.

This is quite a short term, six-week engagement. We wanted to create an application and have it up and running within four to six weeks, rather than spending three to six months on bigger projects on the platform. We wanted it to be quick and fast.

PowerApps is best suited for those cases where you have a small scenario and an application to support that project or scenario. You can call these departmental applications, which are needed on the fly. We create a much shorter development lifecycle and then deploy, and then people start using it.

Take an example of the COVID-19 situation. We wanted all of our branches to log their COVID cases or what exactly are they doing daily to manage the COVID cases and to know what the process is. All of those details are logged into the COVID folder and then the reports are generated daily or weekly.

Microsoft PowerApps is a no-code solution.

I would say that the most valuable features are the user interface, navigation, and business routes.

It quickly drags and drops. It doesn't take much coding, there is no coding in fact. You drag and drop, select a few things to configure, and then read those applications in the user screens. 

With business rules, you can just select and you don't need to elaborate coding or backend code. This way, it's much easier to write or create those applications using their features.

When you capture a lot of data, the data becomes enormous. It's one of Microsoft's challenges that there is a threshold limit of 5000 items. It has to improve the threshold limit where it can handle data beyond 5000 items.

I would like to see integration with on-premise business applications, complex business routes, and complex business workflows.

We started using Microsoft PowerApps in 2014.

Currently, there is a challenge in scaling up. We can't scale beyond large data.

We have approximately 10,000 users in our organization.

There is a challenge in getting support. The support staff is not trained properly in PowerApps.

The initial setup was not easy, but not exactly complex. There was a lot of research.

There are two licensing costs, one is pay-as-you-go, or you can develop it for one year.

I would advise others to make an informed decision before you implement it. There are a lot of challenges, and the product is going through a lot of changes.

It's promising, so I would rate this solution a seven out of ten.

We did a POF with Microsoft PowerApps and we used it for simple automation tasks.

The solution has not helped our organization. Since we moved away from Microsoft PowerApps from the bugs and I'm not sure if it's improved. When I look at the developer community, it's still buggy, there are some issues. It's not consistent when you are working with applications. If I work with the same application, it gives me a different choice every time. It doesn't give you the same choice of how to interact with the application.

Microsoft PowerApps's most valuable features we found are that it's very similar to the other Microsoft products, you can do the basic automation quite quickly. The interface is similar to the other Microsoft products which makes it easy to navigate around because we are used to Microsoft products.

Microsoft PowerApps can improve the number of bugs that are present. When you are using the different applications it is not accurate.

In the next release of Microsoft PowerApps, they should add IDP and a control room.

I have been using Microsoft PowerApps for two months.

Microsoft PowerApps is not stable.

Microsoft PowerApps is not scalable. When compared to the other solutions that we've worked with, it's scalable. Everyone can build their own automation and there isn't a single repository where you can share or make sure that you're using the same automation. Everyone builds their own version of the same automation it's inefficient and at the same time, it is not scalable because if one thing breaks, you have to go update every process that you've automated.

In terms of support, there isn't much support compared to UiPath, Blue Prism, or Automate Anywhere. There is not a lot of documentation, training, or community support. People are starting to use Microsoft PowerApps, but by the time it catches up, it'll be a while.

I rate the support of Microsoft PowerApps a three out of five.

We had six people for the maintenance of the processes used in Microsoft PowerApps.

I have evaluated many other solutions.

My advice to others wanting to implement Microsoft PowerApps, they should do research on the connectors that are available compared to the competition. This will speed up the time to their end goal because Microsoft doesn't have many. The general support documentation that is available on using the tool, compare them with the other solutions to make a decision on what solution to use. They don't have many resources yet that are qualified in Microsoft PowerApps or Microsoft Power Automate.

I rate Microsoft PowerApps a four out of five.

Microsoft PowerApps needs a lot of fixes and improvements, and the competition is way far ahead compared to Microsoft at the moment.

It was used to collect or gather information from the requests, assess requests, and evaluate the requests for a new potential project. 

I am a consultant for developers and architects. People to whom I give consultation use it.

It is a cloud solution. Data can be cloud-based or on-premises, but it is mostly cloud-based.

The most valuable feature is that PowerApps can be used by most business users. It is not only for programmers.

Its performance is also valuable.

In some cases, PowerApps would have some limitations in terms of the data, the number of transactions, and so on, but for a normal solution, it would be enough.

I have used it for more than one year.

I have not heard about any issues with its stability.

It is scalable. It is used by more than 200 people with different roles, but only two people directly work with it. 

People use different solutions for different projects. The previous project was on another technology. They switched because it was more simple, and they knew similar technology for developing the project. They were already using other solutions, such as Power Automate and Power BI, from the Power platform.

It doesn't require any installation. PowerApps works on the Microsoft cloud on the server, and you have two options for using the data. The data is possible on-premises or on the cloud, but PowerApps is only on the cloud.

It depends on the subscription of Office 365 that customers have. With some subscriptions, it's possible to use PowerApps.

I would recommend this solution to others. I would rate it an eight out of 10.

The usability, in terms of low-code applications, is a feature we have found most valuable. We just do development and then distribution.

Improvements to the capturing of geographic locations and integration with maps would raise my score of the product from seven point five to its maximum of ten.

We have been using Microsoft PowerApps for around two years.

So far, the product has shown stability.

The product is scalable.

I am making use of the product in my own company.

I would rate it an eight out of ten. 

The most valuable feature is the compatibility with other Microsoft components, the connectivity to Microsoft databases, the connectivity to other components on the Microsoft Azure environment, the connectivity to Office 365 and the connectivity to teams and the overall environment.

Microsoft should combine both the web and the mobile environment with all of the layers of development into one package. Currently, it's separated because Microsoft Power Apps does not cover all of these issues, so you have to connect to two different solutions. With Mendix for example, with one environment, the developers can create either a mobile app or a web app — it's an all-in-one environment. Microsoft Power Apps is not a service. For instance, if you want to connect to a database, it will be done via a database platform. 

Microsoft PowerApps is both scalable and stable. 

Microsoft PowerApps has a good support community.

The initial setup is no more complicated than similar solutions. I'd say it's pretty straightforward. 

Overall, on a scale from one to ten, I would give this solution a rating of eight.