The MVC (model-view-controller) principle is a generally recommended method for structuring object oriented client software. However, whereas the separation of the M (model) from the VC (view/controller) is obvious and actually found in most software systems, the V-C separation may be sometimes not so clear, especially for Java clients. In contrast to this, SMaker is a module that strictly represents the "V" part of the MVC concept and makes it possible to perform considerable changes in the user interface without having to modify even one line of code. For this reason SMaker is also ideal for prototyping.

The SMaker panel layouts strictly represent only the view part in the MVC, so there exists only a very loose coupling to the application software, given by the IDs of the components. For this reason it is easy to copy and paste part of the layout (groups of related Swing components) from one application to the other or to use the gallery as a storage for proven standard layouts (templates). Be aware that dealing with user interface designs is rather time consuming and this is a big chance to save development time.

The XML files containing the panel layouts may not only be installed locally but could also be retrieved by an URL from a web server. For this reason it is possible to write applications where either the entire user interface or at least part of it may be dynamic. A typical application would be e-commerce where the products and the associated forms are changing frequently but the client software should not be updated at the same rate.