A quick introduction over what you'll be learning this book, what the goals are of this work, and what you'll need to get started.
There are a lot of aspects to consider when selecting an architecture for you and your team. This chapter provides a high-level overview of these aspects, such as qualities to look for in an architecture and more.
In this book, you’ll use a fully-fledged, real-world example app, reconfigured each chapter for the specific architectures that this book will cover. The app used through this book is Koober, a ride-hailing app with just enough complex features to give you a feel for different architectures.
We all depend on one thing or another in the real world, and architecting your applications is no different. You’ll learn how objects depend on other objects to prevent creating monolithic objects from doing all the work, and instead see how compartmentalizing can make them more reusable and testable.
In this chapter, you’ll be taken through the history of MVVM and its concepts. You’ll then walk through the Koober application and explore how it’s been architected using the MVVM architecture approach.
In this chapter, you’ll be taken through the history of Redux and its concepts. You’ll then walk through the Koober application and explore how it’s been architected using the Redux architecture approach.
Elements is an architecture meant to make iOS development fun and flexible. Elements organizes your codebase and makes your project easy for anyone to navigate. This organization allows you to make changes to layers of your application without affecting stability. A set of "Elements" make up the architecture.
In Part 1 you learned about Elements and how to design User Interface and Interaction Responder elements. In this chapter, you'll take a deep dive into two more elements: Observer and Use Case.