This project was developed as a result of a code exercise.

Note: For a SwiftUI/Combine version, please see the project TopAlbumsSwiftUI.

Some of the features included in the design:

• MVVM design pattern
• Unit and UI testing (93% code coverage overall)
• Separate networking clients for albums, images with support for the URLSession dataTask method to be stubbed for testing.
• Dark mode support (special attention needed for store button border)
• Use of stack views, auto layout constraints

While this is a toy project and not a professional product, please be sure to demonstrate your ability to architect clean, maintainable and self-documenting code.

Create a sample iPhone app that displays the top 100 albums across all genres using the Apple RSS generator found here: https://rss.itunes.apple.com/en-us. We look for solid Swift fundamentals, like no force unwrapped or implicitly unwrapped optionals. Things like performance, testing, compatibility, version control and code quality are at the top of priorities.

The app should:

• Use Auto Layout
• Use proper threading use
• Display good architecture around parsing the API response into model objects to populate the UI
• Use modern Swift patterns

The app should NOT:

• Use storyboards or nibs
• Use any third-party libraries
• Use force unwrapped or implicitly unwrapped optionals

On launch, the user should see a UITableView showing one album per cell. Each cell should display the name of the album, the artist, and the album art (thumbnail image). Tapping on a cell should push another view controller onto the navigation stack where we see a larger image at the top of the screen and the same information that was shown on the cell, plus genre, release date, and copyright info below the image. A button should also be included on this second view that when tapped fast app switches to the album page in the iTunes store. The button should be centered horizontally and pinned 20 points from the bottom of the view and 20 points from the leading and trailing edges of the view. Unlike the first one, this “detail” view controller should NOT use a UITableView for layout.