Microsoft Power Apps Reviews

The solution is really strong. I'm not an engineer. I'm an economist. Even without being an engineer, I can handle working with the data warehouse. It offers good speed and excellent design.

If I want to process for payments, I can do it fast and easy in Power Apps. If I need to process information from Facebook, from Twitter, or other places, it's really wonderful. 

Overall, the tool is very democratic. It's easy for anyone to use. You don't have to be a professional or well-versed in technology.

For me, it's easier if I have visual references in order to learn the system. However, I'm also Spanish, and the tool is in English. That's one level of difficulty. Another level is that there aren't too many Spanish use cases and examples. It would help if there was more documentation in my native language to help me learn the system more effectively. In English, I don't think this is necessarily a problem. There seems to be a lot of English documentation.

It would be helpful if there was more explanations built right into the solution's interface so that I can understand what action is supposed to get what result.

In terms of usability, when I tried to make an amortization table, I couldn't find an exponential option. I don't know if it's ideal for financial tools that deal with credit or loans. I'm still looking into this.

It's sometimes hard to import groups of options. At this point, I need to enter those manually and it slows the process down.

I've only been using the solution for about four months at this point. It hasn't been too long. I've used Power VA, Power Pivot, and Power Query for a long time, however, in terms of Power Apps, it hasn't been nearly as long.

The tool is good for work. I haven't had issues with bugs or glitches. It doesn't crash.

For me, and the way I am using it, the tool is fine. I'm unsure if it would work on a very large scale for big, big companies.

The initial setup was not complex. It's very easy as it's on the cloud. You don't need to be an expert in order to deploy it.

I'm using a trial version right now. I'm still learning the system, so I haven't moved into a paid version yet.

It's my understanding that the pricing isn't too bad. I've heard other people mention it's not as expensive as Azure in comparison with Linux. One or two licenses may not be too expensive, however, I don't know the exact pricing.

I started working with the common data model and the entities and working with my data warehouse. Now I'm working on my data warehouse with common data series. I use Power Apps for my standard entities' values. I need to modify it now with the new processes that are in place. And in the beginning, I use Power Apps for the management of the entities for Power VA. Since I've started using Power Apps, as I can see it's powerful and makes it easy for many, many, many kinds of work processes.

I'm still trying the solution out, and I'm still learning a lot about it. I'm by no means an expert yet.

I'm pretty satisfied with the product. Overall, I would rate it eight out of ten. It's a good tool and it's nice that it's part of a suite in Microsoft.

We use it as part of our analytics offering. We are basically into analytics. Maybe sometimes we use it to build small apps to instrument the research process. That's what we do.

I am from the sales side, so I really do not know the technical aspect of it.

It's my understanding that it has been issue-free.

We have pretty easy integration options.

Technical support is great.

The solution is stable and reliable.

The scalability is good. 

I don't have any notes for improvement. It does what it says it does. 

We'd like to see more integration capabilities in the future. 

We've been using the solution for about three years. 

The solution works well. It's stable. the performance is good. there aren't bugs or glitches and it doesn't crash or freeze. 

We use it for a very specific purpose, and therefore scalability is not really a factor for us.

We have about ten clients using the solution currently.

Technical support has been fine. We are satisfied with their level of service. 

We use the cloud version of the solution. There isn't an in-depth deployment process. 

We handle the projects and the implementation for our clients. 

I don't have any comments on the cost or licensing. It's fine. It's cheap compared to other RPA tools. It was about $40. There are people that are lower than that, however, they don't give you the features.

We use a lot of Microsoft products. We use Microsoft Power BI, Power Platform, and Azure Patch Solutions.

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

I'd recommend the solution to others. 

I would rate the solution eight out of ten.

The primary use case of this solution is for developing Proof of concepts and for preparing some use cases to present or to showcase them to the customers. Nothing related to production. It's only for presentations and for showing the merchandise to the customers.

The deployment model we are using is cloud-based.

The most valuable feature is easily connecting to data services.

I can have a SharePoint list and connect with users through PowerApps to present the information.

I am also able to connect with Microsoft Flow, which allows me to connect with different people to email and update items in Sharepoint.

The editor in the Web browser could be improved because it can be difficult to implement the commands in the buttons.

In the next release, I would like to see Microsoft PowerApps be more integrated with Microsoft Teams or SharePoint and with different applications.

When I configure PowerApps in Sharepoint it appears that it is not integrated with the page.

When it is configured it looks like it is a different application.

This solution is stable.

I have not contacted technical support because I haven't needed to.

The initial setup was easy and straightforward.

It took approximately two days, but it depends on what features have to be implemented.

I maintain this solution myself, and it only requires one person for maintenance.

