Microsoft Power Apps Reviews

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.

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.

It's for building custom apps, which is very similar to APEX. We also use it to build small business applications related to any Microsoft products.

In Power Apps, it's the native integration with Microsoft products. This is definitely the most powerful feature.

There is always room for improvement in stability. 

It was three years ago when Power BI started to develop. But for Power Apps, we have a special center of excellence, and I am not part of it anymore because it's too bothersome.

I would rate the stability an eight out of ten. There is always room for improvement. 

I'm not aware of any issues with Power Apps' scalability because maybe we didn't use it so heavily.

I personally never used Microsoft support, but based on references from other colleagues, they're quite satisfied with the Microsoft support team. 

Neutral

We had some cloud-based platforms for development. Microsoft Power Apps is a low-code application. One of the beauties of Power Apps is the fact that it's low-code, so you don't need high-skill development experience to build. This is my opinion.

The initial setup is straightforward. From a setup point of view, I know that Microsoft provides quite great capabilities.

The deployment time varies and depends on the environment. It's a cloud solution. It's a private cloud, part of the Microsoft 365 tenant.

I would rate it a seven out of ten. It's stable, reliable, and easy to implement.

Microsoft Power Apps has quite great AI capabilities. They can embed the functionality of Copilot, and all the AI capabilities of Microsoft 365 can be easily used in Power Apps, as per my knowledge.

We mainly use Power Apps for small applications. Ninety-nine percent of the work is on Internet or intranet solutions, specifically E2E and B2E. These solutions are designed to be developed quickly without being overly complex or requiring high performance or extensive handling of large datasets. In addition to these scenarios, integrating with other platform tools like Power BI and SharePoint enhances the solution. We generally avoid developing for B2C or B2B scenarios due to licensing issues and the nature of those markets.

Power Apps facilitates form creation, application planning, and automation. We have encountered scenarios where automation was crucial, such as managing emails according to SOPs and handling basic ERP tasks like user password changes and role assignments. Power Apps and Power Automate have automated these processes efficiently.

Power Apps offer a wide range of integrations and login options. Typically, we use SharePoint as a backend for these apps. They are both free and paid versions; the paid options are extensively used. 

There have been many improvements. First, performance could be improved. Second, there should be more flexibility in implementing features and functionality. It would be beneficial to have two modes: a developer mode, where developers can utilize more components they build themselves, and a mode for handling large amounts of data. 

Custom error management is also a challenge. Customization, including the ability to integrate custom code, would be valuable.

Due to performance issues, managing large amounts of data can be challenging. Exception handling poses significant challenges. Creating custom connectors and dealing with paid connectors can be expensive.

I have been using Microsoft Power Apps as a partner for four to five years.

You must design your application carefully if you're dealing with a large amount of data and numerous screens. Understanding the context is essential; our platform is designed for people with limited technical skills to develop applications without extensive technical training. However, when dealing with larger datasets, such as ten thousand records, technical considerations become important to ensure optimal performance.

The performance is very poor.

I rate the solution’s scalability a four or five out of ten.

Microsoft's technical support is pathetic. There is no guarantee that they'll be very helpful. They are straightforward. They have experts for each specific topic. They do not exceed their domain or technology. Generally, for significant issues where you need help from Microsoft, you require someone or a team that spans domains. It could involve network problems, process issues, database security, etc. Sometimes, when discussing these issues with their experts, it can take weeks for them to explain the problem entirely. 

Neutral

The initial setup is straightforward. It is online. Creating an environment and assigning users doesn't take time. One person is enough to do it.

The basic license allows most business users to resolve issues. It is included with their Office 365 license, so using Power Apps is fine. ROI is good because we already have it; Microsoft provides it so we can use it. However, licensing becomes more complicated for anything extendable or requires a complex solution. For example, licensing can be unpredictable and unclear if you need a B2B solution.

The long-term impact and license are challenging to understand. Many businesses avoid taking chances due to past negative experiences, and even Microsoft representatives sometimes struggle to clarify these aspects. Personal experience indicates that while they offer discounts, there's uncertainty about future costs after six months or a year. Licensing has improved but remains complex despite recent updates.

I rate the product's pricing a five out of ten, where one is cheap and ten is expensive.

We have started exploring those parts. It is in the initial stages and capable of performing simple tasks that are helpful. We are still exploring how it can work with profiles, and other AI features that Microsoft continues to introduce. It provides a basic starting point within its capabilities. 

Microsoft Power Apps is a perfect tool. Understanding its limitations is crucial to identifying where it best fits within organizational solutions. It excels in scenarios requiring quick turnaround times, offering easy maintenance with minimal technical expertise needed. However, it's not suited for complex enterprise-level solutions.

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

We use Microsoft Power Apps to support some IT processes and for employee evaluation. Sometimes, we use the solution to prepare electronic forms where we cannot use Microsoft Forms. We also use Microsoft Power Apps to prepare small custom applications.

I like the solution's ability to approve some tasks electronically. When we use Power Automate to build workflows, one of the steps is the approval process. It is very convenient to have the possibility of accepting some activities.

Because we have a lot of data and users, achieving an appropriate level of security and privacy is sometimes difficult, especially for sensitive data. I do not mean that the system is lacking in this area; rather, we need very competent people. I believe we don't have enough people to appropriately secure our data and control the transfer of this data.

I have been using Microsoft Power Apps for three years.

I rate the solution a nine out of ten for stability.

I rate the solution’s scalability a nine out of ten.

In some cases, it's very difficult to get very competent reactions from the support team regarding our tickets.

Neutral

The solution’s initial setup is easy.

We have seen a return on investment with Microsoft Power Apps regarding time savings.

On a scale from one to ten, where one is cheap and ten is expensive, I rate the solution's pricing a six out of ten.

