Week3 Homework assignment : My Simple Tweets

[aaronucsd]

Completed Week3 Homework assignment : My Simple Tweets "/cc @codepathreview @codepath

-LongH

[codepathreview]

:+1: Congrats on completing the third project! Nice work overall. Try to implement as many optionals as you can to get most out of each week's assignment. If you didn't get time during week, you can always go back later at any time and try to implement what you can.

• Good to see you were able to format the timestamp cleanly
• Good to see you refreshed the timeline after composing a new tweet
• Consider adding progress bars to your app whenever a network request goes out
• Consider adding pull to refresh for the home timeline
• Consider better organizing your source files
• Consider adding ActiveAndroid to the Tweet and User. See the persistence guide and this other guide for more details.

I have provided a detailed Project 3 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 could improve your submission.

Let us know if you have any other thoughts or questions about this assignment. Hopefully by now you feel pretty comfortable with all the major pieces to basic Android apps (Views, Controllers, Models, Authentication, API Communication, Preferences, ActionBar, et al) and see how they all fit together.

[aaronucsd]

Completed Week4 Homework assignment : My Simple Tweets version 2 with fragments "/cc @codepathreview @codepath

-LongH

[codepathreview]

:+1: Project looks good. Good job finishing all required stories, I would suggest you to spend more time on styling the UI since that is the most challenging part of developing beautiful engaging apps.

• Good to see you properly communicated the user to the user timeline fragment from the profile activity.
• 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!
• Nice to see you used the ViewPager to properly setup the tabs!
• Consider adding progress bars to your app whenever a network request goes out
• In the future, definitely consider additional polish for the UI by reviewing the cloning a screen tutorial and Q&A and the drawables guide
• Try to implement more optional features so that you will get to play with more widgets and understand complexities involved

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.