Challenge Overview
INTRODUCTION
This is the second 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 session listing, session detail and speaker screens.
REQUIREMENTS
You’ll be utilizing the PSD design in the repository branch you’ll be working with to build out the views defined below.
Session Listing (Agenda2 PSD group)
-- Call the consolidated data call on load and when user refreshes and cache locally (detail below)
-- Agenda tab data is populated in Briefings -> Sessions
-- Attendee tab data is populated in Briefings -> Attendees
-- Material tab should display an empty list for this iteration
-- Calendar tab data is populated in Briefings -> Sessions
-- Change “DAY ONE” to the value of the “Briefing_Date__c” field
-- Change bottom footer to contain “Briefing_Date__c” field value rather than today, tomorrow, etc.
Session Detail (Agenda2 Detail PSD group)
-- Detail displayed should be from the session selected in the Session Listing screen
-- “Add to Calendar” should add session information to the device’s calendar
-- “Stub functionality for showing a map of the floor plan; this is going to display a PDF so simply open a web viewer with a hardcoded PDF URL for now.
-- Time should include both “Start__c” and “End__c” time. E.g. “4:12PM - 5:00PM”
-- “BACK TO ATTENDEE LIST” should simply read “BACK”
Speaker (SpeakerDetail PSD group)
-- Detail displayed should be from the speaker selected on the Session Detail screen
-- Remove the “Awards” section
-- Use a placeholder image for the speaker profile picture
All Views (where applicable)
-- Stub out functionality for opening the menu (top left icon) and alerts (top right icon)
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
-- Store Ids for the following lists locally as a NSArray
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 against iOS SDK 8.0 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 SamHouston2 branch
-- Add lazybaer and harrywynn 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.