Mendix vs. Retool

Mendix excels in scenarios involving Business Process Automation, making it a strong choice for applications requiring workflow automation, including processes like request approvals, document management, and other business workflows.Conversely, Mendix may be less suitable for projects that demand highly customized solutions with extensive custom coding. Its primary focus on low-code development may not align well with the requirements of projects that heavily rely on intricate and specialized coding.

Incentivized

Works well in: Connecting directly to databases and APIs holding candidate data. Allows teams to easily drill into records from different data sources. Quick to build dashboards. It wouldn't work well without a team to actually get it set up. There is limited design/ branding, making it look very basic. Your team requires training because data can be overwritten easily. Having some knowledge with your whole team is super important, and if you work with contractors or non-tech people, this can be a huge issue.

Incentivized

• We're able to really easily develop different views that are very specific to a customer's needs or customer's different types of user needs. So for example, the production managers can have a certain view that's relevant to them and then certain line managers can have views that are specific to them that allow them to run different scenarios which they define. So it allows us to easily build customized apps for each different type of user.

Incentivized

• Ease of use - someone with small amount of experience can use it.
• Adaptability - you can build a lot of things with it.
• Reliability - works quite well.

Incentivized

• Earlier versions lacked in UI/Ux. This is still improving.
• Since everyone and anyone can create custom add ons (widgets), Mendix could improve their quality checks (but not as rigid as eg Apple).
• Upgradeability used to be somewhat of an issue. Version 7 looks to be handling this better than previous versions.

• Some Retool apps can become slow to load or refresh.
• When multiple team members work on the same app, changes can overwrite each other or break functionality.
• The UI/UX is pretty basic.

Incentivized

A 10 would say I have nothing to wish for. A 9 means I haven't seen anything better.This tool really helps you in the whole creation and maintenace cycle, so from requirements to building/modeling to testing to deploying to capturing feedback.

Because even though it is quite intuitive it is not the best tool I have ever seen.

Incentivized

Response times are quick and you will get updates regularly about the status of your request. Even with very technical questions they have specialists that can help you with your problems it will give you an answer or help you with a work around.

Mendix would be my preferred system all the way. The system is designed for these kinds of works. I've worked with WP and DNN but they should be used just for websites. To create an app for a business value, I would suggest Mendix. Also, the offline capabilities of Mendix have greatly improved since the deployment of Mendix 7.13.

We selected Retool because it offers the best balance of usability and power compared to alternatives like Appsmith, ToolJet, and OutSystems. It allows us to build much faster, with broad integrations and strong enterprise features like permissions and environment management. Competing tools were either too limited, required more engineering effort. Overall, retool support has been decent too.

Incentivized

• It helps to speed up application development because of its low code by the fact that it's low code. It allows professional developers to focus more on specialized application development rather than the more routine application development that business IT and super users can do for themselves with some coaching from the IT department. So it's just allowing the more specialist professional developers.net, for example, Java in our organization to focus on more complex engineering application developments.

Incentivized

• Major impact - ability to build a backend system is huge.
• Major impact - used every day by multiple people.
• Major impact - ability to be used by less technical teammates.

Incentivized