This is a basic app that consumes photo data from the jsonplaceholder API and displays it in a collection view.
These instructions will get you a copy of the project up and running on your local machine for development and testing purposes.
What things you need to install the software and how to install them
- SDWebImage - Asynchronous image downloader with cache support as a UIImageView category
- Lottie - An iOS library to natively render After Effects vector animations
- DZNEmptyDataSet - A drop-in UITableView/UICollectionView superclass category for showing empty datasets whenever the view has no content to display
To run the project, navigate to the project directory where project is stored and install the pods associated with this project
Type in following command at command line
pod install
Once this is complete be sure to use project file ending in xcworkspace
Use the following command in the terminal to execute the Unit Tests from within Xcode
cmd + u
The project has 2 major view controllers. PhotoVC is the first screen users land on after launching the app. This contains a collection of all of the photos download from the JSONPlacehoder endpoint.
PhotoDetailVC is the screen that users land on after selecting one of the photos from the first screen.
This project uses the MVC-N design pattern.
The network layer uses a class called APIRequestLoader to make requests to the JSONPlacholder API to get data.
To create a new request, conform to the APIRequest protocol
protocol APIRequest {
associatedtype ResponseDataType
func makeRequest() throws -> URLRequest
func parseResponse(data: Data) throws -> ResponseDataType
}
Use the makeRequest method to build your url via URLComponents. From here you use the parseResponse(data:Data) method to parse the response coming back. See the example below of the PhotoRequest that we use to downloads the photos used in this project
struct PhotoRequest: APIRequest {
func makeRequest() throws -> URLRequest {
let components = URLComponents(string: "http://jsonplaceholder.typicode.com/photos/")!
return URLRequest(url: components.url!)
}
func parseResponse(data: Data) throws -> [Photo] {
return try JSONDecoder().decode([Photo].self, from: data)
}
}
The MockURLProtocol serves as a way for us to mock the response coming back from the server during our testing. This allows us to go through the motion of making an actual request but work with the same consistent data when processing that request.
A majority of the views are built using StoryBoards. There is 1 custom CollectionViewCell called PhotoCell. It's only subview is an UIImageView that is used to display the photos coming back from the API request.
The model consist of a Decodable Struct called Photo.
The JSON coming back from API request looks like this:
[
{
"albumId": 1,
"id": 1,
"title": "accusamus beatae ad facilis cum similique qui sunt",
"url": "https://via.placeholder.com/600/92c952",
"thumbnailUrl": "https://via.placeholder.com/150/92c952"
}
]
The values for the albumId and id are decoded as Int, the title as String and the url and thumbnailUrl as URL.
- Marc Aupont - Initial work - digimarktech
This project is licensed under the MIT License
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.