/mobile-challenge-1

Small mobile coding challenge for prospective applicants

Primary LanguageSwift

CodingChallenge

Features

  • Grid of photos should preserve the aspect ratio of the photos it's displaying.
  • Grid should work in both portrait and landscape orientations of the device.
  • Grid should support pagination, i.e. you can scroll on grid of photos infinitely.Feature 3
  • When user taps on a photo on the grid she should show the photo in full screen with more information about the photo.
  • When user swipes on a photo in full screen, preserve it's location on the grid, so when she dismisses the full screen, grid of photos should contain the last photo she saw.

Requirements

  • iOS 10.0+
  • Xcode 9.3

Installation

CocoaPods

You need to install cocoaPod inorder add alamofire:

pod init

Meta

Siddhesh Mahadeshwar – siddheshm1212@gmail.com

Mobile Developer Coding Challenge

This is a coding challenge for prospective mobile developer applicants applying through https://about.500px.com/jobs/

Goal:

Develop a simple app that allows viewing and interacting with a grid of currently popular 500px photos

  • Fork this repo. Keep it public until we have been able to review it.
  • Android: Java | iOS: Swift 3
  • 500px API docs are here: https://github.com/500px/api-documentation. Please don't use deprecated iOS and Android SDKs.
  • Grid of photos should preserve the aspect ratio of the photos it's displaying. Optionally: exclude nude images.
  • Grid should work in both portrait and landscape orientations of the device.
  • Grid should support pagination, i.e. you can scroll on grid of photos infinitely.
  • When user taps on a photo on the grid she should show the photo in full screen with more information about the photo.
  • When user swipes on a photo in full screen, preserve it's location on the grid, so when she dismisses the full screen, grid of photos should contain the last photo she saw.

Evaluation:

  • Solution compiles. If there are necessary steps required to get it to compile, those should be covered in README.md.
  • No crashes, bugs, compiler warnings
  • App operates as intended
  • Conforms to SOLID principles
  • Code is easily understood and communicative
  • Commit history is consistent, easy to follow and understand