Microsoft Power Apps Reviews

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.

We are a big global company that is involved in a large volume of setups involving Microsoft solutions like Power Apps, Power BI, and Power Automate for different environments across departments in organizations functioning at a global level. So we are involved in delivering services while focusing on the setup processes for different environments and departments. It helps the people at work since solutions like Power Apps and Power Automate function excellently.

I would say that it's a very advanced product because it empowers people to do simple things, which previously may have required people to have some technical skills. So, no matter which department or what technical skills a person possesses, it has become very easy to build or automate certain processes. In my company, we chose Microsoft Power Apps since it helps us with small and medium tasks like making certain processes, generating reports, and so on.

Though I don't remember enough details about the solution to comment on it, I think the solution does need to add some technical features to it since I remember that we had faced some gaps while trying to automate certain processes. One area where the solution lacks is the limited size of the database it offers its users. So, some businesses planning to scale up may face certain restrictions while using the solution. Microsoft Power Apps also needs to provide its users with certain specific connectors within the solution. I won't be aggressive enough to complain more about the solution since, in our company, we have a lot of specific handmade tools, and so we don't explicitly expect Microsoft to create specific connectors for Power Apps.

I have experience with Microsoft Power Apps for three years. Also, I don't remember the solution's version since I used it six months ago.

The solution is generally stable, but some limitations, such as the embedded database usage limits, can impair its functionality.

Since my previous company had a specific license agreement with Microsoft, the solution was scalable. The solution allowed for adding new licenses to the company on demand through a step-by-step procedure. This task was carried out during the first stage of the solution's deployment process after we discovered the need for additional licenses.

So, around 65,000 employees were using the solution in the environment flawlessly. Also, my previous company had plans to increase the number of users. The company had decided that since the platform was an excellent one, it should predominantly be used for small and medium processes. Management was planning to scale it up and was waiting for Microsoft to provide a more powerful capacity solution at a time when the company had around 1,00,000 employees.

Technicians from Microsoft visited our company and helped us sort out certain issues, specifically strategic issues.

In our company, we were previously using Microsoft SharePoint Dev. We, later on, chose Microsoft Power Apps since it helps us automate small and medium processes.

The initial setup process for the solution is not complex. So, the company had made arrangements to help us manage the initial kickoff and deployment processes. Since it may not be a very easy process, it is more or less a mediocre one.

Because there were a lot of employees in my previous organization, it took around one year for the deployment process to be completed. Taking into consideration the environment, the initial settings, and the need to take care of security, the entire deployment process would take around one year.

The deployment process was carried out in three stages. If we consider the deployment's first stage, it is free for one year, though I can't recollect it entirely. However, I can say that it was related to Microsoft Azure since it was about security involving steps like how to create the security levels and which levels one can create. So, this process was carried out to create, considering our structure, resources, strategies in the company, security, and environment. The second stage involved the creation of real environments and splitting environments, divisions, and departments. The third stage involved communication and promotion. We then created the specific site devoted to the tools in Power Apps before creating a knowledge base consisting of general articles, specific articles, and the general question and answer section.

We sourced the solution's version for free projects from a company, and the company was really helpful.

Regarding deployment and maintenance, our company had technical resources, promotional resources, analytics, and so on. So, we had a big in-house team using all the available resources. So, around fifteen people in a team were looking at the implementation part of the solution. Also, our sales company had a team of ten members. In short, a significant number of resources were engaged in the solution's maintenance phases.

I had not participated in the evaluation process, and our management communicated with consultants and other resources to investigate solutions, after which they possibly chose Microsoft Power Apps.

I would recommend those considering the solution give it a try. Our organization had some initial doubts, but after comparing it with other platforms in the market, we found it to be highly advanced. Additionally, since we have received excellent support from the vendors, we are confident they will not leave us to face any issues with the solution alone. Many consulting companies are also available to provide further assistance. These factors have made Power Apps and Power Automate popular. Owing to the solution's ability to solve a company's small and medium automated processes, I rate the overall solution an eight out of ten.

We are using Microsoft Power Apps for data collection and processing for small intergroup business applications for our internal needs. 

Overall the solution is reliable.

The scalability of the solution could improve.

I have been using Microsoft Power Apps for approximately two years.

The stability of the solution has been good in our usage.

I rate the stability of Microsoft Power Apps a seven out of ten.

We have approximately 1,000 people using the solution. There are some applications that we will increase the usage of. However, this depends on the use case.

The scalability of the solution depends on the use case of the application being used.

We have a dedicated support team at Microsoft Power Apps for our needs.

I previously used IBM Lotus.

The initial setup of Microsoft Power Apps is straightforward. The implementation depends on the complexity of the application being deployed. It can range from one week to one month. I have not implemented an application that has taken longer than half a year.

We have a team that does the implementation of the solution, such as a delivery manager.

Our enterprise contract with Microsoft Power Apps includes the application feature platform in our subscription package, so we are not incurring any extra expenses. All of our other subscriptions are also part of our license agreement.

I would recommend this platform to others if they have a dedicated internal team with the appropriate experience.

I rate Microsoft Power Apps seven 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.

We have built a couple of apps ourselves, but mainly, we are building the apps for our customers.

The best aspect of Microsoft Power Apps is its time-to-market efficiency. Unlike traditional programming, it doesn't involve lengthy coding processes, allowing for rapid deployment. You can input your requirements and get started without writing millions of lines of code.

The product is expensive. It costs around 20 euros per month.

There is no stability concern from clients. It could be faster, but it's stable. When it is on your infrastructure, it takes more time to work than the public cloud.

Microsoft support is not solving your problem. They're closing the ticket and telling you to open a new ticket. When you're writing back, they're not answering. When you are calling, they don't hear you. Microsoft support is the cheapest support.

The initial setup is easy because you don't need to write a million lines of code.

Microsoft Power Apps runs only on the cloud. There is no on-premise possibility to run it. You can run a connector connecting your on-prem infrastructure and the cloud. We are developing on Azure Active Directory. We're also using it because our clients also use Azure. We have big and small Azure clients. Everything is in the cloud.

If you have a Microsoft 365 subscription. You already have access to Power Apps. You can utilize pre-built apps and even create your own without needing additional data apps.

The solution is fast to adapt.

Overall, I rate the solution an eight out of ten.

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.