Following software design principles
Up to this point, we have reviewed various patterns at different levels, ranging from designing a state management approach to a full-blown app architecture. One observation you may have made is that many of these patterns are not specific to Flutter. Architectures such as MVVM and MVI are common in various software domains, as are concepts such as dependency injection and n-tier architecture. However, we have adapted these patterns to suit the specific intricacies of Flutter.
In the next chapters, we will dive deeper into the specifics of Flutter. Before we do that, however, I would like to discuss one last topic: how to apply general software design principles to Flutter.
Deciphering the acronyms of SOLID, DRY, KISS, and YAGNI
If you have been in software development for some time, chances are you have heard about some or all of these acronyms when discussing code quality and architecture decisions. Programmers seem to be fond of acronyms...
