- What is the single responsibility principle? What's its purpose?
R: It tells us that an object/method should be delegated a single well-defined responsibility, to check that we are applying it we must be able to describe what an object/method does without having to use conjugations (and/or).
- In your opinion, what characteristics does a "good" code or clean code have?
R// A clean code must be flexible to changes, easy and comfortable to read, maintain and test. We can achieve it using meaningful names, SOLID principles, DRY, modularized architecture, design patterns.
This project require XCode 13.0, Swift 5.0 and should be run on device with iOS 15+ and then, you should run the app.
This project uses VIPER architecture, VIPER is an application of Clean Architecture to iOS apps. The word VIPER is a backronym for View, Interactor, Presenter, Entity, and Routing.
This architecture is conformed by 5 layers which have single responsibilities, which represent an opportunity to have a project decoupled, testable, and scalable.
Contains UI logic and knows how to layout and animate itself. It displays what it's told by the Presenter and it delegates user interaction actions to the Presenter.
The presenter layer is responsible to manage the communication between the View, Router and Interactor layers. Its main function is handle each visual request, retrieve information from interactor layer or, route the actual view to another one with the Router.
This layer is responsible to manage the communication between modules, its allows us changing between views and, initalize modules for each feature on the app.
Used for fetching data when requested by the Presenter, contains only business logic..
Contains only business logic, but primarily data, not rules.
- Clean code
- SOLID Principles
- DRY Principle
- Dependency Injection
- Modularized architecture
In this folder we have each app module. In this case we have a Home, and DetailMovie modules.
The main idea of this folder is have a transversal module which help us with reusables functions and components.
- Resources: Contains strings copies for the app.
- Base: Contains base classes for the modules, in this case only router base class.
- Extensions: Contains extra funcionalities to existing classes
- Models: Contains the entities bussiness for the project
- Services: This allows us to separate in a single context everything related to networking and web services.
- UI: Contains visual reusable components.
In this section we have the unit test structure, this folder meets the Viper architecture requirements. To continue, we can find a Test Double approach where we use Mocks, and Stubs doubles to test the differents architecture layers.
