In this chapter, we used the domain modeling framework, dartling, to build an app, from designing the model to generating and testing the application's code. Then, we discussed the universally applied MVC pattern and used it together with dartling to build a complete and usable todo app. In this process, the advantages of using a domain modeling framework became apparent. Once a model is designed, its code is generated, which is a big deal for large models. Although the code for the model is generated, a programmer may add some specific code that will not be lost if the model is regenerated. The API of dartling, for example, for entities, is rich and it allows the handling of identifiers and relationships, which is not done in Dartlero. The code in the TodoMVC application clearly shows that, after the code is generated, there is not much model programming left to do, allowing a developer to focus on the UI.

In the next chapter, we'll get an overview of the MVC and UI frameworks built...