lvu5 / twittercodepath Goto Github PK

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, [email protected].

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, [email protected].

Looks like you are missing the README for this assignment. The README helps us to make sure we don't miss any required or optional stories you have completed.

Make sure you have completed the following steps to completing your README:

1. Make sure you have the correct README for this assignment, go to the "Setup" section in Assignment Tab for the corresponding week in the course portal.
2. Please mark all implemented stories with an [x]
3. Add a link to your animated gif walkthrough to your README and make sure it renders (animates) when viewing the README.

Once completed, please push your updates, mark off all completed stories in your README, add your project walkthrough gif and submit your assignment again so we can regrade it.

Still confused about how to properly submit your assignment? Check out the Submitting Coursework for detailed instructions.

Whenever you make updates to your project that require re-grading, you need to re-submit your project using the submit button on the associated assignment page in the course portal. This will flag your project as “updated” on our end and we know to re-grade.

You should re-submit your assignment anytime you:

• Update a previously incomplete assignment
• Add optional and additional features to an already completed assignment

It looks like your README is incomplete for this assignment. This is because of either of the following:

• You did not mark all implemented user stories with an [x].
• You did not have the correct README for this assignment. Go to the "Submitting your App Assignment" section in the Assignment Tab for the corresponding unit in the course portal.

The README helps us to make sure we don't miss any required or optional stories you have completed. For this submission, we've graded what we found on your GIF. You don't need to resolve and resubmit this project.

Moving forward, please make sure to follow the guide found on the Assignment Tab for the corresponding unit in the course portal.