Mendix Reviews

I built prototypes with it.

We did not really deploy anything for real clients. We only build prototypes in our local environment, and so far, we do not have any engagements with this platform. It was only for proof of concept projects, and we are still trying to gather engagements to work on if there are existing clients that would provide us with something to use.

The ability to model data and relationships between entities is easy, and the ability to write microflows and nanoflows is great. By that, I mean flows, in general, that achieve something which will function. Those are things I really like. On top of that, they are fast to learn and put into practice after a bit of experience. 

Overall the platform is really good. I like it. I wish I was better at it, as there are plenty of things to learn, especially on the front-end side. I like the fact that you can integrate react widgets. It's really cool. The integration is really good.

The debugger is perfect. It's the best I've ever seen. 

Technical support is great.

You can scale the solution.

It's easy to maintain. 

In the beginning, it is difficult to learn and work with. I have to say it was difficult in the beginning to understand best practices.

Once I got the best practices for the back end part, for manipulating data, it was easier to use. For the front end, it was a bit more difficult. For the front end part, I don't like that it's not fully drag and drop there, and I have to know a bit of CSS, which I don't really know.

It would be cool if it could be completely drag and drop, and you could do it like other products, like PowerApps. With PowerApps, you can move it pixel by pixel. It's like PowerPoint.

I've experienced a few bugs. Sometimes it was really tiny things - not something big. There are issues with the versioning systems, et cetera.

It had errors deploying in the public cloud to publish a solution just for the sake of testing it. 

I had an issue with a message definition. When you create a message definition and save it, and then close the project and open it again, the message definition did not save. I had to do it again. This has happened a lot.

I've used the solution for one year. I used it until last week. 

The solution is stable. 

If you establish best practices at the beginning, it's good. There were some bugs here and there I had to deal with. However, they were small. 

It's a scalable product.

I didn't really build something big by myself on it. I've seen with some applications if you respect good practices, if you don't overwhelm, if you put 100 entities in a module or something, and if you separate things properly, you can scale.

Technical support is great. They are very helpful and responsive. 

Positive

I did previously use the Microsoft Power Apps Platform. That's more like a system of services. It's not an on-in-one product.

The initial setup is more complex. I've also noticed that people that have a first-time interaction with it find it more difficult to grasp. It is very difficult to do in the beginning. You need three to six months to start building something which is not breaking.

Of course, that's way better than trying to program, since that's even more difficult.

My previous experience with some automotive company. They had real-world projects that they were using, and they were deploying to the cloud. I don't know exactly how long it took to set up for them. I remember that the deployment was really fast, like a few minutes. They had a medium type of setup. 

Maintenance and bug fixing is really easy. One person can handle it.

I am able to deploy the solution myself. I did not use any consultants or integrators. 

I'm not in charge of licensing costs. 

That said, my understanding is the product is very expensive, and Microsoft's offering is much cheaper. 

We build solutions and sell them to clients. We are intermediaries. We use this tool to deliver products. 

I only use it for web applications and very rarely for the hybrid web. I never use it for the hybrid web. Mostly, I use it only on desktop web.

I would recommend this solution and encourage people to learn it. 

I'd rate the solution nine out of ten. It's very top-notch as a product. It's one of the best.

I used the solution to develop an application for a parking system. It manages everything from parking cards, payments, eGates, tickets, and more.

The most valuable features of the product are its ease of use and speed. My friend and I find it helpful as a team of just two developers.

One area for improvement is its integration capabilities. Creating a pluggable widget or integrating it with other systems is challenging.

In terms of features, it would be great to see advancements such as AI services and the integration of third-party services. Additionally, connecting external devices to the application requires multiple steps. Improving this will make it easier for the developers.

I have been using the solution for the past three years.

The product is stable and powerful.

The tool is scalable. We had a single application in development, and there were two developers with 15 end users.

Six or seven months ago, I interacted with the technical support team, but since then, they haven't reached out to me. I tried to get in touch with them by asking some questions, and they mentioned that someone would contact me, but unfortunately, no one has reached out yet.

I run my businesses and develop applications. My friends and I are a small group of developers. In the past, we worked with technologies like C# and React. However, we are now looking to take the next step using local platforms.

I switched to this solution because of its database handling. You can create and draw your structure. The UI has powerful microflow, workflow, and nanoflow capabilities. It has great speed. It is suitable for developers with varying levels of experience. You can achieve tasks with minimal coding. The CSS and paging capabilities are great.

