If you were talking to someone whose organization is considering Microsoft PowerApps, what would you say?
How would you rate it and why? Any other tips or advice?
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.