We did not use a vendor to implement this solution. I did everything myself.

My advice would be to create a master screen for items like layouts and all of the typography that you may have in your application. 

Create a master screen widget. The rest of the screen will have, for example, settings for the layout that will refer to these objects in the master screen settings. Mainly for editing.

I would rate this solution an eight out of ten.

I primarily use the solution for its business application. My business needed an application and so that's what we're using Power Apps for.

We've been pleased with it. I would say that it has improved the way our organization functions. It makes app-building faster and easier.

The solution is excellent at figuring how to build an application in three months. It makes it very quick and easy.

The pricing is very reasonable. it's not overly expensive.

I can't recall any missing features. Currently, the solution is doing a good job of meeting my needs.

My target is to have an application that I can use for clients. I don't see Power Apps as being the long-term solution. They get expensive when you start to go to non-internal users. If there were to be external users, the solution would get expensive.

The documentation isn't great. It's only 75% of what you need to know. If you go beyond that and run into issues, it's really not going to help you.

For example, the software is almost guilty of being too powerful. The particular problem I had was that they recommended that I use Azure to do the login, to do the user authentication. Therefore, I set it up. However, it didn't work. I could not find the solution via documentation or online at all. Without knowing I could access technical support, I paid someone a couple of hundred dollars to try and figure it out for me and they couldn't figure it out. Eventually, I was just looking around and I came across one setting hidden away and it was set to false. I instinctively realized that it looked like it might be related and so I set it to true and all of a sudden everything worked. However, that whole issue could have been mitigated if the documentation just took that extra step and got into the nuances of the product.

What I'd love to see them do is to sit down and clean up the interfaces. There are three different ways that you can program. I'm particular to using a Power Apps portal. There are three different ways I can edit my Power Apps portal website. Each of them kind of does a better job of doing some things than the other ones do. Therefore you're kind of in this in-between realm of having to choose between certain things if you decide to go with a specific approach. They really need to clean up the development environment so that t's straightforward and predictable across the different ways to program. 

It does things, such as, if you want to delete a particular field or table, you get this message that says you can't due to the fact that it has dependencies. It's really hard to find what those dependencies are. Items like that need to be clarified. 

The application is working great now, however, every once in a while it gets complicated and it's hard to navigate.

I've recently delved into using the product. I've been using the solution for at least the last seven or eight months or so. It's been less than a year. I haven't used it that long just yet.

The solution is very stable. There are no bugs or glitches. It doesn't crash or freeze. its performance is reliable.

The scalability is limited if you want to scale externally. A company needs to keep that in mind.

I only launched my first application sometime around Christmas, or just after. It's still quite new. I have about a dozen or so people that move in and out of it. It's just a small app.

As a company, we are quite small. All of our users would be external. And, due to the fact that the solution gets expensive for external users, it's not a solution we plan to expand upon or use for the long term. 

The technical support is not easy to find. It's a bit of a well-kept secret. However, once you locate them, they are quite helpful and responsive. 

Truthfully, they are hard to find due to the fact that you just don't realize they're there. I had spent a month, six weeks phoning around trying to find internet solutions to problems and resources and paying people to help me, and nobody knew the answer. 

This was done without ever realizing that there was a very capable tech support resource available in Power Apps through the subscription. Once we found them, they were able to fix all of the issues we were struggling with very quickly.

The initial setup is quite straightforward. A company shouldn't have any issues with the setup process. It's not overly complex. 

The pricing is excellent. It's not too expensive.

However, once you get into adding non-internal users, the solution can get pricey. It's only reasonable if you are trying to create internal team-based apps.

I haven't looked at any other low-code development platform.

We're just customers and end-users.

We are using the latest version of the solution.

From a perspective of me doing a full test of the application and how I want it to run, it just met all of my needs and there are other storage locations for data. That said, the data is sitting in the CDS.

From my perspective, it was a great place to start and a great place to sit and test the waters. I'm looking to migrate it into something else in a little while. I won't stay with it forever. That's not the plan.

I'd rate the solution at a seven out of ten.

We use the Microsoft PowerApps platform to create low-code applications that are used for optimizing internal business processes.

The most valuable feature is automized processes.

The connectors are the main components that reference the data sources, and these need to be improved. They have to both improve the ones that are already there and add new ones.

We have been using this product for a couple of years, since 2018

This is a pretty stable product. So far, we haven't had any critical issues with it.

There are some options for scaling the product but we haven't used them, so I am not sure about scalability. We have approximately 1,000 users.

I would rate the technical support a nine out of ten. They are very good but the response time could be improved.

