[Lyft IOS Bootcamp] Review Assignment 1 – Tip Calculator App

[zskyfly]

Hi @codepathreview, the tip calculator is ready for your review!

[sumade]

Good work. This prework is a preview of our project process. Generally, 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.

Nice work adding your own touches to the tip calculator with the icon and the "add tip percentage" slider. That's the first time I've seen that feature. We generally find that students do very well in the class when they try to personalize the app with their own features.

One thing to think about for future work - In SettingsViewController.swift, you call ViewController().buildTipControl; this breaks the abstraction between view controllers. During the class next week, you'll learn about protocols and delegates as a cleaner way for passing data between view controllers.

Looking forward to working with you on monday!

[zskyfly]

Thanks for the feedback!
Yeah, I had a feeling that calling into ViewController().buildTipControl from SettingsViewController.swift was disrupting some peace in the universe, but I wasn't sure the correct approach to have view controllers share code, and I certainly didn't want to write WET code ;)