Mendix

My main use case for Mendix  is software development, specifically for both mobile and web applications.

Currently, I'm working on an electricity application with Mendix  where the customer can raise a bill so we can provide them with the service. I've worked on many business projects, including gift and hospitality, but I cannot expose the titles here because they're client projects.

In addition to that, I have many more use cases with Mendix. Currently, I'm working on mobile applications where I've integrated many widgets including external plugins and Google Maps, incorporating React Native  maps and these kinds of features.

When I mention scalability and the ability to implement new ideas quickly, I can explain that my use case is to implement an attendance system. However, when the client presented a different requirement, I was able to capture latitude, longitude, and many more use cases with ease, showcasing the vast opportunities Mendix provides for integration.

In my experience, the best features Mendix offers include productivity and scalability. We can do anything in Mendix; it's a huge opening where you can realize every idea.

From my perspective, the most valuable feature is pluggable widgets in Mendix. We can develop any React code and seamlessly integrate it with Mendix. This is something I wrote a blog about; it's the best feature I find in the platform.

Mendix has positively impacted my organization as it is fully Mendix-based. My organization primarily converts clients to build Mendix applications, and Mendix applications open many opportunities for developers, leading us to hire numerous Mendix developers to develop with the platform.

I can share that we've noticed significant outcomes due to Mendix in my organization. For a legacy application that typically takes a year, we can now complete it in just one or two months. It's a very quick output project. Moreover, for legacy applications, where we would normally need five to six developers, we find that with just two developers, we can handle everything within two months.

Mendix is already improved with every feature, including AI integrations, available. So I think there are no improvements needed for now.

Even though Mendix is great, I think something could be better regarding the extensions. Many people don't realize the potential of extensions, and if many more extensions are available in the marketplace, it will be quite helpful.

Mendix is indeed very stable. We can choose the Long-Term Support (LTS) options that provide a wide range of supported features.

Regarding scalability, we can certainly scale with Mendix. We can add many more attributes in the entity, and we can do anything we want.

Generally, the customer support takes around two weeks to respond to support tickets, but everything gets resolved. It's a better experience compared to other common platforms.

I would rate the customer support an eight out of ten due to the two weeks' response time.

Before using Mendix, I actually worked on React, which I love, but I found it time-consuming compared to Mendix, where the same feature can be implemented very quickly.

I have definitely seen a return on investment with Mendix. We usually agree on a project with fewer resources in terms of time and personnel, and mostly everything is profitable.

I did not evaluate other options before choosing Mendix, as I am a MERN stack developer who directly switched to Mendix without considering any alternatives.

My advice for others looking into using Mendix is that every new developer coming to Mendix learns it quickly and shows a lot of interest, so it is a great option for others to consider using it. I would rate this product a ten out of ten.

Our organization currently serves multiple pharmaceutical clients, and we design scalable and efficient end-to-end products and services based on web applications using Mendix , a low-code platform tool.

We have created multiple web applications for our pharmaceutical clients, including applications that help patients submit enrollment forms to enter their information and prescription details for ordering glucose monitoring devices or checking their insurance eligibility. We have also built different portals for tender solutions and systems for checking benefits verifications via web applications, including a channel management system and a revenue management system, among others.

Mendix  is quite comfortable for the team to use, particularly for developers who have worked with low-code platform tools in their past experiences, as it enables integration with many components, including external and internal APIs, PDF generation, Twilio  component, and AWS  integration. This is one of the key selling points for Mendix, and if developers are seasoned in CSS and UI, they can create a lucrative and user-friendly interface.

The best features Mendix offers in my experience include its readiness to go to market, which reduces the effort and time consumed in developing an application end-to-end. If you have hands-on developers, you can easily have your application ready for business and end users within weeks or months, instead of the typical five to six months that other applications usually take.

In every area of technology, there is always room for improvement, and Mendix is no exception. I would highlight some areas for potential improvement, such as the ability to integrate more easily with external databases, which takes a considerable amount of time in Mendix compared to my past experiences. Integration with external databases can be slow, and it burdens queries when trying to pull large datasets, thus slowing down page execution.

Additionally, there are issues with constant values during deployments, where Mendix overwrites values without prior notification, which could result in unwanted changes if post-deployment activities are not monitored. The user interface documentation is clear and easy to understand if developers are skilled enough to handle CSS and configuration, but there are definitely a few enhancements that could be made, such as directly importing CSS files or improving the integration of tools like Cognito forms. The areas I have mentioned regarding external database integration, constant values during deployment, and some aspects of CSS and UI, as well as internal coding, cover my main concerns regarding where Mendix could be improved.

I have eight plus years of experience, and I am currently associated with more than six years at Eversana.

Before Mendix, we were using another low-code platform tool, and our organization decided to shift to Mendix. During this transition, our capable developers were able to adapt to Mendix easily, and we successfully delivered all of our projects within the defined timeframe, which made clients and stakeholders happy with the timeline and efficiency we achieved during this shift.

For any organization looking to adopt Mendix, I would advise ensuring that their developers are skilled with low-code platform tools, as Mendix is a great platform that allows for the easy creation of high-quality, scalable, reliable, and durable web and mobile applications. It is essential to face challenges in adopting new technologies and conduct out-of-the-box research and development. Mendix is one of the platforms that the industry currently looks to for improvement and efficiency for end users and clients in the future. I would rate this product an eight overall.