What is the difference between Viper and MVC in iOS development?
The question is about VIPER
The difference between Viper and MVC in iOS development lies in their architecture and separation of concerns. MVC is a design pattern that separates an application into three major components: Model, which concerns the data; View, which involves the UI; and Controller, which involves the logic. This architecture is very much in use today on iOS; the problem is that it tends to result in the “massive view controllers” because Controllers tend to assume too much responsibility and handle most of the UI logic and data handling.
On the other hand, Viper represents a more modular architecture pattern that aims at improving code organization and testability by a better distribution of responsibilities. Viper stands for View, Interactor, Presenter, Entity, and Router, each responsible for a part of the functionality of an app. This, in turn, makes Viper more complex as compared to MVC but will keep components smaller, promote much better code reusability, and enhance testability. While the MVC is simpler and easier to implement, Viper fits a lot better in large projects where maintainability and scalability are an issue.
