So my perspective is: - have worked as a designer for enterprise clients - have worked as a designer for startup/smaller businesses - have worked as a develo

So my perspective is: - have worked as a designer for enterprise clients - have worked as a designer for startup/smaller businesses - have worked as a developer for enterprise, and for B2B serving enterprise clients - have worked as a front-end GUI developer for enterprise, and for smaller businesses, and for B2B serving enterprise clients I am not saying that, even in certain cases where it would be useful, UIs shouldn't be "built" by end users gluing together stuff. Obviously that is necessary sometimes. Just that that is not really a common need. It is a common request though, and that request is normally made by executives. Regardless of if a framework is used or not, the reason it is normally a bad suggestion is that it multiplies the complexity of development, normally by at least an order of magnitude. So it is particularly ill-suited for simple internal CRUD applications. Which, as you say do not need much in the way of "UI". Except they do, just not the highly polished stylised kind. That UI can often be thrown together by the person with the most domain knowledge at the time of creation, ie the developer