Microsoft Power Apps Reviews

We use the solution for collaboration modules within our company. For example, we use Power Apps to handle requests when investing in projects abroad and needing approval.

The solution integrates quickly with our organization's existing systems.

We're running a campaign to encourage users to utilize the Power Apps. This is particularly challenging as we incur licensing costs, and some individuals do not use the applications.

I have been using Microsoft Power Apps for three years.

There were no stability issues.

250 users are using this solution. We have some projects for next year that we will use to increase the usage of Power Apps.

When we need support, Microsoft helps us immediately.

Positive

Deployment is easy and takes three months to complete, depending on the project. When we start using their programming, they understand easily and faster.

The solution has increased productivity due to automation. We can automate and save 30% on costs. Power Apps allows us to allocate or invest time in other activities when the apps handle certain processes.

The product is cheaper.

The solution's maintenance is easy. It is easy to use, understand, and manage.

Overall, I rate the solution a ten out of ten.

We use the solution to create applications. We were getting ideas, fine-tuning, and putting them in different queues that are available to the whole organization.

We have been utilizing the tool for very long. We can easily build a very small application or a large database with the tool. It also provides integration with SharePoint. Anyone can easily build a very basic application using the solution. If anyone wants to create an application to put SharePoint lists, it can be easily built using the product with a few clicks by any user.

The product's usability and the ability to fine-tune are really good. It is easier to work with compared to AgilePoint. The product is very user-friendly.

The solution must provide more integration with third-party applications.

I have been using the solution for the last eight to nine months.

The solution is relatively more stable. Loading is also good. It gets a little slower when we load large amounts of data sets. However, it is good when it comes to downtime.

The solution is very scalable. I rate the scalability an eight out of ten. Around 50,000 to 60,000 people are using the solution in our organization. It is accessible to the whole organization.

I did not contact support because I could get most solutions to my problems on Google.

The solution is deployed on the cloud.

The tool is not that difficult to maintain. We have a separate support team taking care of maintenance. The team works on tickets and closes them. People have built many applications using the solution.

Power Apps is relatively cheap compared to other low-code and no-code systems like OutSystems and Mendix.

Power Apps is more scalable than AgilePoint. It is also easier to deploy things using Power Apps. We can use the tool to deploy smaller solutions without much coding knowledge. If we use Microsoft products like SharePoint, we can integrate them easily with Power Apps.

There are buttons available in SharePoint that enable us to create and publish an app with just one click. The documentation on Microsoft's site and the learning platform of Power Apps is good compared to AgilePoint. AgilePoint has limited videos because it does not have a large working base.

The tool is good. People should definitely try it out. It can be a perfect solution for the whole enterprise. Overall, I rate the product a nine out of ten.

The solution is used internally in my company.

Flexibility, easy setup, and fairly quick results are valuable features of the product.

The fact that we couldn't share that with our other organization or outside of the organization, consisting of our colleagues in the joint ventures, was a weakness of the solution. So, it is an area that needs improvement.

I have been using Microsoft Power Apps since 2018 or 2019, so it's four or five years. Also, I am using the solution's latest version. I mainly use the cloud version. I am a customer of the solution.

Regarding stability, with the normal version of the Canvas app and Power Apps, and for fairly simple apps, it's perfect. But if you need a more nested or layered system in your app, setting them up takes a little time. And it also takes a lot of manual maintenance of the items in your product.

Stability depends and varies from case to case. So, what I do is mainly internal and feedback collection and everything to manipulate how the data comes in, which is great. The interface or setting could be better, but they would have compromised all the other things, including the lead time for development. So, for that level of work, the performance would be about eight on a scale of one to ten.

Scalability depends on the knowledge and skill set of the users. My user community has been in range from seventeen hundred to five.

Given the size, I think that support from the technical team is acceptable. I have had problems with SharePoint, including stalling and throttling of the back end and everything. It took me quite a long time to get an answer from Microsoft, which I understand, as they are big companies, and so they are not going to fix it for you the next day even when they know something, so I would say it's considerable and understandable. There are things that are up there, and they probably are not such a technical hassle to be developed or to be resolved. Now, considering the fact that they have already been around for a few years, it can be a bit disappointing. But, well, given the user community and the forums and everything, I think that it is forgivable.

