I think it's well suited if you have data available and you want to create customized solutions for different types of users. Mendix is very good at doing that. It allows you to do it very easily. So those are good use cases.
Feature Flags are well suited for apps which are being developed across numerous teams in order to extend and basically enable/disable whatever areas of the app you want. It's not really necessary for an individual developer or perhaps even a single team of developers, depending.
Drawing from my hands-on experience with Mendix, I can confidently state that the platform aptly fulfills our needs for web application development. Mendix stands out by providing a marketplace replete with pre-built templates and widgets. This feature empowers users to leverage readily available components, hastening the development process and contributing to an enhanced overall usability of the platform.
I think their support system is really professional. They answer question quickly and accurately. They have a ticket system that allows to track the current status of a request. The only point for imporvement is a way for me to postpone an answer. Tickets get closed automatically after some time. I feel that the user should have the option to change to an on hold status, allowing for more time to respond to a ticket.
Because most of our apps work closely with our main system (ERP) and other tools, we went with Mendix. It's good at easily connecting with lots of different systems, which is exactly what we need. Another thing we like about it is that it can handle growth well, and its pricing is straightforward and easy to understand.
We still utilize Git as our source control system but Feature Flags allow us to use Git in a less complex and more efficient way for our development needs.
Without Mendix we could not have been where we are now. A development platform as Mendix can make the difference in a constantly changing environment.
Upgrading to newer versions of Mendix is a breeze when you stay within a main version (e.g. M6.x to Mx6.x+1) and even between versions (Mx5 to Mx6) most of the time it is no problem at all and there are only minor changes needed to upgrade.
Learning Mendix is simple. Just start playing with it and see for yourself how easy it is and feel the joy of developing applications.
I would say a large ROI considering the reduction in branching and merging we need to perform and also the ability to use common, up to date code across teams. There's a lot of shared code we make use of, particularly with identity and authentication and our entire identity platform which is essentially used by each feature.