The initial setup is straightforward. It is a self-service solution, so there is no real deployment. It is a case of enabling that functionality within the Microsoft account, and then telling the people that it is enabled and available. At that point, I think that that they can create their own applications if they need to.

My advice for anybody who is implementing this solution is to research the material that is available in the documentation, as well as videos on YouTube. These sources contain a lot of information and recommendations for how to implement and use the platform.

They also have a really good community with Microsoft the websites, where many people post their issues and the solutions as well.

Overall, this is a really good product.

I would rate this solution a ten out of ten.

We primarily use the solution to create and arrange a number of requests, including requests for expenses, requests for leave, requests for documents, etc. Depending on the type of business, we can customize the request application.

In our organization, PowerApps is used to manage internal requests for expenses, leaves, documents, company resources. One connects to the application, enter the details of the requests and the request flows directly to the appropriate approvers. Less paperwork and more efficient management of the requests.

The most valuable aspect of the solution is the fact it is highly customizable. All types of forms can be created to collect information, pictures, and files. With PowerApps, you can connect your application to a wide variety of databases and applications where your data lives to read or write to it. If a connector doesn't exist, it's also possible to create a custom one.

With a plan starting at 10 USD, it makes it very affordable for anyone to create a low-code, no-code application. Very little costs are needed to run the solution. Furthermore, PowerApps has a community plan for free, and usually offer a trial period of about 2 months. Plenty of time and potential to learn, discover and develop.

The solution has a large community, so it's quite easy to find tutorials, how-to, and help.

PowerApps is part of the PowerPlatform from Microsoft, with Flow, or Power BI and enhances the possibilities to collect data, to automate processes, and to create rich and visually appealing data visualizations.

The solution is evolving very fast and every month new features are introduced. Sometimes it's difficult to catch up with all the evolution that's happening. I had to focus on Power BI for a while and left PowerApps at the side for a couple of months and when I came back, it had changed its interface and moved components around. 

Some connectors are not very easy to use and sometimes they lack proper documentation.

There should be better connectivity with other applications. I tried connecting with IBM and it brings errors at each refresh. The PostgreSQL connector is useless as it doesn't work. There's a lot of research needed and you often need to download extra drivers or equivalent components that end up not working well.

I've been using the solution for a year now.

The solution is very stable. There are a few issues with the environment, where we would have needed to create a new one. This would have been a problem if we had a lot of data. However, but I haven't faced any stability issues.

Scalability is okay, but they recently changed the pricing. Depending on what we do and what we use it for, the pricing is a bit confusing now. They're also offering a bit of a delay on the adjusted pricing for those who have a certain subscription, so I'm still figuring out what that means for us.

Technical support is very fast, with answers within 24 hours. Most of the time they either call directly or send an email. I've found them very good and they are helpful. They try to give a solution and offer direct service.

I've had experience with IBM and it was a bit more difficult to find the right solution and obtain results. As with some other PRN providers, I was expecting a slower turnaround, so this has been a nice surprise. Microsoft and PowerApps have been very good.

The solution is very easy to set up. Deployment is almost instantaneous. It's on the cloud, so you connect the logins and it's ready to go. You don't have to download it onto any device.

I handled the implementation myself.

The pricing is pretty good. Right now, I'm paying for a two or three-month trial that is priced well. This trial period gives a company time to try an application, develop it, test it, and decide as to whether they will go ahead and pay for a modular plan.

I find their pricing quite affordable.

We use the cloud deployment model. I'm a consultant; I work mainly with other companies.

Already with what exists, the solution is quite good and we can do quite a lot. I don't think too much can be improved.

I'd advise others to make sure they have good parameters and documentation before they get started. It's a good idea to follow the tutorial at the beginning. There are a lot of things about the solution that are good to understand beforehand, including how the different components work.

I'd rate the solution ten out of ten. For me, it has worked very well.

We primarily use the solution for in-house management.  For example, for human resources and warehouse management. 

We are a small business. We keep up all sales and duties within our organization. One day someone might be part of the development team, however, next week we want him on the sales team to directly involve them in a small project that we've done for the client. We don't have to go to a different person from an agency or organization or have someone that is always dedicated to a position. We need to be flexible in order to move our employees from here to here. And this solution allows us to change or play around with our own system to reflect the changes of our personnel.

The solution is very straightforward. Its context is obvious and everything is easy to understand.

Compared to previous applications which developed by Visual Basic, we can quickly update the whole business process without spending weeks or a month dealing with those aspects.

I can't think of any features that are lacking.

The pricing could always be less.

I have heard from developers that there is documentation missing in the reporting.

