Microsoft Power Apps Reviews

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

Microsoft Power Automate is primarily used to update some legacy systems for our client, as well as government compliance systems and web-based reporting systems that don't have APIs. Microsoft PowerApps has the same use case. It's the front end and is the part that is interacting with the client and interacting with the collected data.

We really like Microsoft PowerApps. When compared with Microsoft Power Automate, it is a bit more mature, and we're able to build things pretty rapidly.

It's a different paradigm to build around, and it's a different programming paradigm. It's more like Excel in that you build formulas and pieces, but we've been able to build some fairly sophisticated business logic inside of it. As a result, we believe that is much more mature. I'd say that's around an eight, eight and a half, out of ten.

I believe, Microsoft PowerApps is still in its early stages. I believe it is far more mature and integrated. I would say the programming language, because the drag and drop, low code, no code, its nice to get started, but you really want to be able to work as a programmer with an IDE and real code, and we've been able to start to do that a little bit and integrate a lot of JavaScript with RPA, with Power Apps I haven't been able to do that. I believe there is a way to do it by putting the data into Git. I just haven't used it yet, and haven't needed to.

As it's a cloud-based app, the development environment has some really nice parts and some that are a little clunky, but overall, I'd say it's a good product.

We have been using Microsoft PowerApps a bit longer than we have been using Microsoft Power Automate.

We haven't fully launched a product yet, but I will say that development is quick and we can make changes quickly. I can't speak to the app's scalability just yet.

I've only used it through an RPA. We either did it for many years, or we did it by hand with JavaScript. We would use some tools to actually grab for web-based things, not desktop-based. We wrote tools that would allow us to take control of the website and then modify it on the fly while automating these processes.

We did it all with secure JavaScript, which is a lot of work and custom code, and it's difficult to maintain, so having a tool like an RPA tool, where we can take that business logic, put it in there, and then somebody who knows the stuff can come around after us and go, okay, I see what they did there, would be great.

We believe we have exploited the tool and pushed it to its limits, and we are still learning about its strengths and weaknesses. It definitely has room for improvement, but when I give it a seven, I mean it's functional. I can get the job done, but it's far from ideal.

When I say Java, what I mean is that when we were doing automation, we were primarily working on web automation. My phone is dying, so that's why I cut off.

We would write a lot of JavaScript code to automate, automate, and update these external websites that didn't have APIs, that we would read from. We are now reading from spreadsheets and updating data for them, then retrieving data from the results, and this simplified things significantly.

We wanted to see what people were doing with UiPath. I'm not really using it yet. I've looked into it a little bit, but it just hasn't been a driver for this project yet.

I am just using the product. I evaluated a problem and a solution set for a client, and I just evaluated these tools and said, despite their youth, these tools look like they are good. We looked at UiPath, but the price tag was expensive for a nonprofit, so money was an issue. We had a very limited budget from a grant, so we had to work with a toolset that wasn't on par with the Fortune 500. So far, we're pleased with the solution, and it's working. There are days when it is frustrating, but I've been doing this for 40 years and there are always challenges with tools. We do not have a relationship with Microsoft.

I would rate Microsoft PowerApps an eight out of ten.

This is a low-code solution that I am using for making applications.

The most valuable feature of this solution is the Model-driven or Canvas application-making platforms. The power of the two gives us exactly what we are looking for.

In an upcoming release, I would like to see custom APIs, better integration with other solutions, and more connectors available.

I have been using this solution for approximately eight months.

The solution is stable.

We have plans to scale the solution in the future and it is very scalable.

We have approximately 35 people users using the solution in my organization and we plan to increase that number to 75.

The customer service has been very responsive and has always given us the help we required. Alternatively, there is a large PowerApps community that can help anyone find a solution for their problems. The overall support is excellent.

The initial setup was easy, we had no problems. 

We have a small team that does the maintenance of the solution.

I pay nine dollars monthly for the subscription to this solution and the price of the is reasonable.

My advice to others is to review their use case and if it fits then I would recommend they try this solution.

I rate Microsoft PowerApps a ten 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 use Microsoft PowerApps for the typical use cases including website creation and a work portal, covering all the operations involving the manufacturing side of my customers.

There are three app-building interfaces available in PowerApps. Canvas is model-driven. Power Pages, which was Power Portal, which has more low-code, no-code capabilities and makes web design easy for the everyday user to create a website. Lastly, Power BI reports, or Microsoft DataWorks, which we have integrated with our data provide us the option to work collaboratively.

Most of the people in our organization using this solution are business people. They are not experts in technology and are not familiar with how to use the application. They use Excel and other documents to collaborate. Moving Excel to the application helps them access different data sources. It allows us to provide all the information in one single place. Everyone can view the data based on their role or access level.

The most valuable feature of Microsoft PowerApps is the ease of use to create an application. For example, if you use the Canvas app, there is a feature that you can upload an image, and it will easily identify it and convert it into the application.

The solution is convenient for using Power Effects so we can write customized business logic.

Microsoft PowerApps is not responsive in nature. For us to make an application responsive, it requires some effort. We need to work with CSS, HTML5, or JavaScript.

I would also like to see improvements made to the integration with other data sources, including Azure Databricks or Spark. When we connect from DataWorks, CDS, SharePoint, or OneDrive where the actual Excel file is kept, it is easy. However, if we connect with other data sources, we need to do a no-data filter, particularly when there are in-built integrations available. 

