Why use React Widgets when we have mendix UI elements already?

Hello everyone,   I was part of a debate today where this specific topic was discussed in order to make some process decisions. Could you elaborate an answer (hopefully with examples) where you can clearly state the use of react widgets inside the mendix ecosystem? Why not just use nanoflows for javascript actions and the already existing UI components the platform offers?   Thanks
3 answers

Great question and discussion.

My opinion is that you should stay as much as possible with the standards. Since these are platform supported and with conversions to newer versions of Mendix, you can relpy on Mendix. Thats the whole idea behind a low-code platform.

Although you can certainly extend the capabilities of Mendix with your own react widgets. But only when

  1. It adds real value to the app users = business valie
  2. It is maintainable
  3. The dev(ops) team has the knowledge to create and maintain it.

Above count for use of custom Java as well.

Not because the developer wants to show off its own capabilities by making unmaintainable fancy pancy shizzle.


Rene has already eloquently stated the right approach to React widgets versus Mendix UI elements. So, having that in mind, the main use case for a React widget is when Mendix has no option to implement one of your user’s wishes. For instance, they want to be able to play Tetris incorporated in their Mendix app and store the top-scores in the Mendix database. You want a live example: https://service.mendixcloud.com/p/game/tetris.



just leave this here ;-)