iOS Architecture and Data Prefetching

Question

I've been looking for an elegant solution for some time without happiness.

I want to:

solve the massive viewcontroller problem that VIPER, MVVM, et al address,
always animate transition between fully rendered screens.

This feels like fighting the Apple frameworks; view controllers are in the drivers' seat of the navigation flow. I'm thinking to reverse that and do overall navigation in code, but the question is what kind of objects to create that own the view controllers, and when to instantiate. Activity indicators will be on the source scenes.

so far so good, what is your question? – luk2302 Dec 12 '15 at 19:40 — luk2302, Dec 12 '15 at 19:40
Has anyone seen a solid approach? – Jim Stead Dec 12 '15 at 19:46 — Jim Stead, Dec 12 '15 at 19:46

score 0 · Answer 1 · answered Apr 11 '17 at 02:29

Don't give up fighting against Apple MVC framework!

Use this Xcode plugin (https://github.com/natangr/ViperTemplate) to create and initiate VIPER files automatically.
Read this post for more advanced tips on VIPER instantiation (and explanation of above plugin): https://www.ckl.io/blog/best-practices-viper-architecture/

Having the module initialization code on its own Router will eliminate a bunch of code repetition, specially for huge projects. You need to create these extensions once:

// ReusableView.swift
protocol ReusableView: class {}

extension ReusableView {
    static var reuseIdentifier: String {
        return String(describing: self)
    }
}


// UIViewController.swift
extension UIViewController: ReusableView { }


// UIStoryboard.swift
extension UIStoryboard {
    func instantiateViewController() -> T where T: ReusableView {
        return instantiateViewController(withIdentifier: T.reuseIdentifier) as! T
    }
}

And then, leave initialization code on the router of each VIPER module:

// MainSearchRouter.swift
class MainSearchRouter {

    // MARK: Properties
    weak var view: UIViewController?

    // MARK: Static methods
    static func setupModule() -> MainSearchViewController {
        let viewController = UIStoryboard(name: MainSearchViewController.storyboardName, bundle: nil).instantiateViewController() as MainSearchViewController
        let presenter = MainSearchPresenter()
        let router = MainSearchRouter()
        let interactor = MainSearchInteractor()

        viewController.presenter =  presenter

        presenter.view = viewController
        presenter.router = router
        presenter.interactor = interactor

        router.view = viewController

        interactor.output = presenter

        return viewController
    }
}

It might seem like a lot of steps, but good news: the aforementioned plugin automates that as well!

iOS Architecture and Data Prefetching

1 Answers1