Solstice code challenge for recruiting at iOS positions. You can find the requirements of this exercise in the pdf placed at the root of the repo.

Some frameworks were included in this project in order to speed up the process:

• Cocoapods
• Alamofire
• AlamofireImage

Instalation process is straight forward: first install Cocoapods using the terminal by executing:

$ sudo gem install cocoapods

After the project has been cloned, proceed to open a terminal on the root folder and run

$ pod install

And that's it. Everything should run smoothly.

• MVVM and SOLID were at the heart of this development, always favoring composition over inherence (that's why you can see so many files for such a "small" project). It was lego oriented design 😁
• Little example of how the first view behaves (Mermaid is required In order to properly show it)

sequenceDiagram
Note left of ListViewController: This class reacts to<br/>events and renders<br/> accordingly. ONLY<br/>that

ListViewController ->> NetworkLayer: Hey, got some data for me?
NetworkLayer -->> ListViewController: Here you go
ListViewController ->> ContactsDataSource: Here's the data. Please render it
ContactsDataSource --> UserViewModel: Time to work guys!

• Cache policy is simple: if the response is successful store it, otherwise use placeholder image from now on.
• Use of StackViews wherever possible to laverage its flexibility and layout power.

There were tradeoffs in every major design decision behind the development. While it is true that SOLID principles are at the core of every choice made here, no peace of software is ever complete so there might be minor duplicated here and there for speeding sake. Some notes can be found across the project explaining the shortcomings of those implementations.

You might find odd for me to include this section since it looks like I'm sabotaging myself. The intention here is to acknowledge the things that, most likely due to lack of time, remain pending. Just to mention a few:

• Implement coordinators instead of instantiating and pushing details view controllers from main list controller.
• Add unit testing
• Remove minor duplications on image network calls and cell dequeuing
• Abstract hardcoded strings into plist or centralized struct for instance.

Hope I made myself clear in all of my intents. Looking forward to any feedback!

Regards.