What advice do you have for others considering Microsoft Power Apps?

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.

I rate Microsoft Power Apps a nine out of ten.

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.

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.

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.

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'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 would rate this solution an eight out of ten.

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.

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.

My advice for anyone looking to implement Microsoft Power Apps is: please have a closer look at the Azure infrastructure and do not underestimate the complexity of Azure Active Directory and SharePoint. I recommend spending a week or so letting someone informed like me introduce you to the complexity of Azure Active Directory, SharePoint, and Windows Azure. Not having this information is like driving a car without having put oil into the motor and air into the tires. In other words, it would not be wise.

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.

I recommend this solution because of the type of connectors that they have, the cost is reasonable, and it's easy to learn. I rate this solution seven out of 10.

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.

I’m not sure of the exact version number. However, we are using the latest version. I’d recommend the solution to others. I would rate the solution an eight out of ten. There may be other tools that are easier to work with. However, I’m not sure. In general, it works well, and we have been happy with it.

We are Microsoft partners. I'm using the latest version of the solution. I'd rate the solution eight out of ten. There are some things that need improvement in some ways to make the tool better. However, it's very powerful and it's very fast to deploy something. It's great.

My recommendation is to first investigate OutSystems. I would rate Microsoft PowerApps a seven out of ten.

We use a lot of Microsoft products. We use Microsoft Power BI, Power Platform, and Azure Patch Solutions. I'm not sure which version of the solution we're using. I'd recommend the solution to others. I would rate the solution eight out of ten.

I rate Microsoft PowerApps a nine out of ten.

Building is the simple part of this product, it's the costing that needs to be checked. It can often be overlooked when you build a solution. I rate this solution seven out of 10.

I'm a team lead for the PowerApps platform in general and PowerApps is the product of the platform. I'm not sure which version of the solution we're using. I'd advise others to start with a short hands-on evaluation so that you understand what it looks like when you create on the platform. That will give you a feeling about the components. You get a feeling about what the platform offers and can build slowly up from there. The best way would be perhaps to seek support in the beginning, for example, from partners. If you decide that PowerApps is the way, then consider governance from the beginning on. There's always room for improvement, however, I would rate the solution an eight out of ten.

I'm a customer and an end-user. I would advise other users to try out the product. We've had a largely positive experience. It's good for using for small apps, and automation specifically for Office stuff. If a company needs that kind of specific usability, I'd suggest they use PowerApps.

It all depends on the kind of user you are - PowerApps is a great tool that is built to work as an integrated tool for the Microsoft Enterprise Suite of Products eg: Microsoft Dynamics 365 BC. 

If you are not a Microsoft D365 BC user, the question of how PowerApps fits in remains to be seen.

I would recommend people to pay attention to not only the documentation of the solution but Microsoft provides a lot of video and text documentation. They give step-by-step guides on how to use different features and how to start and complete the implementation. Microsoft documentation is a good way to start for non-familiar people to Microsoft PowerApps. I rate Microsoft PowerApps a ten out of ten.

Deployment has to be supported from the top down because if you're trying to get things supported from the bottom up, you run into a lot of interference. This has not been the easiest. PowerApps is incredible, so I would give it a nine out of 10.

I rate PowerApps four out of 10.

I rate PowerApps eight out of 10.

I'd rate the solution at a nine out of ten. If the external integration process was easier, I would give it a perfect ten.

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.

We are customers and end-users. We are using the cloud version, and therefore we are going with whatever is the latest available functionality. At least for the regular day-to-day work, one can build very useful apps with minimal investment. One can start fast. The only thing is, you need to have people actually experiment on this. Other than that, it's a good platform. Currently, I'd rate the solution at a seven out of ten right now, as there's continuous improvement that's happening and, once that happens, in the future, I will likely be rated even higher.

They think about how they will set it up before beginning to ensure they select suitable use cases. I would rate Microsoft PowerApps a seven out of ten.

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.

I rate this solution at nine on a scale from one to ten.

I am making use of the product in my own company. I would rate it an eight out of ten.

We're just customers and end-users. We are using the latest version of the solution. From a perspective of me doing a full test of the application and how I want it to run, it just met all of my needs and there are other storage locations for data. That said, the data is sitting in the CDS. From my perspective, it was a great place to start and a great place to sit and test the waters. I'm looking to migrate it into something else in a little while. I won't stay with it forever. That's not the plan. I'd rate the solution at a seven out of ten.

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.

I would recommend this solution. Microsoft is a large company and the product has good features. We plan to migrate all our tools to Microsoft in the future. I rate this solution an eight out of 10.

I would recommend this solution for people who are looking for flexibility. PowerApps offers more flexibility than SalesForce. I would advise others to use a local platform to build and test first and fail fast. We are still exploring a few features, but based on what I have learned and seen, I would rate PowerApps an eight out of ten.

I am using the latest version of the solution. I'm unsure of the exact version number. I'd recommend the solution to other organizations. In general, I would rate the solution at a seven out of ten. We've mostly been satisfied with the product, however, it is still immature and needs time for tweaks and advancements.