The initial setup is not complex. The deployment process took two to three weeks.

I set up the solution on my own.

I would not recommend the solution to small and medium-sized businesses because it’s expensive. It’s great for big organizations. I rate the pricing as a three out of ten.

We have used React.js, JavaScript, C#, and Oracle Siebel. However, we strive to move to the next level for future projects.

Overall, I rate Mendix a six out of ten.

The one big use case for one of the clients was to do a legacy organization. If they were on Java, we were trying to move to Mendix.

Use cases for PO approval, invoice approval, creating a better user experience for the user, or digital decoupling would be covered. Where you try to keep your core systems like SAP or PDM, PLM system as the core, you don't want to bring too much change in those for the use cases. 

The user experience is great. Creating the user experience is fast and the development speed is excellent.

I struggle with solutions like Mendix in terms of creating enterprise solutions. When I say enterprise solutions I mean enterprise-grade solutions. Let's say if I create an application on Mendix and I want to roll it out to multiple countries, that kind of thing I can do with Mendix. I'll have to copy it. That's hard to do at an enterprise level which can be quite sizeable. I'm not sure how well it scales. 

The setup itself can be complex and difficult. 

The UX capacity is lacking.

I'm not sure how well the workflow capabilities will hold up. 

I've used the solution for probably about a year. 

I have not had that kind of experience where I can make a statement on the stability of the platform. I don't know whether it is stable or not, as I did not work very deep on the platform in a live setting.

Looking at the architecture, scalability is going to be a challenge. I was part of the program, which I could not finish as I left the company. Yeah. Scalability-wise, I do see the technical approach that platform offers. Scalability will always be a question mark for me. I don't have data to prove whether it is not scalable. However, I am aware that it will be a challenge to scale. 

There are two types of scalability we're talking about. One is putting more and more and more and more processes on top of Mendix. That should not be a challenge. However, taking one process, taking one application, and scaling it to multiple countries, is where I see this platform struggling. However, with the cloud version, scaling may be simpler. 

I have no experience with the technical support I cannot speak to how helpful they would be. 

My portfolio had Mendix, OutSystems, Pega, Appian, Bizagi, and on the RPA side, UiPath, Blue Prism, and Automation Anywhere, and all the cognitive technologies like AI and ML. My responsibility was to create solutions and take them to the client. And then, the team will take care of technical design and implementation.

The solution can be complex to set up. Design-wise, I wouldn't say it is hard. However, you do have a lot of work to do. When you create a solution that needs to be rolled out to many countries, it gets complex. 

I have no visibility in terms of the cost of the solution. 

We are at the initial stages of setting up a partnership with Mendix. 

I was not involved in the technical part. I was leading as a principal architect. My responsibility was to come up with a strategic technical design, and we handed it over to the team, depending on which platform a customer would take. 

I'd advise potential new users to look at the UX capability. They promise too much. Therefore, be careful with the UX capability, as generally, all these platforms struggle in that area. Look at what they offer and what you need. 

Be careful with the workflow capability, as it's new, so it will have its own challenges, and look out for the scalability of the platform.

I'd rate the solution seven out of ten.

We are using Mendix as a low code or no code solution for creating POC origins for clients.

The most valuable features of Mendix are the drag and drop functions, the data entities, domain models, and all the related features.

Mendix could improve by allowing the customization of different programming languages, such as Python and C++.

In a feature release of Mendix, they should add 3D augmentations or other 3D visualizations, such as images. Additionally, more customizations would be a benefit.

I have been using Mendix for a couple of years.

Mendix is stable and is very good. I have used multiple no code/no code platforms and Mendix is one of the best platforms I have used.

The scalability of Mendix is good. However, whenever we deploy the application, it's heavily weighted on the server. It is not a light solution.

We have approximately 100 people using this solution in my organization.

I have not used the support from Mendix.

The initial setup of Mendix is straightforward.

There is a license required to use Mendix. The solution's price is high, but it is best suited for enterprise companies that have the budget. It is not for small or medium-sized businesses.

There are not any hidden fees but there is a cost for every user that uses the solution. The pricing model can be confusing whether it is user or application based.

Mendix provides an academic course, which is free and I would advise people to take the course. If they take it, then it will be easy for new users to run through the Mendix development.

I rate Mendix an eight out of ten.

