Challenge Overview
INTRODUCTION
This is the first 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 login, menu and dashboard 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.
Login (Splash PSD group)
-- Use the REST framework and delegate to authenticate the user.
-- Replace the placeholder text of “Password” with “Pin” in the 2nd textbox.
-- After successful authentication use the REST framework and delegate to make calls to retrieve the consolidated data and personal p and cache locally (detail below)
-- After successful authentication take the user to the Settings screen (detail below)
-- Remove “Remember Me” and “Forgot Password” and DO NOT implement
Settings
-- On change of the ”Dietary Restrictions” switch, use the REST framework and delegate to update the user’s preferences
-- Create an arbitrary list of dietary restrictions as placeholders (this will be updated later)
-- Remove the “System” group and DO NOT implement any related functionality
Dashboard
-- Stub out functionality for loading the preferences (gear) and alerts (bell) screens.
-- Top left navigation icon should open the menu (below)
-- Stub out functionality for selecting all items in the list.
-- Display static information for the weather section.
-- Date countdown corresponds to the start of the briefing.
-- Remove “My List” and “Calendar” from the menu and DO NOT implement
Menu
-- Stub out method calls for all of the menu items.
-- “Sign Out” should remove the EBCKEY value from the keychain and direct users back to the Login screen
-- The current view controller in the stack should be highlighted red
-- Search functionality DOES NOT need to be implemented
-- Remove “My List” and “Calendar” from the menu and DO NOT implement
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 SamHouston1 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.