Lessons
Day 1
1Getting Ready to Build a Twitter App
14:29 2O'Auth Twitter Authentication and Q&A
22:19Day 2
3Introduction and Review of OAuth
05:09 4Becoming an OAuth Consumer
19:17 5Is the User Authenticated?
13:57 6Loading Twitter's Authentication Page
11:43Saving the Access Tokens
37:35Day 3
8Introduction to Loading Tweets and Threading
03:57 9Loading the Twitter Home Timeline
25:52 10Loading Newer Tweets
25:29 11Loading Older Tweets
11:55 12Loading on a Thread
27:19 13Showing the Status Detail View
15:09Day 4
14Introduction to Threads and Tweets
04:51 15Loading Avatars with Threads
13:52 16Loading Avatars with Async Task
35:49 17Loading Tweets with Async Tasks
14:57 18Navigating with a Menu
20:45 19Posting Tweets
15:18 20Wrap Up, Homework and Q&A
08:52Day 5
21Introduction to Skinning and Styling your Twitter App
07:17 22Creating a Theme with Colors and Fonts
30:58 23Styling Menus and Buttons
33:55 24Styling the Text Area and the List
24:53 25Styling for Different Screens
21:23Day 6
26Introduction to Posting your Photos to Twitter
07:03 27Getting Ready for Photos
20:22 28Attaching a Photo from the Library
30:27 29Attaching a Photo from the Camera
28:36 30Posting a Photo
17:11 31Recap of course and Q&A
05:27Lesson Info
Introduction to Threads and Tweets
welcome to Week three of creating a Twitter client with Android. What will be talking about today is background tasks. So we're kind of continuing on the theme that we ended up with last week, where we talked about the importance and the the ins and outs and the how twos of doing long running tasks work long running units of work in your code in the background or what? What? Ah, or more to the point off of the thread that is used that is called a U I thread, which is doing all of the display work and user interaction. The importance of taking those tasks off of the U. I thread is that it allows your application remain responsive, which is, um, which is like, It's one of those things. That's ah, if it's if it's there, then nobody really notices. But if it's gone, people notice really quickly, and it seems it seems like the APP is not trustworthy anymore. And people start to ask questions about how this thing works and why it's not working the way they want, even though it's doing what t...
hey asked. It's just like, um, slow and chunky, and then people start to lose trust, and that's not good. So to continue on with that theme, we're gonna talk about loading avatars for each tweet. Um, that shows up in the in the table view there, the list view. We're gonna load them on a thread, and then we're gonna talk about some of the some of the issues there with using threads for for more than one background task at a time. Up till now, what we've done is just load one thing in the background at a time. But this will be loading a couple things at once. And then we're talking about those issues. And then, well, then we'll introduce something called in a sink task, which helps us deal with some of the issues that will discover. And then we'll talk about, ah, changing reporting over some of the code we've already written to use a sink task. And then we'll talk about navigation inside of an android app between the different activities that are available using a menu and then at the end will push some new tweets. Of course, using an a sink task as well. So some of the new classes Ah, that will be introducing our highlighted here. We're gonna make they, uh um actually, authorization activity is not new. I'm not sure what the deal is there. Um, um I led that one, even though it's not new, but the menu helper below it is new. And then all of the classes inside of common Riley android a tweet tasks are new, and those of the a sink tasks will be creating today. Okay, so let's talk about threads and tweets. First. We'll talk about what the user is expecting of our application when they start to use it. Um, avatars air. Nice to have their kind of give a little personality teach tweet avatars also help the user, um, to kind of understand is they scroll through the list they're not gonna re reading. Nobody goes through and reads every tweet all the way through. I guarantee that's not the way that you actually use on application like this. You kind of scan through. And what helps you to pick out something that you may want to read is the avatar. Um hey, that's somebody that I want to hear from. Let me let me stop and take a look at that. It's also important that we have the avatars, um, not only for a little bit of style, but to let the user, um, scan through the information and pick out information that they want to consume a little more in depth. And then we're also going to allow navigation through the application so that we let the user go through and post a tweet and then move back to the home timeline or go toe to post again and to allow space for Mawr Mawr activities to be put into the application later. And then we will allow the user to post new tweets as we go through The code today will run into a few new characters in this drama of android development. Um, the a sink task we already talked about in depth a little bit. Ah, and is a pretty good an introduction. It's It's a way to, ah to deal with some unit of work in the background without using a thread. Um, and it also deals with, as I said, to come of a couple of the Thea problems of using more than one thread at us at the same time. Um and then we'll also deal with the menu, which is the way that navigation works on the android platform.
Ratings and Reviews
Student Work
Related Classes
Software