Register
Submit a solution
The challenge is finished.

Challenge Overview

INTRODUCTION
This is the fourth in a series of challenges to incorporate design with the framework built out in Jim Bowie.  This challenge will focus on building the UI for the travel information screens.

REQUIREMENTS
You’ll be utilizing the PSD design (mobile.psd) in the repository branch you’ll be working with to build out the views defined below.  All views will be found in the “Travel Info” PSD group.

All Views (where applicable)
-- Call the consolidated data call on load and when user refreshes and cache locally (detail below)
-- Data for display is contained in the Attendee -> TravelInfo object
-- Stub out functionality for opening the menu (top left icon), alerts (top right icon) and search

Flight Info
-- Record type = “Flight”
-- Remove and DO NOT implement: “boarding now”/”gate closing” section, “terminal”, “gate”, “meal”, the barcode and “Share” in the bottom menu
-- Add to the view: “Flight Notes” text field in place of the barcode

Hotel Info
-- Record type = “Hotel”
-- Remove and DO NOT implement: “check in” line, “length of stay” info, “Share” in the bottom menu
-- Add to the view:
     
-- the hotel address in place of “check in”
     
-- “Hotel Notes” text field at the bottom of the screen
     
-- A map of the hotel’s location in place of the photo
-- Show the user’s location on the map
-- Use the pin from the Ground Info view to show the hotel’s location

Ground Info
-- Record type = “Logistics”
-- Remove and DO NOT implement “Share” in the bottom menu
-- Add to the view: the confirmation number and location below the “Reserved at” line
-- Rename the “Ground” tab to “Logistics”
-- Show the user’s location on the map

Data (where applicable)
-- Cache copies of the API JSON responses locally for offline access
-- Update the cached copies when the app becomes active
-- Use these cached copies for displaying data in the UI



Final Submission Guidelines

SUBMISSION GUIDELINES
-- All code should be written in Swift and be well commented
-- Use the workspace setup in the repository for development
-- Code must compile in Xcode 6.1 against iOS SDK 8.1 with a deployment target of iOS 7.0
-- Use auto layout and size classes to fit all classes of iPhone device (4”, 4.7” and 5” screens)
-- Use storyboards for all views and navigation
-- Only portrait orientation needs to be supported
-- Upload your source project as a zip
-- Include your gitlab username and URL of your forked repository in your documentation
-- Provide a video overview of your submission

SETUP
-- Send an email to lazybaer or harrywynn and request to be added to the Project Alamo team on gitlab if you are not already a member
-- Once added to the team, fork the repository if you haven’t already and work off of the SamHouston4 branch
-- Add harrywynn and lazybaer as members of your forked repository.
-- Send an email to lazybaer or harrywynn for an API user email and PIN to request authorization if you do not already have one. Include your Topcoder user name in the request.

ELIGIBLE EVENTS:

2015 topcoder Open

Review style

Final Review

Community Review Board

Approval

User Sign-Off

ID: 30046676