This document discusses and compares several common app architectures - MVC, MVP, MVVM, and VIPER. It defines each architecture and explains the separation of concerns, flow of information, and benefits of each. While there is no single best approach, the document conveys that architectural patterns help organize an app's components and determine how to structure the app as it grows in size and complexity.

1. App Structure
Fundamentals
MVC, MVP, MVVP, and VIPER
www.Pyranova.Tech 1

2. Content
● What is app structures ?
● Purpose of session.
● App structures
○ MVC
○ MVP
○ MVVM
○ VIPER
● Concoulasion.
● Reference.
2
www.Pyranova.Tech 2

3. What is app structures ?
● Organize your application’s component.
● Determine your app scale “as developer”.
www.Pyranova.Tech 3

4. Purpose of session
● Know the most used App structures.
● Determine the best structures you should follow to work in your app.
www.Pyranova.Tech 4

5. Purpose of session
TO
www.Pyranova.Tech 5

6. App Structures
○ MVC
○ MVP
○ MVVM
○ VIPER
www.Pyranova.Tech 6

7. What is MVC ?
● separation of concern
Model - View - Controller
www.Pyranova.Tech
7
7

8. MVC Architecture.
www.Pyranova.Tech
8
8

9. Example.
www.Pyranova.Tech
9
9

10. Why MVC ?
● Faster development process.
● Easier to Debug .
● Good in case of small apps.
www.Pyranova.Tech
10
10

11. App Structures
○ MVC
○ MVP
○ MVVM
○ VIPER
www.Pyranova.Tech 11

12. What is MVP ?
● separation of concern
Model - View - Presenter
● Start using delegate.
www.Pyranova.Tech
12
12

13. MVP Architecture.
www.Pyranova.Tech
13
13

14. Example.
www.Pyranova.Tech
14
14

15. Example
15
15www.Pyranova.Tech

16. Why MVP ?
● Clear separation of responsibilities between components.
● Easier in test.
www.Pyranova.Tech
16
16

17. App Structures
○ MVC
○ MVP
○ MVVM
○ VIPER
www.Pyranova.Tech 17

18. What is MVVM ?
● separation of concern
Model - View - ViewModel
● View model is connect chain between View and model.
www.Pyranova.Tech
18
18

19. MVVM Architecture.
www.Pyranova.Tech
19
19

20. Example.
www.Pyranova.Tech
20
20

21. Example.
www.Pyranova.Tech
21
21

22. Why MVVM ?
● Distribute responsibilities between classes in a application.
● Easier in test.
www.Pyranova.Tech
22
22

23. MVP vs MVVM ?
www.Pyranova.Tech 2323
protocol StudentsViewPresenterProtocol: class {
func updateStudent (name: String, isJoined: Bool)
func showMessage (message: String)
}
protocol ViewModelUIDelegate: class {
func viewWillUpdate()
func viewDidUpdate(requestUrl: String)
func showErrorView(error: String)
}

24. App Structures
○ MVC
○ MVP
○ MVVM
○ VIPER
www.Pyranova.Tech 24

25. What is VIPER ?
• separation of concern
most like MVC, MVVC
• modular approach
each feature = module service by 5 classes.
www.Pyranova.Tech
25
25

26. VIPER Architecture.
www.Pyranova.Tech
26
26

27. VIPER Architecture.
• Viper is a delegation driven architecture. So, One layer calls
another through a protocol.
• Protocols :
PresenterToViewProtocol
ViewToPresenterProtocol
InteractorToPresenterProtocol
PresentorToInterectorProtocol
PresenterToRouterProtocol
www.Pyranova.Tech
27
27

28. Example
www.Pyranova.Tech
28
28

29. Example
www.Pyranova.Tech
29
29

30. Example
www.Pyranova.Tech
30
30

31. Why VIPER ?
• Make the structure more modular
• Very good environment for unit testing.
• Reduce the load and dependency on controllers.
• Working with constantly changing requirements.
NOT good in case of small apps
www.Pyranova.Tech
31
31

32. Concoulasion
● App structure is to organize your application’s
component.
● There is no best and worst.
www.Pyranova.Tech
32
32

33. References
• https://medium.com/@smalam119
• https://danielmiessler.com/study/mvc
• https://blog.pusher.com/mvvm-ios
• https://medium.com/@vigneshwaran_89879/mvc-vs-mvv
m-vs-mvp-vs-viper-which-design-architecture-is-suitable-f
or-ios-bb1f32328bd8
• https://medium.com/swift-india
• https://medium.com/@saad.eloulladi/ios-swift-mvp-archit
ecture-pattern-a2b0c2d310a3
www.Pyranova.Tech
33
33