[Yahoo Android] Review Project 4 - Twitter App Client Redux

[c11z]

@nesquena @timothy1ee

Hey guys finished with the twitter app redux. Took a little longer than expected, my app was way more complicated than the app you modified in the video, required some massive refactoring. In general everything is great, except switching between tabs causes to array adapter in the fragments to refresh, I tried persisting the fragments as class objects but that didn't help. Any suggestions?

Additional User Stories:

• User can switch between Timeline and Mention views using tabs.
• User can view their home timeline tweets.
• User can view the recent mentions of their username.
• User can click icon on Action Bar to view their profile
• User can see picture, tagline, # of followers, # of following, and tweets on their profile.
• User can click on the profile image in a tweet to see that user's profile.
• User sees progress dialog when tweets are loading

[nesquena]

:+1: Project looks good. A few notes:

• In the future, definitely consider additional polish for the UI by reviewing the cloning a screen tutorial and Q&A and the drawables guide.
• For tabs, try following this approach for cleaner tab listeners and better memory management.
• Nice use of tag to setup the ability to click the profile image and view a user's profile
• Nicely done architecting the fragments (base class and extension classes) such that you put as much code and logic as possible in the base class and then used abstract methods to define only the specific behavior where they differ!

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.

I tried persisting the fragments as class objects but that didn't help. Any suggestions?

Check out the tabs fragment strategy outlined above.