Building a Framework with VIPER
summary
Implementation of VIPER as a reusable framework that actually ships: a protocol-first module called VideoPlaybackKit that exposes a simple enum videoType and supports play pause and scrub while the interactor talks to a playback manager and the presenter formats UI without importing UIKit. Navigation is router removed in favor of a Builder and Contract pattern that wires dependencies. Claims: highly testable, single-responsibility, easier reuse; caveats: extra boilerplate, slower for fast-iteration teams, avoid auto-generators until familiar with VIPER.
AI-written summary · about
chapters (8)
- 0:00Introduction to speaker
- 1:10What is VIPER?
- 3:26VIPER components breakdown
- 7:02Inputs and outputs
- 10:45Real world example
- 12:30Implementation demo
- 13:34Code walk-through
- 22:33Pros and cons of VIPER
related talks
31mVIP, not a VIPER, Clean Swift Architecture
11mVIPER architecture
42mClean Architecture with VIPER
32mVIPER: Advantages, Drawbacks, Practice and Related Questions
26mVIPER on Android
18mBuckets of Code
16mSwiftUI API Design Lessons:Bridging Procedural APIs with theDeclarativeWorld
46mPreviews and Package Oriented Programming