Overall, on a scale from one to ten, I would give this solution a rating of eight.

We have just started using the product, it is unclear if we will continue to use it after taking into account the unclear pricing structure. I rate Microsoft PowerApps a seven out of ten.

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.

I would recommend this solution. I would rate Microsoft PowerApps an eight out of ten.

This is a good product and I recommend it. To this point, we have been working on pretty simple apps, and it has done everything that I needed it to do. I have not tried making a complex app, although that will come in the next few months. I would rate this solution an eight out of ten.

We have a very good and very close relationship with Microsoft. I started working more on PowerApps as we were making a comparison with Salesforce. We decided on PowerApps mostly due to the fact that Salesforce would not work. We have to maintain our current environment, so at some point, it's not that we are 100% in these new tools. Right now we have more than 60% of our time in these new tools and try to not develop any coding. We do make some code in JavaScript, however, it isn't too much. It's a good solution. There is some coding needed for customization aspects, however, it's a pretty solid product. There's still a lot that I need to learn about the solution. Therefore, currently, I'd rate it at a seven out of ten. We're not in production yet, and therefore it's hard to gauge many aspects of the solution.

I would advise others to make an informed decision before you implement it. There are a lot of challenges, and the product is going through a lot of changes. It's promising, so I would rate this solution a seven out of ten.

My advice for anybody who is implementing this solution is to research the material that is available in the documentation, as well as videos on YouTube. These sources contain a lot of information and recommendations for how to implement and use the platform. They also have a really good community with Microsoft the websites, where many people post their issues and the solutions as well. Overall, this is a really good product. I would rate this solution a ten out of ten.

I would recommend this solution because it is an easy solution for the Microsoft ecosystem. I would rate Microsoft PowerApps an eight out of ten. We are happy with this solution.

I'm not sure which version of the solution we're using.

It is definitely a useful product. I would absolutely recommend it. I would rate Microsoft PowerApps an eight out of ten because there are still some issues that we are addressing, specifically related to its integration.

I started working with the common data model and the entities and working with my data warehouse. Now I'm working on my data warehouse with common data series. I use Power Apps for my standard entities' values. I need to modify it now with the new processes that are in place. And in the beginning, I use Power Apps for the management of the entities for Power VA. Since I've started using Power Apps, as I can see it's powerful and makes it easy for many, many, many kinds of work processes. I'm still trying the solution out, and I'm still learning a lot about it. I'm by no means an expert yet. I'm pretty satisfied with the product. Overall, I would rate it eight out of ten. It's a good tool and it's nice that it's part of a suite in Microsoft.

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.

On a scale from one to ten, I would give this solution a rating of nine.

We're just a customer. We don't have a business relationship with Microsoft. We are most likely using the most recent or updated version of the solution, however, I'm unsure of the exact version number. While Microsoft is an option, I'd recommend users check out OutSystems first and see if it makes sense for them to use that before looking into Microsoft. Overall, I'd rate the solution six out of ten.

It's very easy to use this solution, you can do integration, there's no need to write much code. I would suggest that Power Apps is for all ERP people. If you want to connect to SPL on-premises, it requires one gateway. That's the bridge between Power Apps and the on-premises SPL. The Power Apps tool is relatively new technology. Not many people are using it yet so whatever problems they are facing, they will be posting to WordPress or something similar. If I need an answer I can go there. I would rate this solution a nine out of 10.

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.

At this time, we are still learning the basics and the setups while discovering the entire product and how to best use it internally. I would suggest investing in the training of the product. It is very important to know the capabilities of the product to be able to address any questions a customer or user may have for you. I would rate this solution a seven out of ten.

We use the cloud deployment model. I'm a consultant; I work mainly with other companies. Already with what exists, the solution is quite good and we can do quite a lot. I don't think too much can be improved. I'd advise others to make sure they have good parameters and documentation before they get started. It's a good idea to follow the tutorial at the beginning. There are a lot of things about the solution that are good to understand beforehand, including how the different components work. I'd rate the solution ten out of ten. For me, it has worked very well.

Previously, we had a whole department using the product. When I lived in Australia, it was used for assembling websites and to upload photos, videos and the like. It worked well because it was for internally-based users. My suggestion to anyone searching for a product would be to invest in a solution if you know that it works. Don't go for anything high-risk. This product works as it's intended. It's missing a few key features to make it really stand out but I believe it has the potential to be the best app for access to the database. The product can be easily integrated - with Microsoft Graph, with common data links, and Power BI especially. You can have a dashboard ready, all the information you want, displayed in whatever form you want. It can present your data in whatever way, shape, and form you want it to. I would rate this product a seven out of 10.

My advice would be to create a master screen for items like layouts and all of the typography that you may have in your application. Create a master screen widget. The rest of the screen will have, for example, settings for the layout that will refer to these objects in the master screen settings. Mainly for editing. I would rate this solution an eight out of ten.