Project Feedback!

[codepathreview]

👍 Nice work! The point of this homework was to get a chance to implement a TableView (one of the most common views in iOS) and to work with real data over the network (in this case from the Movies Database API).

A key part of these projects is that you add additional features and tweak the UI / UX because that will provide the most learning opportunities. We encourage you to complete the projects early each week with the required stories and then spend time adding your own UI elements and experimenting with optional extensions that will improve the user experience.

We have a detailed Assignment 1 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.

Check out the project rubric for a breakdown of how submissions are scored.

If you have any technical questions about the project or concepts covered this week, post a question on our Discussions Forum and mark the question as type, "Curiosity". For general questions email us at, support@codepath.org.

[codepathreview]

👍 Nice work! The point of this homework was to get familiar with two common forms of navigation in iOS (push and tab bar). It also provided a chance to extend your Flicks app in new ways.

We have a detailed Project 2 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.

Check out the assignment grading page for a breakdown of how submissions are scored.

If you have any technical questions about the project or concepts covered this week, post a question on our Discussions Forum and mark the question as type, "Curiosity". For general questions email us at, support@codepath.org. /cc @codepathreview

[codepathreview]

Nice work! This week, we continued to explore how to build apps that use an API (like Twitter). Unlike the movies app, we created a new class called TwitterAPICaller to help us interact with the API. We're also starting to introduce Auto Layout, which is how you make your app work for different phone sizes. Now that you've finished the app for the week, it's good to reflect on a few things:

• Manual segue for the login button. Remember that we couldn't create a segue directly from the login button because we have to check the user's credentials. If they enter the wrong password (or the login fails), you don't want to segue to the next screen.
• UserDefaults. We used UserDefaults to keep track of whether the user was logged in or not. If they were already logged in, we went directly to the tweets screen. UserDefaults is a great place to keep track of things you want to save locally, but not save on the server. For example, if you want to show a popup message one time only, you could use UserDefaults to keep track of whether you've shown the popup message already.
• TwitterAPICaller. Go back to the project and look through this file that we provided. There are some functions related to authentication that you can ignore. Twitter uses OAuth 1.0a for authentication, which is an old standard. Most new APIs will use something similar to OAuth 2. Other than the authentication functions, the class is pretty simple, and you can create something similar to interact with other APIs.

Check out the assignment grading page for a breakdown of how submissions are scored.

If you have any technical questions about the project or concepts covered this week, post a question on our Discussions Forum and mark the question as type, "Curiosity". For general questions email us at, support@codepath.org. /cc @codepathreview

[codepathreview]

Congratulations on finishing the Twitter assignment! Twitter is an example of a RESTful API, and they generally follow the same pattern. It might be interesting to look at other APIs like Yelp, Foursquare, Google, etc. In a company (or your own app), you'll probably be working with a private API, but it'll also be structured like the Twitter API.

• Read more about HTTP requests. The most relevant parts for now are understanding the difference between GET, POST, PUT, and DELETE, and understanding how HTTP caching works.

Check out the assignment grading page for a breakdown of how submissions are scored.

If you have any technical questions about the project or concepts covered this week, post a question on our Discussions Forum and mark the question as type, "Curiosity". For general questions email us at, support@codepath.org. /cc @codepathreview

[codepathreview]

Nice work! As we mentioned, the most common frameworks for backend web development are Node.js, Rails, Django, J2EE, and .NET. While the details of the frameworks vary, they all share similar structures. For prototypes, Parse and Firebase are great options for quickly getting a functional backend, and we prefer Parse because it's open source and more in your control. If you build your iOS using Parse initially, it's easy to move it to a Node/Rails/Django/etc backend later. Reflecting on this project, you should make you understand:

• User registration and authentication
• Creating objects
• Constructing a basic query

Check out the assignment grading page for a breakdown of how submissions are scored.

If you have any technical questions about the project or concepts covered this week, post a question on our Discussions Forum and mark the question as type, "Curiosity". For general questions email us at, support@codepath.org. /cc @codepathreview

[codepathreview]

Congrats on finishing the last individual project! Hopefully, you're beginning to see how you can assemble the things you've learned from the projects to build an app that you design yourself. Here are a few new concepts that we learned from this project that you should reflect on:

• Persisting the logged in user and logging out by programatically instantiating a view controller from the Storyboard and setting the window's root view controller.
• Working with sections and rows in a table view.
• Handling the selection of a row in a table view.
• Adding an array of related Parse objects (comments) to another Parse object (post).
• Integrating MessageInputBar, a custom input accessory.

Check out the assignment grading page for a breakdown of how submissions are scored.

From here on out there are no more assignments as the focus shifts to the final group project. You'll be working over the next several weeks to build your app idea with your team and then finishing the class with a demo day!

If you have any technical questions about the project or concepts covered this week, post a question on our Discussions Forum and mark the question as type, "Curiosity". For general questions email us at, support@codepath.org. /cc @codepathreview