Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Clean Architecture - VIPER

Sergi Gracia
November 13, 2014

Clean Architecture - VIPER

The Redbooth iOS Team is adopting a new architecture: VIPER. We explain what's viper and our experience with it (demo included).

Sergi Gracia

November 13, 2014

Transcript

97 slides
  1. WELCOME TO REDBOOTH (there are ! and snacks, find them!)

    TWEET ABOUT THE TALK WITH THE #VIPERTALK HASHTAG
  2. 4

  3. 20

  4. 35

  5. 13

  6. A VIEW CONTROLLER COORDINATES ITS EFFORTS WITH MODEL OBJECTS AND

    OTHER CONTROLLER OBJECTS—INCLUDING OTHER VIEW CONTROLLERS — Apple
  7. ▸ ViewControllerDelegator @interface TBThreadDetailViewController : RBViewController <UITableViewDataSource, UITableViewDelegate, RBViewControllerURLProtocol, NSFetchedResultsControllerDelegate,

    TBObjectDetailHeaderCellDelegate, TBUploadCellDelegate,TBWatchersViewDelegate> ! ▸ Multi Responsibility [self presentViewController:previewController animated:YES completion:nil]; //Navigation [Task downloadNewObjectWithID:self.threadIdentifier.remoteIdentifier withSuccess:^{}]; // Networking NSFetchRequest *request = [[NSFetchRequest alloc] initWithEntityName:[Comment entityName]]; // Data persistence [self.view setBackgroundColor:ss_Color_White]; // Formatting !
  8. ▸ Monster files size > 1500 lines ! ▸ Impossible

    to test " ▸ Components too coupled #
  9. ▸ Monster files size > 1500 lines ! ▸ Impossible

    to test " ▸ Components too coupled # ▸ Hard to understand (and review) classes. $ %&'()*+,
  10. ▸ Who will persist the data? ▸ And the API

    interaction? ▸ Who controls the navigation?
  11. VIEW ▸ Shows the content received from the presenter ▸

    Notifies user's actions to the presenter ▸ The presenter doesn't know anything about UI
  12. PRESENTER ▸ Includes the logic to format the view ▸

    Gets the data from the interactor ▸ Receives actions from the view and traduces them into: Navigation actions (wireframe) and Interactor requests
  13. INTERACTOR ▸ Associated to an unique use case of the

    application ▸ Works with PONSO entities ▸ Coordinates both data managers
  14. DATAMANAGER ▸ Provider of entities for the Interactor ▸ Responsible

    of the persistence (Web and Local) ▸ The entities don't know about how to persist themselves
  15. WIREFRAME ▸ Initializes the VIPER module ▸ It knows how

    to navigate ▸ Delegate of transitions animations
  16. STRONG/WEAK BE CAREFUL WITH RETAIN CYCLES ➿ @interface TweetDetailViewController: UIViewController

    @property (nonatomic, strong) id <TweetDetailPresenterInput> presenter; @end @interface TweetDetailPresenter: NSObject<TweetDetailPresenterInput> @property (nonatomic, weak) id <TweetDetailViewInput> view; @end @implementation TweetDetailPresenter - (void)sendTweet:(NSString*)tweet { __weak typeof(self) welf = self; [self.view showLoader]; [self.interactor sendTweetWithCompletion:^(NSError *error) { [welf.view hideLoader]; if (!error) [welf.wireframe moveBack]; }]; } @end
  17. ENTITIES DON'T PASS NSMANAGEDOBJECTS! USE PONSOS INSTEAD @interface TweetEntity: NSObject

    @property (nonatomic, strong) NSString *body; @property (nonatomic, strong) NSString *authorName; @property (nonatomic, strong) NSDate *creationDate; + (TweetEntity*)tweetEntityFromTweet:(Tweet*)tweet; @end
  18. TWITTER APP Login and Home views WRITTEN 100% IN SWIFT

    GITHUB.COM/PEPIBUMUR/VIPER-MODULE-GENERATOR HANEKE, SUGARRECORD, SWIFTER, PURELAYOUT, PROGRESSHUD
  19. ▸ The VIPER module is initialized and presented by the

    Wireframe ▸ The view notifies that DidLoad to the Presenter override func viewDidLoad() { self.setupSubviews() self.setupConstraints() self.setNeedsStatusBarAppearanceUpdate() self.presenter?.viewDidLoad() }
  20. ▸ The Presenter formats the View's content func viewDidLoad() {

    self.view?.setLoginTitle("Login Twitter") self.view?.setLogo(UIImage(named: "twitter_logo")!) }
  21. When the user taps on Login ▸ The View notifies

    the Presenter func userDidSelectLogin(sender: AnyObject) { self.presenter?.userDidSelectLogin() }
  22. The Presenter: ▸ Tells the View to show a loader

    ▸ Asks the Interactor for Login func userDidSelectLogin() { self.view?.showLoader() self.interactor?.login() { [weak self] (error: NSError?) -> () in if error != nil { // What should we do here? } else { self?.view?.hideLoader() // And here? } } }
  23. The Interactor: ▸ Login the user through the APIDataManager ▸

    Persists the user's credentials using the LocalDataManager
  24. func login(completion: (error: NSError?) -> ()) { self.APIDataManager?.login({ [weak self]

    (error: NSError?, credentials: TwitterLoginItem?) -> () in if (credentials != nil) { self?.localDatamanager?.persistUserCredentials(credentials: credentials!) completion(error: nil) } else { completion(error: error) } }) }
  25. APIDATAMANAGER func login(completion: (error: NSError?, loginItem: TwitterLoginItem?) -> ()) {

    TwitterClient.requestAccesss { (error, credentials) -> () in if credentials != nil { completion(error: nil, loginItem: TwitterLoginItem(swifterCredentials: credentials!)) } else { completion(error: error, loginItem: nil) } } }
  26. If the login fails ▸ The Presenter asks the View

    to show an error func showError(let errorMessage: String) { ProgressHUD.showError(errorMessage) } If the login success ▸ The Presenter asks the Wireframe to show the home view
  27. SOME CONCLUSIONS ▸ Lighter, more specific and readable classes ▸

    Each team member can be working on a different component once the interfaces are defined ▸ There're no excuses for TDD !
  28. TIPS ▸ Heavy work but you and you'll team will

    thank it ▸ Keep in mind the SOLID principles ▸ Refactor your components through iterations ▸ Decouple your code from the database models and data layers
  29. RESOURCES ▸ VIPER Module Generator ▸ Objc.io post ▸ Mutual

    Mobile Engineering blog post ▸ Dobuts/Ideas/Suggestions on Github issues

More Decks by Sergi Gracia

Other Decks in Programming