[Intro to iOS] Project 4 - Twitter redux

[jonchoi]

/cc @codepathreview

Hey guys – As always, I wish I had ten more hours. I probably spent ten hours on the ray wenderlich custom hamburger menu guide, which I should have been able to implement quicker... However, this exercise gave me a much stronger understanding of last weeks assignments and how view controllers work in general. If I had more time, I would try and make the segues cleaner and more consistent, and would take some time to take a crack at the additional log in and animation in the profile page (which is set up but not implemented yet).

I still have so much to improve, and I'll need to refactor the code at some point. Thank you again for your guidance :)

Jon

[codepathreview]

Nice work! We added this homework so that you'll have the experience building an app that's more similar in complexity to a production app. It's also useful to have practical experience building a container view controller, which is a more advanced topic. The optional account switching feature is interesting because you have to think about how TwitterClient is caching the access token to make sure it works correctly for multiple accounts. Displaying the account switching screen is implemented using custom view controller transitions.

A few notes after checking out the code:

• You should declare all unnecessarily public properties as private for better encapsulation.
• Nice work specifying the Auto Layout constraints.
• Consider refactoring the profile view controller so that it shares code with the TimelineViewController. There are two general strategies: you can subclass the TimelineViewController or create a separate class called a TimelineController (not a view controller). TimelineController is a dataSource and a delegate to a UITableView and knows how to show a feed of tweets.
• Nice work encapsulating the properties of the custom cells that you added.
• You should consider what a more generic design for your hamburger controller might look like. Right now, it's tightly bound to this Twitter application.
• You should consider implementing the blurred table view header. There are several approaches here that are all valid. You can implement the header has a table header, a section header, or a cell. My preferred approach is to implement it as a table header, it's the easiest way to flow the image above the content. These detail touches are where you really learn the nooks and crannies of the framework.

Congratulations on finishing the final assignment! It's impressive to realize that in just four weeks, you've gone from building a simple tip calculator app to a polished MVC client.