Microsoft Cloud can integrate with on-premise infrastructures, but this requires additional licenses. These additional licenses are expensive for us because we have 8,000 employees. Integrating cloud services with on-premises systems is not easy for us. This is mostly not because of technical problems but because of the cost of such integrations. I would recommend the solution to other users.

Overall, I rate the solution an eight 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.

We use the solution to implement new Teams apps. Some customers want apps on every mobile phone in their company. This is implemented using Dynamics or SharePoint, with a list of plan data displayed on the mobile phones. Everyone enters the data and plans when holidays or machines, like magnetic resonance scanning machines, are to be used. Everyone enters this data and coordinates using that Blackboard application. It is for enterprise resource planning or HR planning.

Microsoft Power Apps is the building block for creating applications, similar to how children use different types of blocks to build structures. 

Power Apps is a part of the Microsoft Power Platform suite, enabling users to build custom applications using various components. It is more akin to SharePoint in creating web pages and applications. It allows integration with SharePoint, connected web services, data files, and more.

You need to be familiar with Microsoft Power Apps' infrastructure. If you understand Power Apps, it becomes easy to use; otherwise, it may seem challenging. SharePoint can be a complex product, but if you have someone guiding you or showing you how to use the apps with online checkpoints, then it becomes much easier.

To utilize Microsoft Power Apps effectively, it's essential to grasp its integration with SharePoint. I recommend considering a structured course instead of relying solely on YouTube videos, which can be time-consuming. Whether managing a Spanish restaurant, an Indian restaurant, or any other business, investing in formal training is crucial for efficiently getting your business up and running. This approach saves valuable time compared to piecing together information from scattered online sources like YouTube or random articles across the Microsoft ecosystem.

Microsoft Power Apps allows companies to efficiently manage and utilize measurement or scattered data in competitive environments. While existing solutions are available, understanding how to leverage these solutions effectively is crucial. Power Apps provides an intuitive interface to seamlessly implement measurement data from an open environment such as a bakery or similar establishments.

Microsoft provides excellent technical support. They are known for their competence and respond within a few business days.

Positive

The solution usually takes half an hour to start. However, getting the simple apps running might take days, and some alerts take one or two days. The most difficult part is accessing the data needed within your ERP or HR system.

The license costs around 20$ per user per month. While it is an expensive piece of software, users are willing to pay for it.

SharePoint has been used since its inception in 2001, leveraging web service proxies and the initial framework where any web service could provide authenticated and authorized access. Custom connectors are required to access data. The connected infrastructure does not significantly affect the authentication and authorization requirements. This flexibility allows seamless integration with infrastructures like Google, SharePoint, SAP, and others.

It allows you to integrate ideas like viewing the inventory of used machines or any other inventory-based business scenario. These apps can be accessed on your mobile phone or laptop and displayed within Teams, making them interactive. It serves as a versatile platform for various business logic needs. Additionally, you can build and program apps without Teams using a standard browser, though many customers prefer using it alongside Teams.

It is a development environment that simplifies application creation, though, like any programming, it is susceptible to errors. When integrating systems such as banks, credit card companies, or health insurance providers, ensure proper authentication, authorization, and accurate data transmission. Understanding the origins and significance of your data is essential, often requiring collaboration across departments to align on business data definitions—a resource-intensive process. Developing sensitive applications in such environments can be challenging, especially regarding data protection compliance.

I recommend Microsoft Power Apps to small businesses, such as Spanish restaurants. If you have a small medical practice, like a dental office, you might experience regular service issues, especially in Germany. However, despite these issues, if you need to store data and to interact with it using mobile phones, I recommend Microsoft Power Apps.

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

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

Power Automate is like process automation.

Any task which you do on a recurring basis or a daily basis, you can simply automate. For example, if you have a use case where every day when you go home you need to book a cab. What I can do is I can automate that task through Power Apps at a scheduled time every day. If I'm leaving at about four o'clock in the evening, by 3:30 I can run that Power task and book a cab every day.

With Microsoft, the main benefit that we get is it's easy for a layman to understand it. That's the advantage of it, it's user-friendly. 

The way it integrates with the other applications is very good. The experience is seamless; there are no hurdles. Connectors are easily available, which can help you connect with some third-party apps if required. 

The initial setup is easy.

It is stable and reliable. 

We can scale it. 

They probably need to improve intelligent document processing. In terms of reading the documents, whether it's a Word document, an Excel, a PDF, an HTML, or a webpage. Identifying the key things with its own intelligence is something that Power Automate and Power Apps need to improve.

I've used the solution for close to a year now.

It is quite stable.  It gives you that assurance since it is from Microsoft. The stability, the reliability is definitely there.

It is scalable. We have a lot of ground for it to scale it up, and add more and more apps or users can be added as per our business requirements.

It's being used widely by many people, in fact. However, it's hard to pinpoint the exact number of people who benefit from it. Anyone can quickly learn how to use it as well. 

I'm aware of UiPath and Automation Anywhere which take a longer time to implement. 

It's very easy to set up. You should have all the licenses available. It's quick and easy to implement, and you can get your hands on it immediately. It doesn't take too much time to get up and running. In contrast, its contemporaries like UiPath and Automation Anywhere are not so quick and easy to implement.

The cost depends on which bundle you get from Microsoft. For example, if you go with the standard Office 365 with the other packages around it, it's good enough. However, if you go for anything specific, you'll have to think about it and customize your requirements. If you go for 365, your cost would be less. If you go for Dynamics 365 with Azure, then it's a complete package that will be expensive.

We are Microsoft partners. 

My advice for those people in tersted int eh product would be to try it if they are looking at implementing something very quickly with minimum cost and minimal training. If these are their objectives, then Microsoft Power Platform is a very viable solution.

I'd rate the solution eight out of ten.