Twitter Client complete

[yatchoi]

Completed twitter assignment: @codepathreview

I didn't get to spend as much time on this as I'd have liked, and I lost a lot of time doing programmatic AutoLayout.

[nickai]

Nice work Yat! We designed this homework so that you can get 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.

A couple of notes after checking out your code / gif:

• Great to see tackle programmatic AutoLayout...this can get pretty tricky without the visual aid of Interface Builder!
• After the user selects a row in your tableView, you'll want to deselect that row inside of the didSelectRowAtIndexPath method. This will remove the selection when the user comes back to that screen.
• Make sure you are calling all the view controller lifecycle methods in your ContainerViewController. In particular, I don't see you calling didMovetoParentViewController anywhere.
• It's more common to use a property observer in your TweetCell for a tweet property that you use to configure all the views instead of having the populateWithTweet method.
• Nice to see you add new tweets to the list of tweets automatically without needing to pull to refresh!

You can also find our overall Twitter assignment feedback guide below:

• Each .xib file or Storyboard scene should have Auto Layout constraints specified for each view. There should be no yellow Auto Layout warnings, even if the layout seems to work. Auto Layout warnings are like having bad HTML. The browser will try to render it, and it might even look right, but it won't be fully predictable.
• Is your TweetsViewController generic enough that it can be reused to display tweets from other Twitter endpoints? A view controller that displays a list of tweets is the type of view controller that you want to make generic enough that it can be used in multiple places throughout an app. This particular TweetsViewController can come in handy for displaying the user's home timeline, but can also be reused for displaying a list of tweets that mention the particular user, showing another user's timeline, etc.
• Did you properly handle the conditionally present label "retweeted by..." in your custom TweetCell? You'll notice that for some tweets you'll need to display the "retweeted by..." label and have this hidden for other tweets. You'll want to create an outlet for a top margin AutoLayout constraint and programatically modify the constant depending on whether you want to show the label or not.
• Did you properly format the timestamp of each Tweet? You'll notice that in the actual Twitter app the timestamps for each tweet are presented in a friendly format (i.e. "10m", "1h", etc). Since this isn't how the timestamp is returned from the server, you'll need to do the conversion yourself. DateTools is a handy CocoaPod that does this for you.
• Did you handle reply/retweet/favorite actions from within the TweetCell? This is an example where it's useful for your model to be able to handle network actions, so you can simply wire up the buttons to a method like tweet.retweet(). You can even pass in an optional block if you want to handle a failure of the network event.
• In your ComposeViewController, did you pass back the Tweet after it was successfully created? This will allow you to locally insert newly created tweets so you don't have to do a network refresh to see the new tweets.
• Did you immediately update the retweet and favorite counts when a user retweets or favorites a tweet? It's common practice when building an app to have actions like favoriting a tweet assume success and ignore any failures. This gives the user an immediate response to his/her action without having to wait for a network response.
• Did you share code between your ProfileViewController and TimelineViewController? The ProfileViewController and the TimelineViewController both contain a feed of tweets. There are three general strategies: you can have a single view controller that conditionally has the profile header, you can create the ProfileViewController as a subclass of the TimelineViewController, or you can 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.
• Did you design the HamburgerViewController so that it can be reused in other apps? The HamburgerViewController should be designed to be agnostic to the Twitter app. In other words, have you designed it to be reusable in another application?
• Did you make sure to trigger the proper view controller lifecycle methods when adding or removing a child view controller to your container view controller? Make sure to review the Apple guide on Container View Controllers to ensure you've triggered the proper lifecycle methods. These lifecycle methods should be triggered for _both_ the ContentViewController and the MenuViewController.
• Have you implemented property observers for properties where appropriate? When setting the MenuViewController and ContentViewController in the HamburgerViewController, it's a good idea to use property observers to call the appropriate view controller lifecycle methods.
• Did you properly format numbers like the favorite count? In most apps you'll notice that large numbers will be formatted like "10.8M" instead of "10,800,000".