Out-of-the-box connectors, like dataflow, would help to load the data from those data sources into CDS.

For future releases, Microsoft PowerApps should add more templates that help bring more experiences to the websites.

I work as an IT analyst. I have been using Microsoft PowerApps for two years.

In our organization, PowerApps is used by program managers, IT engineers, IT analysts, assistant consultants, and delivery partners.

The initial setup of Microsoft PowerApps is straightforward. 

For deployment, we use the ALM CoE kit, and GitHub through the pipeline. It is done through the team, creating a Dev environment for each pre-Dev and production environment. When we have completed testing and validation, we proceed with staging and then production.

We have not implemented using an automatic deployment through Azure Pipeline as there are a lot of bugs. We are still doing the implementation manually.

Deployment is done by our customers' teams. They are handling the pipeline activities.

The ROI is always positive. Our customers who use this solution can quickly create and circulate through a group. For example, for an innovative idea, you can create an idea zone, QC, or something similar. You can create a form and circulate it via email through PowerApps.

PowerApps has been adopted by all major partners and Microsoft is widely used. We use Microsoft Teams to collaborate. You need to have licenses. E1 plus Intune or E1 plus licenses is enough for everyone to use PowerApps as it's free, even if you are using data sources like SharePoint.

If you want to deploy something with RPA or Power Virtual Agents, you will need to think about the licensing model and the capabilities of the AI builder. AI can deploy the AML model, so you can use the capabilities, meaning you need the licensing.

For an organization looking to implement Microsoft PowerApps, they should consider the timeframe required and the experience they would like. 

Responsiveness is a concern with PowerApps. If you want to build an application for your desktop, tablet, or mobile, the application needs to be responsive on all screens. PowerApps is not responsive to these requirements. If responsiveness is not a concern, then I recommend this solution.

I would rate this solution a seven out of ten.

With Power Apps, we create some of the collaboration forms for our employees to use during the pandemic. We can record our employees' status health daily, and start a database of the information. After that, we can track using Power BI if there are any symptoms or if the risk is low, high, or medium. We use it basically for self-declaration forms.

The solution offers good integration on the Microsoft Power platform. You can use and develop apps, local apps using Microsoft Power Apps. It helps automate processes. We can do the monitoring and tracking of the Power BI app in Microsoft. 

It's very easy to set up.

The solution is stable.

The scalability is good.

The flexibility of the user interface could be better. Currently, they are using the Microsoft OMS, Management System. It would be ideal if we could customize the layout of the user interface.

I've used this solution for one to three years. 

The solution is very stable. We haven't dealt with bugs or glitches. It doesn't crash or freeze. It is reliable. 

You can easily scale the solution as needed. 

We have 500 people that use the solution. We use it quite regularly. We do not, however, plan to expand usage at this time. 

Technical support has been good. They're also very supportive. When we have any problem or issue, we can reach out to them and they will reply.

The initial setup is not complex or difficult. It's easy to set up. It's very straightforward. 

It took us about four to five months to set everything up. The apps vary in how long it takes to develop and release them.

We develop everything in-house. We handled the setup in-house as well. We didn't need any outside assistance. 

We have not yet seen any ROI.

I cannot speak to the exact pricing of the product. We are, however, heavily affiliated with Microsoft.

We're users and Microsoft partners. We use a lot of Microsoft products.

It's my understanding that we are using the latest version of the solution. 

I'd recommend the solution. Everyone would be able to use it as it is not overly technical. 

I'd rate the solution eight out of ten. 

The primary use case for this solution for us is building in-house applications rather than having to purchase them. We build fairly basic applications and we would rather use Power Apps to deploy them or create them in-house.

The way this solution helped us improve is by allowing us to collect data by combining it with phones and the tools Microsoft uses to send out surveys and also use it for a number of automation and requests. It creates forms with which people can make requests or respond to surveys and those are worked on the backend. The whole process is done using Power Apps.

The features I find the most valuable are the 365 and Microsoft applications integrations and the automation.

The area where this product can be improved is the documentation. When we get stuck it's with the documentation when we are not able to find the codes we need. The solution requires a lot of codes and understanding of the scripting language. Most of the time I end up going to forums to get them. I would like to see Microsoft come up with a knowledge base for Power Apps.

In the next release, I would like to see more integrations because there are some that are not available and we end up having to get adjacent script to work on to work with that.

I have been using this solution for two years now.

My impression is that it is very stable. I would rate it a 10, on a scale of one to 10, with one being not stable at and 10 being very stable.

We rarely scale when it comes to Power Apps. Once you deploy the application, that's it. So if you need to scale something more robust you probably have to deploy a new one.

Currently, there are over 500 users of Power Apps in our company.

We plan on expanding because it saves us a lot of cost in terms of the application that we currently use this for.

I am not even aware if there is any technical support for Power Apps because most times we have to go through online communities and forums to get what we want. I think the support for Power Apps should be something Microsoft could look into.

The initial setup was straightforward because they have a quite number of templates that you can pick from. The deployment does not take long as it comes with the Office 365. If you have Office 365, you have the Power App enabled in your directory.

The ROI is visible considering the number of applications we have been able to use it to build.

The Power Apps comes included with the Office 365. When you purchase a business standard license, the Power Apps comes included.