VIPER ( ? OR : AND) MVVM
Download as PPTX, PDF0 likes311 views
The document discusses the VIPER architecture, explaining its components (View, Interactor, Presenter, Entity, Router), pros such as flexibility and maintainability, and cons like complexity and overengineering risks. It also compares VIPER with the MVVM architecture and concludes that while VIPER has advantages, it's important to adapt and mix architectures based on specific use cases. References to additional resources are provided for further reading.
VIPER ( ? OR : AND) MVVM
- 1. VIPER ( ? OR : AND) MVVM by Roxane Markhyvka
- 2. Agenda ● What is VIPER? ● Common problems and solutions ● How does MVVM fits in? ● Conclusions
- 3. What is VIPER? ● View - user interface, usually UIView or UIViewController subclass. ● Interactor - business logic layers, like API, Persistent Storage etc ● Presenter - fetches data from Interactor, passing it to View (modified if needed) and processing user initiated actions from View. ● Entity - model in business logic, usually a struct ● Router - knows only of navigation that can happen from current screen.
- 5. VIPER: cons ● Too many files ● Confusing communication (who owns who) ● Delegation of responsibilities (since all components are visible and available)
- 6. VIPER cons: Too many files Presentation Business logic
- 7. VIPER cons: Who owns who strong weak strong reference from UIWindow strong weak weak strong by injection DI creates creates and holds
- 8. VIPER cons: Delegation of responsibilities ● UIKit ● Life cycle ● User Interaction ● UIKit ● Navigation ● fetching data from interactor ● converting data to representable ● filling View with data ● process output from view ● delegate to router ● provide data on request ● create Entities ● dumb model
- 9. VIPER: pros ● Flexible and reusable ● Easily maintainable ● Convenient for large teams ● Decoupled distribution of responsibilities ● Testable ● Cross platform code review with Android team (this last one is so not my idea :) https://medium.com/@ankoma22)
- 10. VIPER in code: View
- 11. VIPER in code: Presenter
- 12. VIPER in code: Router
- 13. In real life...
- 14. What is MVVM?
- 16. VIPER + MVVM in code
- 17. Conclusions Like any other software architecture, VIPER has its pros and cons. It is easy to fall over to overengineering side of the story with VIPER, so don’t be afraid to put in a little extra to the mix when you see fit. Pursuing sole architecture in your app often won’t give you the relief it has promised, and not because the architecture is bad, but solely because any of the patterns simply can not forsee each and every use case your app will throw at you.
- 18. References 1.https://www.objc.io/issues/13-architecture/viper/ 2.https://medium.com/ios-os-x-development/ios-architecture-patterns-ecba4c38de52 3.https://clean-swift.com/clean-swift-ios-architecture/ 4.https://medium.com/@ankoma22/the-good-the-bad-and-the-ugly-of-viper-architecture- for-ios-apps-7272001b5347 5.Lotus MVC - https://matteomanferdini.com/ios-architecture-lotus-mvc-pattern/ 6.Xcode templates - https://blog.kulman.sk/creating-your-own-xcode-templates/
- 19. The end Q & A
Editor's Notes
- #7: Xcode templates