1st Submission

[jain150]

Currently working on added functionality. Please review /cc @codepathreview

[chieger]

This is a great submission Arnav!

In order to even further increase your chances of acceptance and familiarize yourself further with the language, we encourage you take a stab at additional optionals. You can just submit a new Github issue when you’re done and add /cc @codepathreview. No need to refill the pre-work form

This pre-work is a preview of our weekly project process. Generally, weekly projects take about 5 hours to complete the required features and an additional 5 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 programmatically, 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 programmatically 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? 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.

Acceptance emails will be sent out during the first week of January.

Charlie Hieger CodePath

[codepathreview]

Hello Arnav.

Looks good, this exercise is intended in part to give you an introduction to the general rhythm of this course. The course is entirely project-based with an app being assigned each week and then due the following week. Each project builds on the last to help each engineer learn the practical elements of iOS development and best practices as quickly as possible. We also do a code review for each submitted project once the program begins.

Great to see you were able to complete some optional features to your app already. The optional tasks available on each project are often the most valuable learnings since they dive deeper into common real-world iOS use cases. We encourage you to continue working on extensions to your tip calculator as a way to further explore iOS development.

See if you can expand the functionality of the app or instead work to improve the user interface by experimenting with colors, spacing, styling, icons, etc. You can update your submission at any time here, and it will notify us to review again.

We'll be following up with you again shortly to outline the next steps in the admissions process.