[Intro to Swift] Project 1 - Review My App

[jejikenwogu]

My app is complete. Please review. /cc @codepathreview

[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 Objective-C or Swift. For example, in this project, we explored the following concepts:

• Code styling in Objective-C or Swift. You can find some code styling guides here:
  • The New York Times Objective-C Style Guide
  • 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.

Right now, the 5 Zynga seats are taken, but you're on the waitlist. We can put you on the list for the next class in May if you're interested.

The best thing that you can do to prepare for the class is to start thinking of app ideas that you're interested in building in groups of 3. For example, you can think of apps that streamline some process at Zynga or it can be something for fun for your coworkers. You can also build the next killer dating app or we'll also have some non-profit apps you can work on. Having an app in mind is the best way to explore the iOS framework in a very focused way. Note: This class is focused on designing RESTful clients, and we don't cover mobile game development.

You should also download and audit popular iOS apps like Pinterest, Uber, Tinder, etc. There's a designer app called capptivate that showcases mobile patterns in a bunch of other apps.

[jejikenwogu]

Hey Timothy. Thanks for reviewing my app. Yeah it's unfortunate that I couldn't enroll in this session of the class, but if there's space available in the May session I'd definitely love to join. Let me know if there's anything I need to do to make that happen. Thanks again.

On Thu, Jan 22, 2015 at 12:19 AM, Timothy Lee notifications@github.com wrote:

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 Objective-C or Swift. For example, in this project, we explored the following concepts:

• Code styling in Objective-C or Swift. You can find some code styling guides here:
  • The New York Times Objective-C Style Guide https://github.com/NYTimes/objective-c-style-guide
  • Ray Wenderlich Swift Style Guide https://github.com/raywenderlich/swift-style-guide
  • Github Swift Style Guide https://github.com/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.

Right now, the 5 Zynga seats are taken, but you're on the waitlist. We can put you on the list for the next class in May if you're interested.

The best thing that you can do to prepare for the class is to start thinking of app ideas that you're interested in building in groups of 3. For example, you can think of apps that streamline some process at Zynga or it can be something for fun for your coworkers. You can also build the next killer dating app or we'll also have some non-profit apps you can work on. Having an app in mind is the best way to explore the iOS framework in a very focused way. Note: This class is focused on designing RESTful clients, and we don't cover mobile game development.

You should also download and audit popular iOS apps like Pinterest, Uber, Tinder, etc. There's a designer app called capptivate that showcases mobile patterns in a bunch of other apps.

— Reply to this email directly or view it on GitHub https://github.com/jejikenwogu/TipCalculator/issues/1#issuecomment-70985662 .