TodoListViewController responsibility is to display the user interface as told by the presenter. We create a TodoListViewController object that subclass UITableViewController and implement the TodoListViewProtocol. TodoListModule Protocols Implement TodoListViewProtocol It communicates with other module/screen to be shown. Routing/Wireframe: Handle the navigation logic asked by the presenter object.Usually the interactor fetch the entity from a separate data store object. Entity: The model object that used by interactor.It also relay the user input from the view and fetch/update the data from interactor. Presenter: Fetch the data from the interactor and handle the logic of how the data will be displayed in view.Interactor: Process the business logic of the application, it communicates back and forth with the presenter.View: Shows the user interface told by the presenter, it also communicates back the user input to presenter.VIPER basic components are separated into 5 parts: Unit testing and Integration test becomes much more simpler because of the boundaries (protocol/interface) between each components. This makes the application becomes more modular and less coupled with other component. VIPER divides the app structure into components inside a module/screen with single responsibility principle. One of the architecture this article will approach is the VIPER architecture. ![]() The architecture we choose will shape on how the software will be built and scale as it grows. Deciding which application architecture to use when building an iOS application is one of the most challenging task, there are many architectures to choose from MVC, MVVM, MVP, View State, VIPER and many more.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |