Microsoft Power Apps Reviews

Right now, our primary use case is very easy to explain. I push applications for applications and supply applications on mobiles because a lot of my customers need to have to access certain data from an iPad or iPhone.

Microsoft PowerApps has made our organization faster and more secure. 

What I find the most valuable is the simplicity to create PowerApps and link them to a list and then bring the list from SharePoint, and sharing the data in SharePoint with other people who do not need to have access to a mobile. 

Creating a PowerApp is very easy. All I do is link and share the result with my colleagues. Deployment is very fast. It takes about a month or so. 

I would like to have more options for changing the layout because customizing something as simple as colors is very hard. The environment is low-code/no-code, so changing something small is hard because you need to find tips for doing that online. It takes quite a few clicks to find a solution sometimes. 

Greater customization overall would be good. 

I would like for them to make it easier to link to a list. It would be great to see not only empty boxes but also those with the first data of your actual list when you create pages. 

More widgets would be better as well. 

The end-user experience would benefit from being more fun. 

I started using Microsoft PowerApps six months ago. 

I have not had any real problems with performance. Any stability issues with PowerApps come from network quality and are not related to the solution's performance. 

Right now, I can't say much about the solution's scalability. At the moment, we are using it for a few users, but I think we plan on increasing our scope in about two years. This would be about 1,700 people in France on the Continental retail side. 

I mostly use the Microsoft website for issues I run into so I have not had any interaction with the PowerApps support team. We also have a very strong IT team within our organization. 

Overall, I give Microsoft PowerApps an eight out of ten. 

Before going with Microsoft PowerApps, we evaluated Mendix and WINDEV. But these are not Microsoft products and we have a big contract with Microsoft. 

I do not have any advice for future users because the solution is holding up well for me. 

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

I had to upload a form, an invoice, specifically, and then using an Azure function, I had to get that form from the Dataverse database and feed it to an Azure form recognizer and write the data back to the Azure Power App.

I like that you can quickly click together a user interface. For all no-code platforms that let you create a front end, you can click together something very quick. 

My problem with solutions like Power Apps and Betty Block blocks and probably with every no-code platform out there is that, as soon as you want to do something custom, something that's not provided by the environment you're using, it gets really tough. You have to work around the constraints of the platform. No-code platforms have constraints. I'm a developer myself, so I tend to not use no-code. I tend to code a lot. 

The notion people have is that no code equals no knowledge, and that's simply not true. Even though you don't have to write codes, you still have to know what you're doing.

I had some trouble interfacing with the Dataverse database. If I could, I'd make the couplings with other software easier. The integration with other software could be better. Any developer who had to work with an application made in Power Apps would find that useful.

There are limited use cases. 

I've used the solution within the last 12 months. 

The solution is a lot more stable than Betty Blocks. I haven't had any crashes or lost data or anything. That said,  haven't used it thoroughly. While I say it's pretty stable, I can't say how it performs under heavy use or big projects.

I've never had to reach out to technical support in the past. 

I've also used Betty Blocks. With Power Apps, you can quickly click together a user interface, that's also the case with Betty Blocks. However, both being no-code have constraints. For example, Betty Blocks was using jQuery one, and at the time we had jQuery three. I wanted to use a front-end framework. That was just not possible since it would mess up the Betty Blocks designer. And that's also the case with Microsoft Power Apps.

The ease or difficulty of the initial setup varies. For me, it wasn't that hard. However, I already had an Azure subscription and a Microsoft account. If you don't have any of that, it's not that easy - especially if you're not very technically inclined. It can be a daunting task.

I'd rate the ease of setup six out of ten. 

The deployment is fast and takes almost no time at all. I developed the application, and I pushed the publish button, and it was published.

I handled the initial setup myself. I did not need outside assistance. 

The license for the solution comes with my professional license, so I'm not sure actually if you pay by the user. For me, it was free to develop with a professional license, which is about 70 euros a month. That said, if you get a lot of users using it, it's not included. I don't know how much that would cost.

Whether it is worth the cost or not depends on the use case. 

