Muutke küpsiste eelistusi

E-raamat: iOS Architecture Patterns: MVC, MVP, MVVM, VIPER, and VIP in Swift

Teised raamatud teemal:
  • Formaat - PDF+DRM
  • Hind: 67,91 €*
  • * hind on lõplik, st. muud allahindlused enam ei rakendu
  • Lisa ostukorvi
  • Lisa soovinimekirja
  • See e-raamat on mõeldud ainult isiklikuks kasutamiseks. E-raamatuid ei saa tagastada.
Teised raamatud teemal:

DRM piirangud

  • Kopeerimine (copy/paste):

    ei ole lubatud

  • Printimine:

    ei ole lubatud

  • Kasutamine:

    Digitaalõiguste kaitse (DRM)
    Kirjastus on väljastanud selle e-raamatu krüpteeritud kujul, mis tähendab, et selle lugemiseks peate installeerima spetsiaalse tarkvara. Samuti peate looma endale  Adobe ID Rohkem infot siin. E-raamatut saab lugeda 1 kasutaja ning alla laadida kuni 6'de seadmesse (kõik autoriseeritud sama Adobe ID-ga).

    Vajalik tarkvara
    Mobiilsetes seadmetes (telefon või tahvelarvuti) lugemiseks peate installeerima selle tasuta rakenduse: PocketBook Reader (iOS / Android)

    PC või Mac seadmes lugemiseks peate installima Adobe Digital Editionsi (Seeon tasuta rakendus spetsiaalselt e-raamatute lugemiseks. Seda ei tohi segamini ajada Adober Reader'iga, mis tõenäoliselt on juba teie arvutisse installeeritud )

    Seda e-raamatut ei saa lugeda Amazon Kindle's. 

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. Youll find out why its important for your applications to be based on these patterns and which ones are the most common. Then youll look at the MVC as one of the best known and used patterns. Youll see how and when it can be implemented in your applications, as well as its advantages and disadvantages. 





From there, youll 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 withthe views through Data Binding. With those prominent patterns covered, youll 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 architecturepatterns, those who already have more experience and are looking for a starting point on complex patterns such as VIPER or VIP, and beginner programmers
About the Author xi
About the Technical Reviewer xiii
Acknowledgments xv
Introduction xvii
Chapter 1 Introduction
1(44)
What Is Software Architecture?
2(1)
Architecture Patterns
3(1)
Why Do We Need an Architecture Pattern for Our Applications?
3(2)
Design from High Level to Low Level
5(1)
Design Patterns
6(4)
SOLID Principles
10(1)
How to Choose the Right Architectural Pattern
11(2)
Most Used Architecture Patterns
13(1)
In Search of a "Clean Architecture"
14(1)
Clean Architecture Layers
14(3)
The Dependency Rule
17(1)
Advantages of Applying a Clean Architecture
17(1)
MyToDos: A Simple App to Test Architectures
18(1)
App Screens
18(10)
App Development
28(15)
Summary
43(2)
Chapter 2 MVC: Model-View-Controller
45(62)
What Is MVC?
45(1)
A Little History
45(1)
Apple Model-View-Controller
46(1)
Components in MVC
47(1)
Model
47(1)
View
48(1)
Controller
49(1)
Advantages and Disadvantages of MVC
49(1)
Advantages of the MVC Pattern
49(1)
Disadvantages of the MVC Pattern
50(1)
MVC Application
51(1)
MVC Layers
51(13)
MyToDos Application Screens
64(25)
Testing
89(16)
Summary
105(2)
Chapter 3 MVP: Model-View-Presenter
107(38)
What Is MVP?
107(1)
A Little History
107(1)
How It Works
107(1)
Components in MVP
108(3)
Advantages and Disadvantages of the MVP
111(1)
MVP Application
112(1)
MVP Layers
112(4)
MyToDos Application Screens
116(23)
MVP-MyToDos Testing
139(5)
Summary
144(1)
Chapter 4 MWM: Model-View-View Model
145(80)
What Is MVVM?
145(1)
A Little History
145(1)
How It Works
145(1)
Components in MVVM
146(2)
Advantages and Disadvantages of MVVM
148(1)
Advantages
149(1)
Disadvantages
149(1)
MVVM Application
150(1)
MVVM Layers
151(4)
MyToDos Data Binding
155(9)
MyToDos Application Screens
164(34)
MVVM-MyToDos Testing
198(8)
MVVM-C: Model-View-ViewModel-Coordinator
206(1)
What Is a Coordinator?
206(2)
Using MVVM-C in MyToDos
208(16)
Summary
224(1)
Chapter 5 VIPER: View-Interactor-Presenter-Entity-Router
225(60)
What Is VIPER?
225(1)
A Little History
225(1)
How It Works
226(1)
Components in VIPER
226(2)
Advantages and Disadvantages of VIPER
228(2)
VIPER Application
230(1)
Communication Between Components
230(4)
VIPER Layers
234(2)
MyToDos Application Screens
236(39)
VIPER-MyToDos Testing
275(7)
Summary
282(3)
Chapter 6 VIP: View-Interactor-Presenter
285(80)
What Is VIP?
285(1)
A Little History
285(1)
How It Works
285(1)
Components in VIP
286(7)
Advantages and Disadvantages of VIP
293(1)
VIP Layers
294(2)
MyToDos Application Screens
296(55)
VIP-MyToDos Testing
351(13)
Summary
364(1)
Chapter 7 Other Architecture Patterns
365(20)
Introduction
365(1)
RIBs: Router, Interactor, and Builder
366(1)
A Little History
366(1)
How It Works
367(1)
Components
368(2)
Advantages and Disadvantages
370(1)
The Elm Architecture
371(1)
A Little History
371(1)
How It Works
372(1)
Components
373(1)
Advantages and Disadvantages
373(1)
Redux
374(1)
A Little History
374(1)
How It Works
375(1)
Components
375(2)
Advantages and Disadvantages
377(1)
Advantages
377(1)
Disadvantages
378(1)
TCA: The Composable Architecture
378(1)
A Little History
378(1)
How It Works
379(2)
Components
381(1)
Advantages and Disadvantages
382(1)
Advantages
383(1)
Disadvantages
383(1)
Summary
384(1)
Chapter 8 Conclusion
385(4)
The Importance of Clean Architecture
385(1)
Moving Forward
386(3)
Index 389
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 hes learned and studied about the world of mobile development.