You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 22, 2025. It is now read-only.
是关注点分离的 (separation of concern),这是一个很清晰的设计模式,具备单一的清晰权责
2. 测试
三、让架构能够在未来几年都能够适用
四、糟糕的架构是什么样的
四、设计模式
1. 设计模式该怎么用
2. 组合设计模式 (Composition)
3. 依赖注入 (dependency injection)
五、流行的架构模式
1. MVC
2. VIPER
3. MVVM
六、我们能做什么
1. MVVM+
2. Flow Coordinator
3. Coordinator Redux
七、ReSwift
八、代码注入工具
九、总结
十、Q&A
ShannonChenCHN
changed the title
读『[优秀的 iOS 应用架构:MVVM、MVC、VIPER,孰优孰劣?](https://academy.realm.io/cn/posts/krzysztof-zablocki-mDevCamp-ios-architecture-mvvm-mvc-viper/)』
读『优秀的 iOS 应用架构:MVVM、MVC、VIPER,孰优孰劣?』
Oct 14, 2017
No description provided.
The text was updated successfully, but these errors were encountered: