DexOfTheWild / codepath-ios-chirpy

iOS Twitter app for Codepath homework
0 stars 1 forks source link

Project Feedback! #1

Open codepathreview opened 6 years ago

codepathreview commented 6 years ago

:+1: nice work. With this assignment, we've now explored all the main patterns for building MVC clients! If this were 2009, you would be well on your way to building most apps that you could find in the app store. Over the next few weeks, we'll be focusing on custom views and view controllers to implement the interactions and visual effects that we find in more modern iOS apps.

We have a detailed Project 3 Feedback Guide which covers the best practices for implementing this assignment. Read through the feedback guide point-by-point to determine ways you might be able to improve your submission. You should consider going back and implementing these improvements as well. Keep in mind that one of the most important parts of iOS development is learning the correct patterns and conventions.

If you have any particular questions about the assignment or the feedback, feel free to reply here or email us at support@codepath.com

This was a very challenging assignment, congrats on completing it successfully!

codepathreview commented 6 years ago

:+1: 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. 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.

We have a detailed Project 4 Feedback Guide which covers the best practices for implementing this assignment. Read through the feedback guide point-by-point to determine ways you might be able to improve your submission. You should consider going back and implementing these improvements as well.

If you have any particular questions about the assignment or the feedback, email us at support@codepath.com.

A couple notes I had from reviewing the assignment:

We covered this briefly in class, but you ask about how navigation controllers should be set up in your notes. When using a container view controller (like a tab bar controller or hamburger view controller), it is common to have one navigation controller per “section” since each tab or section should be able to keep its own navigation stack.

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. /cc @codepathreview