It would be useful if Power Apps were capable of providing more flexible reporting to allow the developer to really to manipulate the data, and get into more details - for example, why it's being changed and how it's been changed. If there was a way they could comment right in the reports, that would be very helpful. 

There should be more document management capabilities.

We've been using the solution for a year and a half at this point.

The stability is pretty good from a business point of view. It was reliable and easy to understand and work with.

We haven't really tested the scalability, however, we've noticed that, since everyone is working from home, it's much slower than if everyone works from the office.

With everything going on, we don't really have the right scenario to really test for scalability. That may happen in the future. COVID-19 has put a lot of plans on hold.

We currently have 12 people using it. They are mostly project managers and developers. We also have two sales people and the CEO on it.

We've never had to reach out to technical support. That's a good thing. It means we haven't had any issues.

The last solution we used was old and it was built in-house. It was time to retire it, which is why we adopted this product.

Although I'm not the person who handles the initial setup, my understanding is that it's not too difficult and pretty straightforward.

Deployment typically takes two months. The last deployment we did started in May and was completed by July.

There isn't a lot of maintenance needed. We have one developer that's dedicated to the maintenance and changing the environment as needed. It's pretty hands-off though.

We handled the implementation ourselves. We didn't need any outside assistance.

The solution is subscription-based, however, I don't handle billing, and therefore don't have insights into the costs. We don't have any extras that we pay for. We just have a standard subscription package.

I'd recommend the solution. Overall, I'd rate it eight out of ten. If the reporting and pricing were better, I'd rate it higher.

I've definitely learned about the power of the cloud. Before everyone used to use the VPN connection to the head office. When we pushed into the cloud and everyone can just see everything and the system is very sound. It also allows our developers to see what they can change. It's been great.

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

We are into software consulting. We have been developing various solutions and leveraging PowerApps to do it.

What I like about it is that it is coming from Microsoft. It is very easy for us, our techno-functional consultants to spin an application in days, not in months. 

This is easily integrated with native systems including the Microsoft stack. If we have to integrate with other products such as SharePoint, we can leverage any services using Azure or the same platform.

In terms of scalability, it can scale quite well. It's so scalable with forthcoming technologies. We can develop something in PowerApps, and that can easily be scaled to a bot. We can quickly make a bot there and make it work in conjunction with applications.

We had it integrated earlier with voice channels. You can manage an omnichannel kind of scenario between Voice, Teams, WhatsApp, social integration platforms like Twitter, Facebook, et cetera. 

The RPA is very closely integrated onto the same platform and BI as well. It's great.

The initial setup is very easy.

The product is very stable. 

I have found the technical support to be helpful.

When we talk of integrating with external applications, that's one area where, even today, I had to loop in my code developers. If this area can be streamlined so that my techno-functional consultants, who are on-site, can immediately start working on something without the assistance of developers, that would be ideal.

I've used the solution for four and a half or five years. 

The stability has been great. There are no bugs or glitches. It doesn't crash or freeze. It's reliable.

It's so scalable. We can scale to all the latest technologies and we can integrate with the social platforms. We can integrate with the document management system (SharePoint). We can integrate with the Active Directory exchange server. It's limitless.

It is so much more scalable once you have everything available over in the Dataverse so that you can write triggers and automate a lot of the BPM. Once you have everything with you, you can spin any dashboards, reports, schedules, and then those can go through mail alerts. You can schedule alerts through WhatsApp messages. You can schedule it through voice IVRs. You name a thing, or you can schedule it. You build it over here and then schedule it over there. 

My experience with technical support has been very, very hood. They've been very supportive. The only thing is that you have to have the right support plan. If you have one, they adhere to the SLA quite well.

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

I have done the initial setup multiple times for the various installations. I can handle it on my own and do not need outside assistance. 

The pricing is a subjective thing. Whenever we are positioning PowerApps to an enterprise that is already into Dynamics 365 ER PCRMs, it is very easy to position it as they have already made initial investments there. It is just simply that the number of users that are based on the number of applications and it can be scaled. For them, I've never faced any issues. For example, for a hospital with it, we were already reaching out to, say, 40 units. When they wanted to scale to their smaller units, the 70 of them, it was a cakewalk. Then we had a plan to extend it to their pharmacies, say, 50 of them. That, again, was a cakewalk as they were already on that platform.

However, when I go and reach out to a smaller business SMB segment, the challenge over there is that we are faced with competition - with other software which has been built on PHP. If we host it on-prem, of course, then that discussion of cloud versus on-prem and those fundamental discussions creep in and then there is the minimum unit price per license, meaning per user or per app. When you look at it that way, an SMB will see it as expensive compared with open-source options.

I'd rate the solution at a nine out of ten. If the external integration process was easier, I would give it a perfect ten.