My main use case for Mendix is to create smart applications in a fast way, applications that have integrations, use of AI, custom widgets, and so on. A quick, specific example of an application I've built with Mendix is an application with video calls, which stands out for me, and it's an application that I am really proud about. In this application, we have like two people talking in a video call and then the agent on the other side can take pictures from the user's phone, because the user's used his or her phone to join the call via a Mendix application, and then they talk to each other with a video call, pictures, drawing pictures, that kind of stuff.
Mendix
Siemens Digital Industries SoftwareExternal reviews
External reviews are not included in the AWS star rating for the product.
Has delivered fast app creation with AI and reduced field engineer visits through smart video solutions
What is our primary use case?
What is most valuable?
The best features Mendix offers are easy deployment, fast application creation, easy to build logic, and lots of marketplace modules and components to use in your applications, so you don't have to reinvent the wheel. If you need to eventually customize code, you can do it by using JavaScript and Java, which just make things faster.
Mendix has positively impacted my organization, especially for clients, who are getting lots of benefits, particularly speeding up changes, because they eventually need to change business rules, or they need to change how their business works. Mendix makes sure that happens fast, and about the video call application I created, they now speed up their customer service by having that video call feature, meaning they don't really need to send engineers physically to the client's location to see what's going on. All they need to do is do a video call, take a few pictures remotely, and that's it. No need to drive, no need to spend fuel, money with the engineers' location relocation; saving money is the most valuable thing.
After implementing Mendix, they reduced by 98% the engineers' relocation, as 98% of the cases are now being done by video calls instead of in-person appointments, which says a lot, even though the company didn't provide any numbers on how much is saved.
What needs improvement?
It would be great for AI in Mendix to read my whole project and understand the whole business, so all I need to do is ask, hey, what does this button do, and why is that button there? AI could answer me why we have that button, and what that button does. I know that this is something in progress by Mendix; eventually, we will get that feature, but this is something that we definitely need because new developers that join a project might struggle to understand the whole business, especially in complex applications. I chose eight instead of a higher or lower number because Mendix would be a 10 if we have the feature that I just mentioned, like asking why that button is there and getting a clear answer about its business purpose. It would also be a 10 if we have a faster Studio Pro, like not taking too much time to process things, especially when projects are too large; those two aspects would make it a 10 for me.
For how long have I used the solution?
I have been using Mendix for the last eight years.
What do I think about the stability of the solution?
Mendix is stable.
What do I think about the scalability of the solution?
You can scale Mendix using a private cloud, but if you want to scale it to a bigger instance, you have to contact a Mendix partner or the same Mendix partner that sold you the license.
How are customer service and support?
Customer support for Mendix is very good; we open a ticket, and they answer, of course depending on your plan, but it's very useful. I would rate customer support a nine.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
Before Mendix, I used to be a high-code developer, so I didn't really use a platform or solution; I coded with React, Node.js, MongoDB, which aren't actually platforms but open-source solutions.
How was the initial setup?
In the project that I'm working with, we are using the Mendix Cloud and with just a few clicks, we can deploy the application acceptance or production, which has made my work easier and more efficient because I don't really need to understand how DevOps works. I don't need to understand Kubernetes or Docker. All I need to do is to build my app and deploy it by just doing a few clicks. About the speed of development of app creation, I think it's just a matter of open Studio Pro, create the app, do all the pages logic we need, and then push to the point. So that's pretty much it.
What about the implementation team?
My company has a business relationship with Mendix as a partner, specifically an official partner.
What's my experience with pricing, setup cost, and licensing?
Not much about pricing, as it's something that you have to reach a Mendix vendor to see what the possibilities are. From the pricing shown on the Mendix webpage, we have a basic package where you pay 60 Euros a month for five users and 10 Euros per additional user. This is all I know about pricing, but for a different size of Mendix Cloud, you have to consult an official Mendix vendor or partner.
Which other solutions did I evaluate?
I evaluated OutSystems before choosing Mendix.
What other advice do I have?
Right now, I'm working with AI, which is pretty new to me, but I'm learning a lot and Mendix makes sure we can use AI in a very smart and fast way by using the platform. My advice for others looking into using Mendix is to start with the basics; don't get rushed. Things will come up eventually and always ask for help. There are forums and lots of communities; you're not alone. It's a great platform to learn a lot and make a lot of money with it, so keep it going. The review rating for Mendix is 8.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Offers comprehensive integration options and support resources, allowing projects to be easily managed and scaled
What is our primary use case?
What is most valuable?
What needs improvement?
For how long have I used the solution?
What was my experience with deployment of the solution?
What do I think about the stability of the solution?
What do I think about the scalability of the solution?
How are customer service and support?
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
How was the initial setup?
What's my experience with pricing, setup cost, and licensing?
Which other solutions did I evaluate?
What other advice do I have?
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Cloud-based, helps fill gaps and that seamlessly integrates with existing systems
What is our primary use case?
I am applying the application to digitalize the Orbiq process and have created a customer-focused program to keep customers close. Additionally, I have an application that enables me to create quotations for my customers and their clients. I maintain and continue to develop these applications.
How has it helped my organization?
Mendix gives me the opportunity to build a solution that is more attractive to my end users, allowing me to create my own specific software. I use an ERP program called EnterpriseOne from Oracle, but ERP software options can be rigid and not practical for end users. Mendix fills the gaps where other software falls short.
What is most valuable?
Mendix provides the ability to create solutions that fill gaps that I would otherwise be unable to address with standard software. It integrates seamlessly with my existing ERP systems, enabling me to build attractive and user-specific solutions. Its cloud-based platform supports agile methods and enhances my development speed. These features enable me to better meet my organizational needs.
What needs improvement?
All software applications have their hiccups, including the Mendix Studio Pro developers program. Though still improving, there is no specific example of what really needs to be improved. Some learning paths need improvement, but most are satisfactory. It is not one hundred percent stable.
For how long have I used the solution?
I have been using Mendix since June last year, so that's about one year and a half.
What do I think about the stability of the solution?
The product is generally stable, however, is not 100% stable.
What do I think about the scalability of the solution?
Mendix supports scaling well with its comprehensive online documentation and learning paths. Consultancies can assist with scaling from small teams to enterprise levels.
How are customer service and support?
I find support accessible. I haven't often needed to seek direct support from Mendix teams as their online resources and knowledge database are comprehensive. I rate their technical support between eight or nine out of ten.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
I previously worked with IBM Notes. However, since IBM Notes is no longer on IBM and will likely disappear, I have found Mendix to be better for the long term.
What about the implementation team?
You definitely need professional people to do the development in Mendix, especially if you're a small company.
What other advice do I have?
I would recommend Mendix to others, particularly medium to large-sized companies. For a small company, it might be better to hire consultancy companies.
I'd rate the solution eight out of ten.
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Provides an integrated approach to monolithic and microservices
What is our primary use case?
We built a SaaS product for our own customers and are developing internal applications for most of the MDM using Mendix. Additionally, we handle small to medium-complexity workflow management systems, whether process-related or complete system automation, using Mendix Workflow.
Some customers prefer building their products rather than buying them. For instance, they wanted a simplified version instead of purchasing a product management system, so we developed it. We built a couple of external-facing, consumer-facing applications, although the consumer base for these is small.
What is most valuable?
When I often want to pitch Mendix, if there is something out of the box that is not available, I can always extend Mendix. Whether it's the front end or the back end, It can be extended with Java. I've also built many widgets using Mendix.
What needs improvement?
We are all moving away from a monolithic product model to microservices. We are building an F2DUI application to decouple the front and back end. Mendix provides an integrated approach for both. Ideally, we should have a way to separate the front end and back end to scale them independently.
While Mendix does offer different ways to achieve this, I sometimes prefer having the front end separate. I don't want the back end to be tightly coupled with the front end all the time.
For how long have I used the solution?
I have been using Mendix for five years.
What do I think about the stability of the solution?
Mendix is quite stable. However, some customers do not always use the stable versions provided by Mendix, which include both LTS and MTS versions. If a customer chooses a version other than these two options, it may lead to stability issues. Therefore, we always recommend that customers choose the appropriate development version to ensure their applications' stability. Mendix offers stable versions, but customers must be educated about using them correctly.
What do I think about the scalability of the solution?
The scalability has an issue. When you buy a license for a private cloud, you can scale as much as you can afford in your private cloud. However, buying a public cloud with a t-shirt sizing model has limitations. You are limited to the one instance you can get whenever you want to upgrade. There is always a limit to whether they provide 30 gigabytes or 128 gigabytes of RAM. For the public cloud, its scalability is limited, so I'm rating it seven. The rating is nine for a private cloud or on-premise because you can scale however you want.
Most of the time, it is for enterprise customers because of the licensing and the user-based cost.
How are customer service and support?
Since we are an official partner of Mendix, we receive priority on requests. Based on my interactions, responses are generally quicker, but the quality of resolution varies. There are two levels of resolution: one is through the documentation and technical support they provide, and the other involves their expert services, which may incur charges. While technical difficulties can be resolved with their assistance, charges may apply. It's important to note that Mendix does offer expert services that can help solve any problem.
How was the initial setup?
The initial setup is easy. You can get started right away.
What other advice do I have?
Integrating with Mendix is generally easy. It is integrated with most modern frameworks, such as REST and Kafka. We've even integrated it with external workflow orchestration tools like JPM or Camunda. However, I have encountered some issues with Mendix regarding SDK-based integrations. While it is possible to perform these integrations, there is no direct way to do it, making the process more complex. For example, if Salesforce provides an SDK instead of a REST API, integrating with the SDK is more complicated than a straightforward REST API integration.
I would not recommend Mendix because it is very expensive for external users and can also be expensive for internal users. If your internal workforce is less than 10,000, I recommend Mendix because you can achieve a faster ROI. However, if you have an internal customer base of 30,000- 40,000, I would not recommend Mendix.
In version 10.12, released a week ago, Mendix introduced some new features I had requested multiple times. They now have an in-app help feature within the Mendix IDE to speed development. Specifically, they have enabled a chatbot within the Mendix IDE, which helps streamline development.
Additionally, Mendix should support modularity in each functionality. For example, the workflow engine should operate separately from the main application, allowing for independent deployment. This means I should be able to deploy the workflow engine, microservices, or UI components separately. If Mendix provides this option, it will be a game changer. This way, I can scale the workflow for workflow-intensive applications, scale the backend for high-throughput scenarios, and scale the content to accommodate many visitors.
Overall, I rate the solution a nine out of ten.
Which deployment model are you using for this solution?
Simple initial setup and good development tools for building new apps, both mobile and enterprise web
What is our primary use case?
We have clients in petrochemicals, agriculture, financial services, retail, and all sorts of other areas. It is amazing when we use it for what it is designed for.
What is most valuable?
The development tools are excellent for building new apps, both mobile and enterprise web.
We also use Mendix Enterprise Integration for complex business logic. It's a low-code platform, so we run Mendix in the Mendix Cloud.
What needs improvement?
The code refactoring tools could be better, especially for applications running for years. It's not bad, but it could be smoother.
Also, writing new widgets can be trickier than it should be for some people, but not if you're familiar with Mendix.
Pricing used to be complex, but Mendix has improved that quite a bit. So, the pricing policy in general. It's not exactly straightforward.
The reporting feature also wasn't great, but Mendix has fixed that in version 10. I still need to test it fully, though. Version 9's reporting could be better.
In future releases, I would like to see more features around report writing.
Another thing is managing and breaking down monolithic apps into modules, with version control for individual modules, which could be more robust. Sharing individual modules wasn't as strong as it should be.
However, the biggest improvement still would be better refactoring tools, both for code and models.
For how long have I used the solution?
I have been using it since 2011.
What do I think about the stability of the solution?
I would rate the stability a ten out of ten. We've been running large applications on it, and almost never have any issues.
What do I think about the scalability of the solution?
Mendix is easy to scale for typical business applications. It's horizontally and vertically scalable.
It used to be mainly for medium and large companies, but the new pricing makes it much more accessible. Now, it's suitable for the whole spectrum, from small to large.
How are customer service and support?
The customer service and support are not bad. There is definitely room for improvement in response time. And they tend to escalate things quite a bit before acknowledging a problem. So, our experience has been a bit slow but not terrible.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
Mendix competes with Outsystems, Microsoft Power Apps, Salesforce, and a few local players.
I'd definitely rate Mendix as the number one low-code, model-driven platform. It's much better than the competition regarding ease of use, pricing, stability, IDE strength, good training materials, and easy staff onboarding and certification. It has made major improvements in those areas.
How was the initial setup?
The initial setup is very simple. It was super quick.
It supports all deployment models. You can run it in the Mendix cloud with a single button deploy, on your own cloud, or integrate it into your DevOps environment for scripted rollouts.
It's very flexible, and Mendix has really improved the deployment aspect. So, clients have complete control over deployment.
What's my experience with pricing, setup cost, and licensing?
The pricing is fairly comparable. I would rate the pricing a six out of ten, where one is high price, and ten is low price.
Which other solutions did I evaluate?
What other advice do I have?
Overall, I would rate the solution a nine out of ten. There is room for improvement.