Final Submission for CodePath Challenge

[jottamenezes]

Hey guys, my app is done. I'm gonna try to add some UI animations to make it fancy, but the main features are there for you to watch! /cc @codepathreview

[chieger]

This is a very well done submission Jean! I really like the logo too!

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

[jottamenezes]

Hey Charlie, thanks for the feedback. I'll not lie to you. In the beginning it was greek to me, i had to watch the video tutorial twice to have enough courage to open xcode, and after that every little line of code, every little label put in, every simulation has been a challenge. I know that you might have noticed but my submission is called "smartip 5", that was not for stylization of the brand. That represents every time i had to start it from scratch, because i've faced a wall i couldn't trespass.

I'll continue not lying by saying that i'm not sure if i'm ready for what you guys are proposing, the first time i've ever opened any programming GUI was in july, this year.. What i'm sure is that it is going to be challenging and it is going to be rewarding, according to the mono-myth that's all you need for a good journey!

Thanks for the tips, the review and the feedback. Looking forward to hear from you, have a happy new year!

2015-12-29 18:20 GMT-08:00 Charlie Hieger notifications@github.com:

This is a very well done submission Jean! I really like the logo too!

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 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 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

— Reply to this email directly or view it on GitHub https://github.com/Jaymenezes/smarTips_5/issues/1#issuecomment-167919800 .

Jay Menezes Graphic Designer/ Illustrator

jaymenezes.com http://jaymenezes.com