Microsoft Power Apps Reviews

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.

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. 

My primary use case for Microsoft Power Apps are mostly demos for my customers and in trainings. I am a Microsoft Registered Trainer.

The most valuable feature is the completeness of the concept. It is not restricted by where you are allowed to use it and that is its greatest strength.

There is room for improvement in error handling and debugging. I would appreciate it if Microsoft created something like the social network graphs Facebook sometimes shows you (potential connections). It would be great for Microsoft to take a similar point of view regarding the data and data flow in Power Apps. It would help us see which field is changing and which is influencing the follow-up field or display or workflow, etc.

As a chief financial officer, I would like to see the mark of chain retracement and where the money flows. Imagine dropping a little drop of ink onto a handkerchief and seeing the ink sucked into the fibers of the handkerchief and distributing itself. Similar things happen to money if you put it into a small market and a chief financial officer needs to have that information. 

I have been working with Microsoft Power Apps since 2018. 

Microsoft Power Apps is definitely stable. It is as stable as SharePoint and this app model has been in place since 2013. Essentially, it requires you to put code onto a SharePoint site which is not executed there, but rather on a client or on specific workflow codes, which are client. If code executions are well work-flowed, it is capable of saving your script and of the global resources. That capability to take off where you left off, including external resources, is a great strength.

Microsoft Power Apps is scalable. SharePoint is a farm. It is a big forest of machines interconnected by a messaging system, Windows Azure Service Bus. It can be understood as a telepathic network between the machines. As long as one machine is running, the system's running and as soon as more machines are adding the capabilities, the load is distributed automatically.

Microsoft's technical support is at a high level. 

We did previously use a different Microsoft workflow operating system, but it was complicated to program and difficult to provide interactions with the users. All of that is much easier now that we use SharePoint platforms like Teams. Microsoft has the best of all worlds. I am confident that it will rock the market.

I have an MSD end subscription; it's a flat rate subscription.

My advice for anyone looking to implement Microsoft Power Apps is: please have a closer look at the Azure infrastructure and do not underestimate the complexity of Azure Active Directory and SharePoint. I recommend spending a week or so letting someone informed like me introduce you to the complexity of Azure Active Directory, SharePoint, and Windows Azure. Not having this information is like driving a car without having put oil into the motor and air into the tires. In other words, it would not be wise.

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