Read more
Develop well-structured applications using tested techniques and patterns. When you start to develop an application, you not only have to think about the idea of the finished application, but also about how it will evolve as it is built. This book shows you how to plan for changes, scope creep, and for the possibility of other developers joining in.
Start by learning what architecture patterns for an application are. You'll find out why it's important for your applications to be based on these patterns and which ones are the most common. Then you'll look at the MVC as one of the best known and used patterns. You'll see how and when it can be implemented in your applications, as well as its advantages and disadvantages.
From there, you'll discover the first evolution of the MVC model: the MVP, which introduces a new layer (Presenter) to better manage views. The next evolution after that is the MVVM, which introduces the ViewModel layer and its connection with the views through Data Binding. With those prominent patterns covered, you'll read about VIPER and VIP, Architecture Patterns that seeks to make applications easily maintainable, modularized, and highly scalable. All of which are hallmarks of Clean Architecture.
Architecture patterns have developed and evolved to give your applications solid foundations. Understanding these patterns, you will reduce the problems that may arise when modifying existing functions, adding new ones, or correcting errors that may arise in the development process.
What You'll Learn
- Code cleanly with solid foundations
- Start your project ready to adapt and evolve as features and other developers are added
- Find and apply the right patterns for the best results
Who This Book Is ForDevelopers with some programming knowledge who want to learn different architecture patterns, those who already have more experience and are looking for a starting point on complex patterns such as VIPER or VIP, and beginner programmers
List of contents
1. Introduction
1.1. What are architecture patterns?
1.2. Why we need an architecture pattern for our apps?
1.3. The search for a 'Clean Architecture'.
1.4. How to choose the right architecture.
1.5. Most used architecture patterns.
2. MVC: Model-View-Controller
2.1. What is MVC.
2.2. Components in MVC.
2.3. How it works.
2.4. When to use MVC.
2.5. Applying MVC.
2.6. Testing.
2.7. Advantages and disadvantages of MVC.
3. MVP: Model-View-Presenter
3.1. What is MVP.
3.2. Components in MVP.
3.3. How it works.
3.4. When to use MVP.
3.5. Applying MVP.
3.6. Testing.
3.7. Advantages and disadvantages of MVP.
4. MVVM: Model-View-ViewModel
4.1. What is MVVM.
4.2. Components in MVVM.
4.3. How it works: Data binding.
4.4. When to use MVVM.
4.5. Applying MVVM.
4.6. Testing.
4.7. Advantages and disadvantages of MVVM
4.8. MVVM-C: Abstracting Navigation from MVVM
5. VIPER: View-Interactor-Presenter-Entity-Router
5.1. What is VIPER.
5.2. Components in VIPER.
5.3. How it works.
5.4. When to use VIPER.
5.5. Applying VIPER.
5.6. Testing.
5.7. Advantages and disadvantages of VIPER
6. VIP: View-Interactor-Presenter
6.1. What is VIP.
6.2. Components in VIP.
6.3. How it works.
6.4. When to use VIP.
6.5. Applying VIP.
6.6. Testing.
6.7. Advantages and disadvantages of VIP
7. Other Architecture Patterns
7.1. RIBs: Router, Interactor and Builder
7.2. TCA: The Composable Architecture7.3. Redux7.4. TEA: The Elm Architecture
8. Conclusion
8.1. Importance of Clean Architecture.
8.2. Moving Forward
Audience: Intermediate
About the author
Raúl Ferrer García holds a doctorate in Chemistry and started short-circuiting computer science by programming with a ZX Spectrum when he was 14. For the past decade as a Mobile Tech Lead, he has dedicated himself completely to the development and management of mobile applications for iOS. He also maintains a blog in which he tries to explain everything he's learned and studied about the world of mobile development.
