prework for February iOS bootcamp

[hugohn]

@codepathreview @timothy1ee Hi Tim, this is my tip calculator app. Submitting the basic portion for now, I will be adding the optionals soon!

A little about myself: I'm a Codepath alum! Was part of the Android Sept 2014 cohort in San Francisco. My team's app for KIPP made it to the final demo day @ Yahoo, and I've been TA-ing a few times for the community evening/weekend sessions. I'm looking to transition into iOS dev at my workplace (Scribd) and would love to join this Feb class!

Thanks! ~Hugo

[hugohn]

@codepathreview update: completed all the optionals. Will continue tweaking to further customize/polish the UI and add more animations.

[timothy1ee]

Good work. This prework is a preview of our weekly project process. Generally, weekly projects take between 5-10 hours to complete the required features and an additional 5-10 hours to complete the optional features. In general, we've seen that the more hours you log, the quicker you improve your proficiency with iOS.

The purpose of this project was to begin to explore Xcode and to get a broad overview of iOS development using Swift. For example, in this project, we explored the following concepts:

• Code styling in Swift. You can find some code styling guides here:
  • Ray Wenderlich Swift Style Guide
  • Github Swift Style Guide
• Views are created in Storyboard, Interface Builder, or programatically, but they have the same goal: instantiate, initialize, and layout view objects. We use IBOutlets to give names to view objects, similar to giving unique ids to divs in HTML.
• We registered for touch events, which can be done programatically or via IBActions.
• We explored NSUserDefaults, one of the four persistence strategies in iOS.
• View controllers have a set of methods that are called when it loads, appears, or disappears. These are called view controller lifecycle methods.
• Do your views look good on iPhone 4, 5, and 6? Do your views look good on both iOS 6 vs iOS 7/8? We will cover in class how to use Auto Layout to robustly design your views for different screen sizes and OS versions.
• After this assignment, you should understand the purpose of IBOutlets and IBActions as well as the basics of designing views and programmatically interacting with the views from the controller.

I apologize for the delay in reviewing your submission. You'll receive an email in the next day or so if you will have a seat in the class.