VIP, not a VIPER, Clean Swift Architecture
summary
Claims that VIP is a unidirectional VIP cycle that fixes Massive View Controllers and differs from VIPER by routing and responsibilities, shows a small UIKit app fetching Hogwarts API wired with a network worker, interactor, presenter and router, uses Clean Swift Xcode templates (deprecated but usable), includes basic unit-test patterns, reports use on a large codebase with about two dozen network goals, and concludes VIP works well for large projects but feels heavy for SwiftUI or small apps.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 0:57What is VIP
- 4:03VIP Architecture
- 10:22Example App
- 13:10Scenes
- 15:47House List
- 25:15Project Overview
- 25:48Easy to Understand
- 27:08What goes where
- 28:17Does it work with SwiftUI
- 29:17Learn more about VIP
- 30:00Outro
related talks
11mVIPER architecture
26mBuilding a Framework with VIPER
23mSimplified VIPER architecture
01h 02mA comparative approach to MVC, MVVM and VIPER: taking the best ideas without fighting against the platform
27mFull Stack Development with Swift and Vapor
33mMVVM as good (anti)pattern in iOS
22mMVVM at Scale: Not so Simple
43mRefactoring a Massive View Controller in Swift