I use Mendix. Mendix has more of everything in one place, and you can see your process actually as in a flow instead of ready code or work with the objects in the front end. So that's definitely a pro of the solution. The problem is that it's much less configurable with the other solutions than Power Apps. Power Apps by itself is not configurable, but it is pretty much configurable when connected to a database, Azure or SharePoint.

The solution is deployed on a corporate cloud, so it is for the organization's private use. The time taken for deployment depends on the complexity. But, when I was working on Power Apps, it took me days. When they were responsive or needed to form a table, I needed to manually add blocks on top of each other, including everything in that, and that was taking a long time.

Usually, the free licenses of Power Apps come to normal corporate users for free. If you do not use the premium workspace and are employed in a big company already using E3 or E5, then Power Apps would be something for free, and that's a trick. For normal users within a corporate firm with licenses, it's totally favorable. But I don't know how it would be if you were outside a company or using it yourself.

The overall performance of the solution depends on the use cases. So, Microsoft Power Apps is perfect for smaller things or smaller assignments. For very big things, the solution's overall performance also depends on the education level of the people using it. But if you want it to be super reliable and whatever, I would say that it has some constraints. And I was using a version of the solution with SharePoint and all. I was still working on the database and things like that. I understand that they will probably be performing much better. The normal version is not a super reliable tool.

Microsoft Power Apps has been very useful. With Mendix, I have been a user of the developed solutions, but because of the tool and the license you need to get or the training you need to get before starting with the development, it has been hindering, so I cannot really say. Overall, I rate the solution an eight out of ten.

We're not in production yet. We're still very much in the early stages of this solution.

The cloud aspect has been great. We don't have to do a lot of research in order to begin integrations. It's so easy to integrate with other solutions.

The solution works well with Microsoft Teams. We used to use Skype for Business, and now we rely on Microsoft Teams Enterprise E5. 

There's great integration with Dynamics 365, Office 365, and more. It's great that everything is easily connected.

We can use the solution from cell phones, tablets, or computers. It works on every platform and in every environment. 

The solution does work a bit differently on cell phones and tablets.

We still have information on our SQL server and we need to migrate things over. The timing of doing that is going to be a little tight.

We're not in production yet, so we're still working through some issues. However, by the time we are in production, I'm confident this solution will be ready.

I've been working with the solution for about six months at this point.

The stability of the solution is quite good. Of course, if we run into any issues, technical support is right there to help us, and they are very helpful.

We have more than 1,500 users in our organization. There are other users that will also be able to access the solution from the outside. With this particular solution, in terms of maintenance and direct work on it, we started off as a team of four, however, now we are a team of ten. We needed some more people to maintain the surrounding software. However, overall, it's been good.

We're not a small organization. We're pretty big. It's easier to focus on smaller projects rather than trying to implement something that's large scale.

We've found the technical support to be very good. They are always right there, ready to assist. We can open tickets 24 hours a day. If they are critical, they are dealt with quickly.

Our company is quite large. With 1,500 or so people, changes take a while to implement. It's not like a small organization where you can do everything quickly. You need to make sure people know how to use it.

In general, the full deployment took a few months.

I don't have too much information on licensing It is likely per application we use, or per machine. I don't deal directly with billing and therefore don't have the exact pricing.

We have a very good and very close relationship with Microsoft.

I started working more on PowerApps as we were making a comparison with Salesforce. We decided on PowerApps mostly due to the fact that Salesforce would not work. 

We have to maintain our current environment, so at some point, it's not that we are 100% in these new tools. Right now we have more than 60% of our time in these new tools and try to not develop any coding. We do make some code in JavaScript, however, it isn't too much.

It's a good solution. There is some coding needed for customization aspects, however, it's a pretty solid product.

There's still a lot that I need to learn about the solution. Therefore, currently, I'd rate it at a seven out of ten. We're not in production yet, and therefore it's hard to gauge many aspects of the solution.

I use Microsoft Power Apps and some other tools in my company. Sometimes, we use just Test Studio. In general, we just use Microsoft-based software in our company.

The solution's most valuable feature revolves around its low code capabilities. Coding work is less in the tool.

The controls are not available in the tool by default, so it needs to upgrade their controls, like gallery controls and some other controls, so that they can be made more usable.

I have been using Microsoft Power Apps for more than ten years. I am just a user of the tool.

The tool sometimes fails because of connectivity problems or something, but it is generally stable.

Depending on the users or according to projects, my company secures the tool's licenses, and we use it. Around ten people use Microsoft Office 365.

