The initial setup is very easy. There is nothing to do. The setup in development environment capabilities, they even provide citizen development capability,  which makes them very competitive. 

I'd rate the ease of setup five out of five. However, if you're trying to install this in an on-prem environment, it is a hassle on its own for integration. We are not talking about integration. We are talking about just the initial setup.

The length of deployment depends on the problem the company is solving, the use case, and a bunch of different things around it. It varies.

For one company we work with, we can build our own connectors, private connectors. We did that in hardly three to four weeks, which that company itself could not do on its own. A lot of things are available in the background, however, if we decide we want to do something a certain way, we'll just build it that way.

With a low-code environment, traditionally, you need fewer people to maintain everything. You only need one person to do the external integration, for example. You need one person who can do custom UI development for sure, as for any project you hit, you will have 30% custom development, for sure. 

IF you have a team of five, where three are purely Mendix developers and two are full-stack developers, they can deliver anything. It's not like SAP where you need specifically SAP people to handle everything. 

The initial setup for Mendix was straightforward. You just have to download Mendix Studio Pro if you are using a desktop computer, and you can create your app very easily. If you are using the cloud version, for example, Mendix cloud or any other cloud, especially as any other cloud is hosting Mendix, it's really easy to access the developer. All partners develop the portal access where Studio and Studio Pro are enabled for my company, so my team can work on any cloud-based application. Setting up Mendix was very easy.

It is easy, but you have to have a governance model. You can't just drop it in and hope it works. It involves going in and making sure that you are controlling it.

The actual deployment was pretty fast. It only took a couple of days, but it took probably nine months of planning. There were lots of talks related to what is a governance model and what happens when it goes live. All the planning around what it means to have it live took about nine months, but the actual deployment was over a weekend.

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.

You don't need to do any setup for Mendix because it's on the cloud, but you need to install the studio version, which took only five minutes to get the platform up and running.

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.

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.

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

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. 

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

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.

The solution is very straightforward, due to the fact that it's all cloud-based infrastructure, and there's low-end stuff that a citizen developer could do pretty easily. For our onboarding, if we have new developers, people who were actually back with their schooling, compared to some other products, and typically they're on their own doing development within one month of starting training. This is compared to some of our more complex solutions. They may be shadowing and have oversight for six to seven months. The onboarding process to learn it is very, very quick. Therefore, a company shouldn't have any issues with the initial setup.

In terms of maintenance, we have a person on the team that creates a backlog of small work to do once a month, and that's it. There are no updates, or new deploying, or anything like that that is necessary.

The initial setup of Mendix is straightforward.

The solution is very easy to set up the solution. I'd rate the ease of setup nine out of ten. 

It hardly takes a minute to deploy. I can't speak for complicated projects however, since I have yet to be a part of one. As per my current experience, it's very fast and takes minutes or less. 

You only need one person to handle maintenance tasks once it is set up. 

The initial setup was fairly straightforward. The time it takes to complete the setup depends on an organization's internal requirements. The maintenance of Mendix is also straightforward butI would recommend using experienced resources to know Mendix. 

The initial setup was simple. It's not difficult to do yourself. 

Installing the solution took from five to 10 days to ensure proper integration with, say, the active directory and other tools for data migration.

We handled the deployment.

For small applications, it definitely is easy to set up. From my coworkers, I understand if you want bigger applications, it's harder to adapt. However, that's what we see with all the local platforms.

I also worked on another platform where deployment could easily take hours. Yet, with Mendix, it was minutes. That was really good. It’s so fast.

The installation is fairly simple.

We had Mendix support, with a cycle of five deployments per night. Setting up the infrastructure took us about a week the first time, but it became easier and quicker afterwards. When we deploy for the second time, it only takes a fraction of the time compared to the initial deployment.

The initial setup is really easy all you need to do is create a Mendix account, create a project, fill in some basics for the project like the name, choose a base theme and then you are good to go. You will automatically get a sandbox environment connected to it, which is basically a free node in the cloud environment from Mendix to test and share your application with others. Using the Mendix Sprint environment you can also easily share the Mendix model with others to either develop or just review the application.

Very straightforward from first version of your web-app to deployment.

The initial setup was both straightforward and complex.

Setup is an easy wizard installation process. It is straightforward and downloads and installs missing dependencies like the Java Runtime and SDK.

Mendix presents a deceptively simple environment that seems too shallow for many techies, but is not. It does present a completely different paradigm and team culture and to leverage Mendix a change in corporate culture might be required. From us and them, to a integrated innovative whole where technologists can focus on delivering value to the rhythm of business demands. Convincing classical techies might be a challenge and this often limits the success of implementations.

Simple, and there is a free course which shows all the in and outs of how to use the modeler to design and develop a solution. It helps, but it's not necessary if you have Java experience, for those cases where you want to go further than the standard.

The initial setup was easy and straightforward. Just an exe to run. Also they provide good 18 Hrs training for you to get started with the product.

The initial setup was not too complex, but it took some time. I would say that it was mid-difficulty.

Our deployment took about four to six weeks, and then we used it for some of our application development builds. We took some of the agile projects and aligned them to that.

The setup is very straightforward. Download the right modeler and start building apps!

Even if you do not know the platform at all you can learn to build Mendix applications in hours even with no program experience. It is better to have a good knowledge of your business processes than knowing how to program. That last part is easier learned than the other way around.

Pretty straightforward . Mendix is a one-stop solution with most things integrated and it would require only a few changes such as custom configurations for various aspects like the database, to bootstrap a project and start building solutions.

It's very straightforward. I used to be a mainframe tester and was able to start developing in Mendix in a short period of time.

It was straightforward.

It was straightforward.

It's straightforward. It depends on the choice of on-premise or cloud implementation as to how easy it is. For on-premise implementation you need some expertise, while the cloud implementation just needs you to follow the manuals or take a one day training course.

No, there is alot of support for getting started, from videos to tutorials.