codepathreview
commented
3 years ago 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
Looks like you did not link your gif walkthrough for this assignment or it is not rendering (animating) properly when viewed in the README 😬. The gif helps us to make sure we don't miss any required or optional stories you have completed.
Render your gif: Once you have uploaded your gif to a site like imgur you can render it using the following syntax.
<img src="my_gif_address.gif", width=250 /> Make sure you have completed the following steps to completing your README:
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. Please mark all implemented stories [x] Add a link to your animated gif walkthrough to your README and make sure it renders (animates) when viewing the README. Your assignment is incomplete until the GIF is valid. Once resolved, please push your updates and submit your assignment again through the Course Portal (within 48 hours from the posted deadline) so we can regrade it. We will no longer review resubmissions made after this date.
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