ale-long / twitter_ios

Twitter iOS clone (CodePath iOS Development Course)

Hi there 👋

About Me

Hi, nice to meet you! My name is Alex, a first-generation college student, and a sophomore studying computer science at UC Davis with interests in web development and software engineering. My passion lies in social good and leveraging technology to create an impact. Currently, I am a technical director at HackDavis, a hackathon focused on spearheading social good initiatives, in which I have developed the landing page site in a team of 4 using various technologies like React.js,Gatsby.js, and Firebase.

In order to further develop my passion for web development and social good, I am also currently developing Sub.ly, a full-stack web app that streamlines the apartment sub-leasing process for college students. My friends and I drew inspiration from the housing group pages on Facebook and realized how inefficient they can be as students are posting on top of each other. Information is easily lost and it can be a hassle for students to scroll through a plethora of posts in order to find the right apartment for them. Our goal is to make this process hassle-free and time-efficient so students can focus on more important matters at hand. Our tech stack consists of React.js, Firebase (authentication), MongoDB, Express.js, Node.js, and GraphQL.

I am always seeking opportunities to improve myself and further my knowledge in any way I can. My ability to accept and learn from constructive criticism has allowed me to thrive in a constantly changing environment, and I look forward to bringing that mentality into my future endeavors.

twitter_ios's Issues

Project Feedback!

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].