Microsoft Power Apps Reviews

We're working on B2E applications and therefore we can't really get into specific use cases.

The solution allows you to use data to create excellent UI and quickly deliver an app. It speeds up production time.

You can't add too many filters onto anything you build, otherwise, it will be very slow and it will affect your performance.

For example, some companies want to use a lot of dashboards for Excel Spreadsheets or Sharepoint. If you put everything onto a mobile app, you won't get the kind of performance that you would if you just worked in Sharepoint. A mobile app has certain limitations.

I've been using the solution for the past year or so.

The solution seems pretty stable, or, at least, it's moving in the direction of becoming very stable. We've been happy with it. It's reliable.

The solution is quite scalable. There are third party connectors, or you can design your own connectors if you like. It's very customizable, which makes it very flexible and easy to scale.

I've never had to reach out to technical support yet. We've found that the documentation that they offer is good enough to answer any questions that we have. We also have many experts in our organization. We'll ask around internally before venturing out and asking Microsoft.

The initial setup is pretty straightforward. They have a lot of third party connections. It's easy to connect things if you need to. However, this can add to development costs. That said, it's nice to have the option.

I don't directly deal with the actual billing. Therefore, I don't know the exact cost or the licensing structure. That's an aspect of the solution someone else handles. That said, it's Microsoft, which tends to be a bit more expensive. It might now be the best option for smaller customers. 

I'm most likely using the latest version of the solution, although I don't know the exact number offhand. We have a partnership with Microsoft so we're likely to be using only the most updated versions. Everything else: Power BI, Power Stack, AI, and all that, are also on the most updated versions.

While for larger companies, it's probably not too much of a problem, cost-wise, to adopt this product, for smaller firms, it's likely too expensive.

Overall, I would rate the solution at a six out of ten. It's useful, however, there are limiting aspects of the product that could be improved upon.

Our primary use for Microsoft PowerApps is to develop production-ready applications.

The most valuable feature is the simple data connectivity components. With no code, you can use multiple data sources with different software systems.

Integration with databases and other tools needs to be improved.

I have been working with Microsoft PowerApps for about three years.

The stability is fine and we have no issue there.

I am a bit concerned about scalability.

I have my own technical support team so we have not had to contact Microsoft technical support.

I have experience with Zoho Creator and I find that the environment is much better. The database integration is better and creating a production-ready app is very straightforward.

The initial setup is straightforward.

The problem that I am having with Microsoft PowerApps, and other no-code or low-code solutions, is that younger developers are not comfortable with it. They are more comfortable with C# because it gives them more control over what they are doing, and more control over the testing.

My advice for anybody who is implementing this solution is to first conduct a large-scale, enterprise-level project. This way, you will see if the product is scalable enough for your requirements.

I would rate this solution a seven out of ten.

We are customers and resellers. We mainly collaborate with Microsoft and supplemental applications.

I like the containerization of Azure. We are trying other architectural options that they offer.

There is always room for improvement and with PowerApps, there is a long way to go. 

The flexibility and the user interface need improvement. 

The speed, as in how fast things can be done, needs to be improved.

The workflow needs improvement and should be included in the platform.

We have been working with Microsoft Azure for the past year.

The support is good.

Here in Greece, we have enough support for Microsoft. There are some government-level agreements and county-level agreements. 

It is easy to deploy, although we have some experience.

It seems pretty straightforward.

You have to be careful with pricing.

It might be too complicated to continuously monitor the business consumption and what to pay.

It's not something you can easily rate, as you have to rate according to specifications and characteristics.

It is a good product but I would like to see the flexibility issues improved, and there are issues with the user interface. You have to use the interface in a specific way.

I would rate this solution a seven out of ten.

The most valuable features are low-code and fast development.

Microsoft is evolving constantly.

PowerApps is still a bit new compared to a slightly more mature product such as OutSystems.

OutSystems has many features that are still not available in Power Apps.

Simple things like navigation are better with Outsystem without much coding.

The key is the licensing; the fees could be reduced, especially at the enterprise level.

I would like to have more usability, with more fanciful navigation. More like what you would find in Outsystems BI. They offer more drag and drop navigation, and more advanced navigational options around the drag and drop lists and hierarchical navigation out of the box is literally a drag and a drop.

It can be done in Power Apps, but you need to do a bit of coding to achieve the same thing. It's lacking in features.

We are in the evaluation phase and have been using PowerApps for three months.

We are using the latest version of this solution.

To be fair, we are relatively new to this solution. It's stable but at the moment in terms of stability, the enterprise version is more sustainable.

The version that I am using is not at an enterprise level. If you want to increase in size you have to purchase more licenses. It's scalable as long as you purchase the license.

We have more than 100 users in our organization.

I have not contacted technical support. We haven't had the need to.

I am currently working with Microsoft Power BI and Power Automate, which goes hand in hand with Microsoft Power Apps.

The initial setup is quite easy, it's as simple as turning it on.

It took us two weeks to deploy it and to come out with the first prototype.

The licensing fee at the enterprise level is expensive.

We are currently doing a proof of concept with Microsoft, we are evaluating some of their products.

