PowerApps is much harder to learn. It lacks the robustness of Mendix; if a detail is lacking in PowerApps the app won't run and it takes much time to debug. Mendix is build to work for Scrum teams. I think Microsoft could learn a lot from the way working on one app by diverse …
Mendix excels in scenarios involving Business Process Automation, making it a strong choice for applications requiring workflow automation, including processes like request approvals, document management, and other business workflows.Conversely, Mendix may be less suitable for projects that demand highly customized solutions with extensive custom coding. Its primary focus on low-code development may not align well with the requirements of projects that heavily rely on intricate and specialized coding.
Power Apps is ideal for scenarios that are neither too complex nor too large. It is easy to begin development in Power Apps, as it is one of the best tools for low-code development. Power Apps can be implemented for complex scenarios as well, provided there is strong knowledge of the tool and ample time for planning. Our applications benefit from Power Apps' cross-platform support, making it easy to use on any device, including desktops, laptops, and mobile devices.
We're able to really easily develop different views that are very specific to a customer's needs or customer's different types of user needs. So for example, the production managers can have a certain view that's relevant to them and then certain line managers can have views that are specific to them that allow them to run different scenarios which they define. So it allows us to easily build customized apps for each different type of user.
Power Apps has formats that are pre-built that don't require any coding which makes it easier to achieve your vision. This does become a challenge if your App needs don't fit into that format.
We deal with a ton of data so the fact that you can connect to any data source in addition to their pre-stablished data connections makes the process a breeze.
The online learning resources and tutorials are helpful as well for those who are tech savvy.
Sometimes the cost of solutions is greater than the benefit. Licensing is expensive relative to the scope of some business user-created personal or team-level solutions.
While there is a starter-kit for Governance, it is complicated to stand up and requires dedicated resources to provide on-going governance operations. Many organizations are not going to be able to dedicate resources to governance and this causes the sprawl, solution duplication, silos, unneeded and unplanned licensing expenses, and a general "wild wild west" environment.
There needs to be better direction and best practices given around Power Platform Environment utilization and optimization.
The accessibility to the platform and ease for business partners to independantly create solutions is both a benefit and a negative. When the business outcome needed is a good fit for PowerApps it is a quick win, but when not a good fit it becomes a frustration for the business partner attempting to make the platform do something it is not well-suited for. The business partner entangles tech teams in the effort which drains resources and provides a lack-luster solution. All of this to say, it would be beneficial to have some tools that business partners could leverage to determine\understand if the type of business outcome they need is well suited to PowerApps or not.
A 10 would say I have nothing to wish for. A 9 means I haven't seen anything better.This tool really helps you in the whole creation and maintenace cycle, so from requirements to building/modeling to testing to deploying to capturing feedback.
PowerApps is a great solution and I have spent the last year familiarizing myself with the platform and building custom applications to complete a whole range of tasks such as asset management, custom invoice generation, and item restriction tracking. We as a company have barely begun to scratch the surface of what can be achieved with PowerApps.
Response times are quick and you will get updates regularly about the status of your request. Even with very technical questions they have specialists that can help you with your problems it will give you an answer or help you with a work around.
The community forums are extremely responsive to questions asked, there is a good body of online documentation and many community posts to draw from. Although the platform has changed, which means some of the posts are out of date and the solutions provided aren't relevant. Of relevance, I read over 400 articles plus documentation to get this first app built in SharePoint, move it to SQL and make it work exactly the way it should.
Mendix would be my preferred system all the way. The system is designed for these kinds of works. I've worked with WP and DNN but they should be used just for websites. To create an app for a business value, I would suggest Mendix. Also, the offline capabilities of Mendix have greatly improved since the deployment of Mendix 7.13.
1. PowerApps functionality comes with E1 over E3 License without adding extra costs 2. For Nintex you pay (at the beginning) for each workflow, so my intention would be, to do no workflows to prevent additional costs, but I want a platform with a fair price that allows me to create workflows without thinking about the price for each workflow and we use only some workflow and relative easy workflows and forms as a medium-sized company. 3. PowerApps provides a lot of functionality without needing to invest in premium features directly.
It helps to speed up application development because of its low code by the fact that it's low code. It allows professional developers to focus more on specialized application development rather than the more routine application development that business IT and super users can do for themselves with some coaching from the IT department. So it's just allowing the more specialist professional developers.net, for example, Java in our organization to focus on more complex engineering application developments.