I did the certification in Mendix and it was nice and easy to learn first.  Everybody can learn it easily with available resources. Everything is documented properly, from version to version, and is easy to learn. My area of expertise is with enterprise and I sell to clients which are enterprise companies.  

I recommend this solution to others.

I'm using the solution for assignments with my students. I give little projects to my students and I want them to use the free version of Mendix to solve the problem.

Usually, my class is around 30 students and we separate into ten groups. Each is comproised of three students and we give each group the task of building some small application using a local platform. 

There is a free version of the solution you can use. 

Mostly, the students are very excited about the product due to the fact that they can make applications without coding.

Students do have some difficulties translating the hard code. They are usually using code from a previous course.

My understanding is that, if you are not using the free version, it is very expensive. 

We'd like more support and more publication of use cases and examples so that students can more easily study the product and better understand how it works and its applications. 

I've used the solution for two or three years. 

The solution has been stable. We haven't had issues with it having bugs or glitches and it doesn't crash or freeze. It's reliable and the performance is good. 

The free version has some restricted functions. It doesn't give you access to the full solution. 

The only technical support is from the documentation and website, no more. If a customer has difficulty figuring out how to use it, they can start with the documentation and learn how to use it, how to set it up, et cetera. They can learn to build an application with restricted functionality from the free version and go from there. 

We use usually two platforms - Mendix and OutSystems. So we freely let the students make the choice as to whether they use Mendix or OutSystems and usually 50% use OutSystems and 50% use Mendix.

We take advantage of the free version of the product. 

Once you move away from the free version, it can get pricey.

We're just end-users. 

My students use it. I just view and am not involved intensively in using Mendix.

Coming from a developing country, Indonesia, we hope that Mendix continues to offer a free solution.

It's a very good solution. I'd rate it eight out of ten.

One use case which we're thinking about at the moment is for a clearing platform for security clearing for risk assessment on margin accounts. It happens from time to time that there is a situation called margin call, which is basically a process where one of our operators from the risk unit behind securities needs to get more money or more assets from the client who owns the margin account. 

At the moment, the process is that they have a spreadsheet or checklist in digital form and they go through a highly governed process. They follow a printed-out or virtual copy step-by-step. At each step, they're getting a sign-off and a peer review of each step by a peer in the risk department and it takes forever. It's a lot of admin.

The Mendix base automation is basically replacing this document, this checklist. It just makes it much more helpful as all this has to happen within an hour, that call and getting assets, for example. 

The company is massive and each use case is very different, however, at the moment, those tend to be small processes and trying to cut down the administration, which normally means writing documents, archiving files, scanning documents, that kind of thing, which people currently do manually.

We like Mendix a lot. In terms of technology, it is really good. 

We find it intuitive and easy to use. 

We are quite happy with the solution and look forward to moving to the cloud. We have it hosted in the Docker systems on-prem. When we move to the cloud, we can see that it will be simple. 

We specifically want version control of whatever we deploy in the production. However, with Mendix, unfortunately, storing things in binary is quite a lot. If you put it into Github and stuff like that, we'd like it to be a text type of source code rather than binary. 

There are not enough developers who are using Mendix. The knowledge base available online and in the market is not as rich as other competitors. 

In terms of workflow automation, local automation, they should focus on integrating AI modules. Many companies are trying to build their own models, however, if you compare with how much learning Google has done on their Google models, it makes sense to go for integrations rather than starting from scratch with teaching your AI. That's roughly how we see the domain of RPA and local automation platforms.

The integration or making use of some artificial intelligence and models which are out there could be a lot better. There should be some kind of marketplace. 

The user interface styling is a bit tricky. It's got a restrictive and highly sophisticated styling which could be better.

We put the solution into production about a year ago now.

We have a new platform, which we put into production about half a year ago, and we had an initial 10 sort-of automated processes on top of it at the moment. It's going to grow, obviously. That's the idea.

So far, we are happy with the potential it has for scaling, although in practice we have not yet tried.

We haven't yet had to reach out to technical support and therefore I can't speak to how responsive or knowledgeable they are at this time.

For Mendix, we're not using any kind of collaboration tools or deployment which Mendix provides as we have our own tools and deployment and task management and risk management right inside our organization. We're not going to jump from one tool to another. Just because we have Mendix code, we're not going to use its deployment. We are using current tools, which are established in the enterprise.