I would recommend Microsoft Power Apps to anyone who is interested in using it.

As of recent Microsoft has been evolving the Power Platform rather aggressively. 

For example, I'm using Power BI, and every month they have a rollout of new features, and with Power Apps, when you compare to one year ago has evolved quite a bit, and so has Power Automate.

Microsoft is on a journey of evolving. 

It's a good tool now, but it will be a great tool soon.

I would rate this solution a seven out of ten.

The most valuable feature of Microsoft PowerApps is the user interface.

Microsoft PowerApps could improve the speed of Power Automate, it is not very fast.

In a feature release, any additional features would be beneficial.

I have been using Microsoft PowerApps for half a year.

The stability could be better when it comes to performance.

Microsoft PowerApps is simple to install.

The price of Microsoft PowerApps is reasonable compared to other solutions.

I rate Microsoft PowerApps a nine out of ten.

PowerApps is mostly a front end. It's a form where users can input information, and it gets goes into a database.

If you want something that you can use for cellphones, multiple tablets, and things like that, you can use PowerApps for the front end. It gathers all the information, and the information goes somewhere else. 

PowerApps can't do a lot of things that users need now. For example, it can't handle signatures. 

We just started using PowerApps last year.

I don't know if PowerApps is suitable for the enterprise level. When we need an enterprise solution, we don't use PowerApps because it's too complicated for the users and creates too many headaches for IT.

It's hit or miss. Microsoft makes changes so fast that even their support engineers are confused. Sometimes I'll change my settings, and then I'll go back to my settings the next week, and I can't find it. Finally, I realize that Microsoft changed something, and this particular setting is now integrated into another part of the menu. They keep doing that. It confuses the admins and even their own people.

Microsoft had a solution called InfoPath that they discontinued and replaced with PowerApps. I still like it much better because of the licensing issues. PowerApps' use case is more general. Microsoft took InfoPath's functionality and made it more complicated in PowerApps. 

They did the same thing when they introduced the new version of Power Automate. Microsoft took away the best workflow feature. Without that particular one, it's hard to create general workflows for somebody else. Many people don't know how to create workflows, so they rely on IT to do that for them.

Setting up PowerApps isn't straightforward. We allow users to be citizen developers, as they call it, and around 95 percent of the time they end up going back to us, saying, "Hey, we can't use this. We don't know what to do. Help us!" As IT, we're spending a lot of time creating these forms for them instead of users doing it themselves.

There are better solutions like Jotform, which is a complete form solution. We're now using Jotform instead of PowerApps because the workflow is simplified. It can accept signatures, and there are many widgets you can use. Jotform has drag-and-drop functionality. However, even with drag and drop, many users still can't build forms and need help from IT. 

It's just a matter of which will make the best use of your time. If it takes a long time to create something in Power Apps and half the time to do it in Jotform, I would make it in Jotform and be done with it. We also use Microsoft Forms for simple forms instead of PowerApps.

I rate PowerApps four out of 10. 

We use the solution for making forms for Office 365.

The solution is easy to use and map.

The solution should have more integration with other platforms. 

The licensing price could be better. 

We have been using Microsoft PowerApps for five to ten years. 

The solution is definitely stable. 

For sure, the solution is scalable. 

As the solution is deployed on-cloud, there is no need for installation. 

The price for the license could be more cost-effective. 

Customers have the option of monthly and yearly subscriptions. 

The solution is deployed both on-premises and in the cloud. 

I would recommend the solution to others. 

We deal with around 15 customers. 

I rate Microsoft PowerApps as an eight out of ten. 

Once you have a cloud solution, for instance, and you work within a Microsoft suite, such as Dynamics CRM, ERP, or another dynamic platform and you want to extend it with a mobile app, Microsoft PowerApps is the right solution.

Main limits will be the "vendor lock-in" concept, pricing for mass external users, and the training could be better. It is not intend to serve ex-Azur assets or on-prem. 

The solution integrated well in Azure environment thus provide a full rapid development solution. Thanks to the extensibility (as low code platform should), You can do anything, and if not directly, you can use other Azure functionality. 

1. The licensing lakes a plan for a mass number of external users on the app.

2. The Data layer based on Azure data layer which complicates the environment, the min. required knowledge (citizen developers will not be independent under with PowerApps) and the vendor lock-in limitation.

3. The training is not integrated in the tool and the available training is not a full course which might be available in the online universities but not free and accessible like in other tools. 

It's a stable and trustworthy solution and can serve in an organizational critical processes.

Anything special to share.

Yes I'm using Mendix.

The major advantage of PowerApps is in Microsoft environment.  Once your assets are in Azure, this is the natural choice for rapid development.

As always - depends on the size and complexity of the needed solution. But the cloud based solution + the Low Code approach simplify it. 

I estimate that the time to market will be 3-5 times faster then 3rd generation solution or twice faster that best of breed of the shelf solution (which you have to find the specific specialist +rely on your solution provider ...)

The setup costs depend on the organization (it's professional knowledge) and it's assets location once the basic data and application is in Azure the setup effort will be very cost effective.

For organizational internal users the prices are fair. But for external users It's negotiation. The the long term is vague.