Twitter app with Fragments (Hw #4 submission)

[monachitnis]

@nesquena

Thanks for allowing to submit a day later. Faced some issues this time with infinite scroll this time even though it had worked the last time. Also didn't get enough time for too many optionals

[nesquena]

Glad you were able to complete in time. What was the issue you ran into to infinite scroll? Let me know if there's anything I can add to helpful hints. Hope you can get some time to go back and do a few optionals and stylize the UI. Make sure to focus on this key aspect for your group project as well.

👍 Project looks good. I have provided a detailed Project 4 Feedback Guide here which covers the most common issues with this submitted project. Read through the feedback guide point-by-point to determine how you might be able to improve your submission.

Let us know if you have any other thoughts or questions about this assignment. Hopefully you can see this coming together as a "fully fledged" twitter client with some more work and polish. This app contains all of the components now (fragments, models, networking, client, tab navigation, image loading, et al) of 90% of dynamic data-driven API client. Obviously there are lots of details and patterns to learn, but by this point you have been introduced to all the major frameworks and concepts. Hopefully you would feel fairly confident getting started making Android apps for instagram, pinterest, yardsale, flickr, using the same patterns.

[monachitnis]

Since there are two fragments Home and Mentions, I am using 2 sets of variables for each, marking the max_id and since_id of tweets. Now each time a set of tweets is fetched from the client, I set max_id and since_id accordingly. However I am seeing (in debug logs) the max_id set to a low value (in hundreds) when actually the tweet ids are in order of millions. On refresh the client just fetches based on count (max_id set to 0), and gets the latest tweets, but in the onLoadMore() using a combination of max_id and since_id, something is not right there.

I think I was right in using two sets of pointers here, one for each fragment since ids for both are separate. But i'm not sure if they are interfering with each other somehow. Also wasnt sure how to abstract away the populateTimeline() method in base fragment itself (quite a bit of duplication in the derived fragment code)

[monachitnis]

again thanks for your time and I will try and resolve this conceptual confusion about twitter timelines in a couple of days.