It's important that Mendix stays flexible in terms of source code, in terms of deployment, and that it doesn't lock things down. If, for example, there would be a restriction suddenly on which kind of deployment mechanism can be used, then that would cut some customers out. That goes through the approval of risk management. Risk management is very important when you're deploying to production.

We use our own in-house team and tools for implementation purposes.

At the moment, we are using Blue Prism for RPA. We are using also Mendix for the workflow, which is not quite RPA. We're combining those two. We do have an eye on UiPath due to the fact that, in the last year, we're feeling that Blue Prism is falling behind the competition at the moment.

We did look at other tools, however, it wasn't me who did that. It was about two and a half years ago. There was a lot of research on everything on the market. Honestly, I don't know why they picked Mendix, however, they were clearly a strong candidate. Looking at Gartner shows it's a very strong candidate. I was quite surprised that it doesn't have a bigger clientele. 

We are just a customer and end-user.

We're not using the latest version of the solution, however, we're going to upgrade to the latest one. In Mendix, we're using 8.9, however, we're now going to upgrade soon as some of our teams have just started using later libraries, and obviously, that needs upgrading.

We're heavily governed and our governance processes and approvals for cloud take forever. We have these automations deployed on-premise. Both Blue Prism and Mendix are hosted internally and will be for a number of years. We want to go cloud, however, first, we need to get our internal approvals in order.

I'd rate the solution at a seven out of ten. It's one of the best which we touched and we're still happy with it. However, dealing in binary makes me deduct a few points. 

I am currently evaluating the product.

I enjoy the low-code nature of the product.

It's user-friendly and very easy to handle.

The product was easy to set up.

It is stable.

The stability is good.

I'm still in the evaluation phase. I have not fully vetted the entire product yet.

It is expensive.

I've been evaluating the solution for three months. Before I evaluated Mendix, I evaluated OutSystems for six months.

The stability has been good. There are no bugs or glitches and it doesn't crash or freeze. it's reliable. 

The product can scale and expand if you need it to.

We're planning to use it for 100 people.

At the moment, I can't communicate with technical support. It's expensive. I've never dealt with them directly.

I have using the OutSystems and now use Mendix.

It's an easy, straightforward setup. It's not overly complex or difficult at all. Setting it up shouldn't be an issue. 

The solution has been very expensive overall. It was not cheap.

At the moment, I'm looking for a solution for low code, so I am evaluating any product or solution with low code as an option. We already tried OutSystems. Microsoft Power Apps is another solution that may be an option.

I'd rate the solution eight out of ten. I can recommend it as a scalable option. It is easy to use and the evaluation is not expensive. The support is for the moment is good but expensive. 

I'm just a partner and an end-user.

We are building our custom solutions based on Mendix for our clients. Most cases are e-services for the government sector.

It is really a rapid platform where you can minimize the time-to-market, where you can also engage the customer from business perspectives throughout the entire cycle of the development. It is providing really the acceleration to adopt an agility approach.

You can really minimize the time-to-market, which is great.

It is easy to set up.

You can scale the solution.

It's stable. 

The cost of total ownership needs to be better. The licenses are very expensive. If you compare it with, let's say, a kind of BPM, or CRM solutions, the cost is very, very big. 

While the community is great, they need to work on making their direct technical support services better.

I've used the solution for a while.

The product is stable and reliable. There are no bugs or glitches. 

The scalability potential is very good. If you want to expand it, you can. 

There is a weakness in the support. That said, the community is good. You can post your question. You can get support from the community and the answers are quite effective.

They have an amazing academy. They have amazing content for self-learning. Maybe due to that, they don't have that much direct support. They instead seemed to have built a very amazing knowledge base where you can really develop your skills without any direct support and help. Most of our engineers could make the full cycle of e-learning without any class-based training. They also could acquire the certifications without any support. So, even without direct technical support on offer, they have a good online academy.

It's a pretty straightforward setup. It's not overly complex or difficult. It's easy. One DevOps engineer can handle all this stuff for many solutions for many clients. It doesn't require that many resources.

We're a Mendix partner. We have maybe 20 engineers. Most of them are certified. We have Rapid certification and intermediate and advanced certificates. 

We are not a user. We're not a consumer. We are the provider building custom solutions based on Mendix for different clients and different customers in different domains.

I'd advise potential users that the principle of having a citizen developer and a business developer is a good idea. You can engage with the business people from day one with the entire cycle of development. This is maybe the key to having such a platform.

Overall, I would rate the solution eight out of ten.