App Architecture By Manual DI

Tokyo iOS Meetup
https://www.meetup.com/ja-JP/TokyoiOSMeetup/events/250300377/

Transcript

1. App Architecture by Manual DI @yoshikuni_kato Tokyo iOS meetup 2018/07/21 1
2. Who am I ? • Yoshikuni KatoʢՃ౻༝܇ʣ • iOS Engineerʢ3.5 yearsʣ • Yahoo! Japan -> OHAKO -> Pangea • Twitter: @yoshikuni_kato • GitHub: @yoching • Interests: Software Design, FRP (ReactiveSwift), UI Implementation 2
3. Agenda 1. Coordinator Pattern 2. Goals 3. Architecture Sample 3
4. Coordinator Pattern 4
5. Connecting View Controllers 1 let nc = window?.rootViewController as! UINavigationController let episodesVC = nc.viewControllers[0] as! EpisodesViewController let storyboard = UIStoryboard(name: "Main", bundle: nil) episodesVC.didSelect = { episode in let detailVC = storyboard.instantiateViewControllerWithIdentifier("Detail") as! DetailViewController detailVC.episode = episode nc.pushViewController(detailVC, animated: true) } • transition logics are outside of view controller 1 https://talk.objc.io/episodes/S01E05-connecting-view-controllers 5
6. Coordinator Pattern 2 3 • Objects to handle view controller transition = Coordinator • View Controllers can be isolated each other -> DI friendly • Other names: Router (in VIPER), Wireframe, Navigation, ... 3 https://speakerdeck.com/yoching/coordinatorpatanfalseshi-jian 2 https://speakerdeck.com/yoching/hua-mian-qian-yi-falseguan-li-tomvvm 6
7. More commonized way // in ViewController enum EpisodesRoute { case detail(Episode) } protocol EpisodesRouting: class { var routeSelected: ((EpisodesRoute) -> Void)? { get set } } class EpisodesViewController: UIViewController, EpisodesRouting { var routeSelected: ((EpisodesRoute) -> Void)? } // in Coordinator episodesVC.routeSelected = { route in switch route { case .detail(let episode): // present detail } } (inspired by "Deep Linking at Kickstarter" @ SwiftTalk 4) 4 https://talk.objc.io/episodes/S01E49-deep-linking-at-kickstarter 7
9. Coordinator Pattern problems • 2 tasks in Coordinator • view transition • view controller creation • lots of dependencies 9
10. Goals 10
11. Goals • All dependencies are injected from outside ɹ • Coordinator doesn't do view controller creation ɹ • Project is well organized ɹ 11
12. Goals • All dependencies are injected from outside -> Manual DI 5 • Coordinator doesn't do view controller creation -> using ViewFactory, CoordinatorFactory • Project is well organized -> Application / UI / Component 6 6 Minimizing Decision Fatigue to Improve Team Productivity @ try! swift 2017, https://www.slideshare.net/DerekLee/ minimizing-decision-fatigue-to-improve-team-productivity 5 https://ja.wikipedia.org/wiki/%E4%BE%9D%E5%AD%98%E6%80%A7%E3%81%AE%E6%B3%A8%E5%85%A5 12
13. Architecture Sample 13
14. Sample Code • yoching/iOSAppArchitectureSample 7 7 https://github.com/yoching/iOSAppArchitectureSample 14
15. Figure 15
16. Development Workflow situation workflow make service make service -> update Components make view make VC & VM -> make function at ViewFactory make transition update Coordinator 16
17. More Practical Sample • yoching/JSONPlaceholderViewer 8 • persistance using CoreData • networking • ReactiveSwift 8 https://github.com/yoching/JSONPlaceholderViewer 17
18. Discussions • Over engineered? • Dependency management objects = DI container? 18
19. Thank you! @yoshikuni_kato 19