We initially chose the solution as it was a customer specification. They wanted to use a Microsoft Power App.

I'm an end-user. 

I have been using the latest version of the solution. However, I don't even know if you can switch between versions.

If you want a complex system with lots of custom work done, then it is not ideal, as you are going to have to face the limitations of the platform. If what you want is a simple tool where you just need to upload some files, or you need to store some data to make a custom CRM application, then it's very easy to use.

It's certainly not a replacement for actual development work, and it's not a replacement for developers.

I would recommend the solution to others. 

I'd rate the solution seven out of ten. In terms of no-code, it's pretty good, especially when you use it with a Logic App, which is part of the Power platform. When I compare it to Orbis or Betty Blocks, it's just a really good product. It has a small learning curve, however, it should be really easy for people who have no previous experience.

We use this solution to provide a cloud-based platform for our clients to develop, connect, and store data from across the full Microsoft suite.

We particularly like the workflow connectors in the forms, for information introduction purposes.

Our customers appreciate the fact that the licensing for this solution is also connected with Office 365, making it a it's less expensive overall system.

It is also very user-friendly in terms of learning curves; it can be picked up very quickly by new users and provides good interoperability between Teams, Outlook, and other solutions from Office.

We would like to see some improvement in the cost of the solution when an organization has a more complex network structure. The advanced connectors are very expensive, which discourages our customers from implementing it.

We would also like to see a more robust library of uses for different system roles to be built into this solution, such as for authorizations.

We have been working with this solution for nearly three years.

The stability of this solution is okay, and really depends on the clients architecture and infrastructure.

When the solution is properly designed at the implementation stage, the scalability is incredible, and the only limiting factor is the cost involved with scaling.

The initial setup for this solution is very easy.

We would recommend this solution to organizations of all sizes. However, the level of investment needed may mean that it is better suited to medium to large organizations.

We would rate this solution an eight out of ten.

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.

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.

We predominantly use the product for a lot of intake forms. There is a lot of data collection and a lot of intake forms. We use Power Application for validation rather than using spreadsheets. It's good for automation, where we need a data repository of the input, which we get from the resource.

It's extremely user-friendly. It's easy to use. Of course, it's a local tool, however, if you're aware of some of the basic Microsoft products, you can really get on with it. That's something which is really wonderful. 

Even a beginner can set up a Power App and run with it. That's one of the most important features when it comes to the adoption of Power Apps.

The solution becomes easier the set up once you get used to it.

It's a stable product.

The solution has the potential to scale. 

I would like to see some of the connectors which they have right now to be more basic. The ones they have right now, they claim, are premium connectors. They should make that a little more affordable and have it in the free version. Some of the basic databases like SQL should be part of their normal connectors, and it should necessarily be premium.

It can be a bit more difficult to set up the first time.

They have a feature that integrates well with Power BI, however, it is not seamless. We'd like a better, more seamless integration with Power BI in the future. 

They need more of a font selection. If I'm in Excel and I'm using a particular font, I'm limited in terms of which I can use. It should allow for use of any fonts under Microsoft 365.

We've been using Power Apps for the last two years or so.

The solution is stable and reliable. There are no bugs or glitches. It doesn't crash or freeze. 

It is scalable if we integrate with other applications like Power Automate and connect it with some other applications or some other databases like SQL. That said, in the current arrangement with SharePoint, we have some limitations. The moment the data increases, if we're able to integrate Power Automate, then surely it becomes a scalable application. Right now it can be scaled, however, it's not something that we are looking to do. 

There are maybe 60 to 70 users at this point of time actively giving us data, however, there could be other applications that people are using.

In terms of technical support, we do have a governance team. The IT governance is a security team who helps us navigate through issues. We raise requests internally within our organization to help us see where the issue is, and they will escalate as required. They might reach out to Microsoft support to kind of get it sorted. That said, we have not found any major issues so far. If we do, our internal team is the first team to go to.

We previously used mostly manual consolidation using Excel, emails, and things like that. There was no other tool before. That said, we used normal Office productivity tools like Excel and Outlook. We went with Power App since we were already using Microsoft and Office 365, which helps us to integrate multiple other Microsoft solutions. That's the reason we thought Power Apps would be the best way for us. It also integrates with SharePoint and is easy to build in. 

The initial setup was not straightforward, however, once you get a hang of it, then it's pretty simple to create things. From a documentation perspective, it's kind of a good guide that they have as far as Power Apps is concerned. It's easy to get started. Like any tool, you have to spend some time understanding and navigating around it. There is just a normal learning curve that is required as with application. You won't really find it that difficult if you are ready to invest the time to learn the tool. There's a moderate level of complexity.

It was not that effort-intensive, yet it definitely took us close to three weeks to create our first app on Power Apps, which was mostly SharePoint driven and had pretty decent complexities. It was not a very straightforward application. It took a fairly decent time. It was not a very long-term project, it was short-term, and we could manage to do it in three weeks.

We have not found it difficult to maintain Power Apps. It's pretty straightforward. We haven't had any challenges so far.

Everything was handled in-house. 

Right now, we are using an enterprise license without the premium connectors at this point. For Power Automate, we are definitely going to need some licenses which we're exploring. 

Depending upon the user requirements, we're still exploring the licensing requirement. Most of the applications that we leverage are without any cost other than the normal license which we are paying for as part of Office 365. We'll take additional licenses depending on the solution and the need.

We have performed a lot of other projects on the Power platform, which is a Microsoft product. So we have used Power App and Power Automate to do many of our automation initiatives.

We are working with the latest version of the solution. 

I'd advise potential new users to have the UI designed well in advance. Articulate the flow in which you want to create your Power Apps so that you can save time. Then, do a dry run using Excel as well. It's important when you're using Power Applications, to have your UI design and the BRD clearly articulated, otherwise it might take a little longer to implement Power Apps. Once you have everything in readiness, it will be easy. 

I'd rate the solution eight out of ten.

We use Microsoft PowerApps for very small use cases. For example, conducting internal surveys, or say some of the key business stakeholders want day-to-day reporting. Using PowerApps, we are creating such reports for those executives.

We connected PowerApps to the relational database, which generates the report. 

Also for contract review and approval of these types of use cases. Those are, in my opinion, very simple use cases. There are no complex rules or decision-making processes, which is why PowerApps was designed.

It offers integration with several Microsoft products, including SharePoint and Outlook, in my opinion, is a huge plus. 

It can also integrate with Microsoft SQL servers, which makes it easy, and you can send reports and create business applications from it.

In terms of workflow automation, I believe that capabilities for creating the entire business process are required, or, at the very least, the option to model the business process, define complex business events, handle them, and route them to appropriate business stakeholders.

Those, I believe, are the critical areas that require improvement. 

For the time being, it is only an application development platform. I am not counting a business processing management platform, only working on capabilities with business process management.

It is extremely stable. 

The apps that we created were not particularly complex. We did not thoroughly test PowerApps to determine their true capabilities. It was similar to tactical applications built as part of the POC to ensure what capabilities of the PowerApps could be used.

It was not used for any critical business application.

I believe it should be scalable. 

However, in our organization, we only have approximately 15 to 20 people who are currently using it.

The initial setup is straightforward. It does not take long.

Maintenance is minimal. It is only one or two people who keep it running.

I believe it simply depends on the complexity of the business process. If you are serious about implementing a complex business process, I believe you should use a platform like Appian or Pega.

In terms of low code automation, I believe those two platforms are quite mature. They also develop capabilities such as robotic process automation and process mining. That's where the most value is because business users don't just want one thing; they want several things at the same time.

I believe it is preferable to use a platform that is robust in nature. Appian and Pega, in my opinion, would be better for them. However, if you only have a simple application that does not require much scaling, I believe you can use PowerApps, such as a simple three or four screens or forms. That should suffice for Microsoft PowerApps, in my opinion.

We are Microsoft partners and resellers.

I would rate Microsoft PowerApps a seven out of ten.