The product's initial setup phase is easy.

The solution is deployed using Azure's cloud services.

The tool is neither cheap nor expensive. The tool's cost is manageable.

I recommend the product to those who plan to use it.

It can be easy for a beginner to learn to use the tool.

My company uses the product with AI features, and it is easy to use.

I rate the tool an eight to nine out of ten.

Our use case for the product revolves around financial applications, including account services, a service portal, asset transfers, and additions for the organization. It involves multi-level approval processes for stakeholder identification and managing entries in the DLP lecture.

The platform's most valuable feature includes the gallery for displaying data for managing approval flows, which is useful for our multi-level approval processes. Additionally, the 360 payments feature is valuable for its default hierarchical approach.

One area for improvement in the platform is enhancing the user experience, especially for less tech-savvy users, by simplifying complex features and controls. Additionally, adding more functional options and features could further improve its usability.

I have been working with Microsoft Power Apps for the past six months.

The platform has been a stable product for us. Despite occasional updates and transitions, it has consistently met our needs and requirements.

I would rate the scalability of the product as seven. While it generally scales well, occasional issues arise.

The response time of the support services has been satisfactory for our business requirements.

Positive

Compared with competitors like PegaDM, the platform, and Power Automate offer a more versatile platform that is particularly suitable for workflow applications like ours.

The platform's pricing is reasonable compared to competitors like Apigee. It offers good value for the quality of the product.

Data integration with the platform has been relatively easy for us. We have integrated data from external systems without facing any significant challenges.

I rate the platform as an eight overall. It meets our requirements well and has proven to be a valuable tool for our organization.

Initially, we used it mainly to wrap up Power BI reports for BetterView, creating very simple apps. About a year ago, it evolved into more robust apps for collecting information, particularly for logistics. We developed apps to streamline workflow and gather data for specific operations. We then built a more advanced app that allowed us to communicate with customers—connecting workflow issues, creating problem reports, and sharing shipment updates via SharePoint, which integrates easily with Microsoft Power Apps.

Currently, Power Apps is used mostly locally, within one or two departments. Each app is developed locally, and it’s not really used for enterprise-wide purposes. In our organization of about a thousand people, around six people are developers working with Power Apps. There are likely a couple of hundred users in total across all apps.

Over time, it became a key part of our operations, and we've developed around three or four apps in total. However, the main use case remains displaying Power BI reports. By wrapping reports within Power Apps, we can present them in different formats to create better dashboards, making the process more efficient.

In my experience with Microsoft Power Apps over the past two years, the best feature is its seamless connection with the Microsoft ecosystem. It integrates well with Microsoft Teams, and you can use it with minimal programming, which is typical for low-code and no-code apps.

A downside is that Power Apps is primarily designed to work within the Microsoft ecosystem. It’s not suited for publishing apps outside of the network, so you need additional Microsoft technologies for broader use. While it’s very scalable for simple apps, it's not ideal for large-scale enterprise applications.

I’ve been using Microsoft Power Apps for about two years.

In terms of pricing, Power Apps is cost-efficient.

Overall, I’d recommend Power Apps for its ease of deployment and supportive documentation. However, it's not suited for complex, enterprise-wide applications. I’d rate Microsoft Power Apps an eight out of ten overall.

Power Apps is a tool to create forms and solutions for collecting information from the floor. We have 10 or 15 users at the moment, but we expect to add more.

Power Apps helps our company manage projects, like improvement projects, for example. We can track each project and have a single point from which we can see all the project details.

You can easily connect Power Apps with other databases, like Excel, SharePoint, SQL, etc.

We use GoCanvas to make forms. It's easier to make forms in GoCanvas, but Power Apps is cheaper because it is bundled with our Office 365 license. if I want to create a form in Power Apps, I need some knowledge, but GoCanvas is intuitive.

I've been using Power Apps for one or two years.

I rate Power Apps nine out of 10 for stability.

It should be easy to scale up Power Apps. I don't know because I was only working with one connection through SharePoint.

I taught myself to use Power Apps. When I needed a solution, I found a lot of examples on the web.

Setting up Power Apps is easy because it's a cloud solution. The deployment required one or two people and took one or two months. 

We deployed Power Apps in-house.

We get a return.

I rate Power Apps seven out of 10 for affordability.

I rate Power Apps eight out of 10. My advice to new users is to start a simple solution to get more user-friendly apps to the people.