HotelsGuideApp

Application Architecture Diagram

this app contains:-

• Data Managment Layer

  this layer is isolated from the applecation logic and data types
  • Cache Backed Data Store
    this fremework provide protocoles lo manage the data fetching and caching process
  • Networking Layer
    this framework provide the code require to request the data over the internet
  • Request Builder
    this framework builds the request for us and the framework build with Builder Design Pattern

• Application Data Layer

  this layer is build over the previous one to translate the protocols and logic to be used with our app logic and data types
  • Image Cache Back Data Store
    this framework implements the under layers Cache Backend Data Store his duty is to fetch images and cache it and retrieve it when it needed again
  • Hotels Fetcher
    fetch hotels from internet using the endpoint enum

• application layer (View Controllers)

  this layers contains the view controllers and feed with data from the previous layer

Application Pros

• testable

  I used protocols to build each struct and class which means the code is highly testable and I started the implementation using TDD and for the sake of time I started to implement without testing The first layer is almost all tested

• Maintainability

  the code is consist of layers each layer is independent from the other and can be easily modified or replaced

• the use of continuous integration

  in this app i am using travis ci to automate testing

• Simplicity

  the app made using MVC architecture I used this architecture because it is a simple one and I used to use it and prevent his weaknesses for example (the massive view controller)

• Grid Layout

  the app shows the list of hotels as a grid layout uicollectionview (bonus) each cell determines its size based on the image size

Aplication Cons

• UI Design

  i am not a very good designer but i can easily implement any design with the best possible efficiency

Note: i used a lot of ways implementing this app to show you that i can follow any way that the team use (interface Builder or programmerly)

Refrences:

https://www.donnywals.com/building-flexible-components-with-generics-and-protocols/

https://www.donnywals.com/architecting-a-robust-networking-layer-with-protocols/

https://medium.com/flawless-app-stories/building-urlrequests-with-ease-f0136cdd56c3

https://blog.usejournal.com/building-a-safe-modularized-and-well-structured-networking-layer-in-swift-4-2-de264d079ce2

https://medium.com/flawless-app-stories/reusable-image-cache-in-swift-9b90eb338e8d

https://www.raywenderlich.com/4829472-uicollectionview-custom-layout-tutorial-pinterest