The State of UX design & Mendix - Mendix Forum

The State of UX design & Mendix


A lot of the time Designers/frontenders are forced to work against the Mendix platform because it is forcing certain elements to behave in a specific way which is not always beneficial for the User experience.

Most frustrations come from:


Related Questions

Where are the instructions/examples for setting the Class?

Setting .focus on first input field

mx-listview-selectable is on the non selectable listviews?

why are Building Block version locked?

Remaking the docs navigation tree?

Is there a way to add ".active" to a button it if is links to the page we are currently on?

Best practice cross-application styling

Best way to sync styling across apps?

customizing the modal pop up layout

What is the usecase for resizing and repositioning the Modal Popup?

Help styling input fields

Extending glyphicon set with custom icons

Can we Customize Template Grid?



Related Ideas

Visibility based on editabilty

New grid widgets to replace grid/template grid / listviews for UI flexibility

A sortable and editable Template Grid

Copy Paste between modelers

Make layouts and building blocks not version locked

Condition classes

Cross-application styling / sync UI resources

Intuitive way of sharing / maintaining your company UI Resources

How to keep AtlasUI updateable and still customize your own SASS files?

Make navigation tree's great again

Bootstrap 4 support (closed)

Beter Empty listview, datagrids options

Make type of input textbox widget editable

As a user I want to see the correct keyboard when entering data in an input widget

Enable Changing Icons for Reference Set Selectors

More glyphicons to choose from

make tabs in main window smaller when there are more (like web browsers do)

modeler only layout grids

Align UX Resources




beter way for styling checkboxes and radio buttons (Implemented in MX 8.0)

Clickable container with same functions as a button (MX 8.3)





I will try to keep this post up to date with any UX topics I see, also post them in the comments if you see any I have missed

8 answers

@Wojciech Machniak We are not sure about Bootstrap 4 yet. Maybe a part of it.

I’ll look into the interpolation issue, but it’s better to create a PR or an issue on the AtlasUI github in the future. This makes it easier for both of us :)


@Wojciech Machniak there is this closed topic (8 months ago):


We are indeed looking into this, but we also need to take backwards compatibility into account."

“looking into this” is a very vague answer.

maybe reCreate a new ideatopic so we can discus the pro’s cons of MX implementing bootstrap 4 (I’ll add it to the links).


@Jason Teunissen It’s true what are you saying. But I would like to know what is a plan for a future of Atlas UI


I dont think upgrading the CSS framework will solve a lot of ux problems
UX is not CSS, CSS is a tiny part of what creates the UX.


@Wesley Do you consider upgrade to Bootstrap 4?

If you are responsible for improvements in Atlas UI, please check one thing:

I have noticed an errors in compiled lib.css file.
You have an issue in directory theme/styles/sass/lib/components/_buttons.scss

// Button Sizes
.btn-lg {
    font-size: $font-size-large;
    img {
        height: calc($font-size-small + 4px);

You should interpolate SASS variable inside calc function. #{$font-size-small}

Hope this helps!


@jason Thanks for this overview. We’re currently working hard to improve Atlas. I’ll definitely look into these points and see what I can improve. Will keep checking this for updates!


@mitchel to a certain extent that is possible, you can delete the Atlas theme and possibly the Mendix css.

the problem is that Mendix generates a lot of inline styling and by adding the class “-stylingless” it adds extra classes that override other classes that you will then also need to override.

Atlas also has “!important” in some css elements making it even more clumsy to work around.

also view:


Or instead release a base theme with just the bare necessities that allows for a full custom style. Also, with the disclaimer that it will not be fully ready (stylish) out of the box. But without the need to fully start from scratch.