Submission

[aphexcx]

@nesquena @timothy1ee

Here are the required user stories before the required submission deadline. I will implement more optional user stories as I complete them.

Primary user stories took me 8-10 hours to complete. Gotchas I ran into:

• Relative time display (Spent 3+ hours on this and got the basic requirement working, but could not get the third party library, prettytime, to display times in the format of "13m" rather than "13 minutes ago" which is more succinct and matches the current twitter app)
• Getting the current logged in user with the verify_credentials endpoint
• Trimming the extra tweet returned to the EndlessScrollListener

Extra stuff I threw in (as of now):

• I set a hierarchical parent for the compose activity, so it has a "<" symbol to go back on the action bar rather than having to implement a Cancel button
• I scoured the internet and extracted the little twitter compose button with photoshop and converted it to the right sizes
• I modified the profile images returned to be high quality rather than normal quality
• Auto-expand images in tweets and rewrite the tweet body to remove the image url (like in the real client!)

More to come!

[nesquena]

:+1: nice work overall Afik. Definitely appreciate the little touches you added! A few notes after checking out the code:

• Good to see you were able to format the timestamp cleanly
• Consider adding pull to refresh for the home timeline as explained in the cliffnotes page
• Good to see you added the tweet to the home timeline after you posted new on compose
• Nice touch with the character count being calculated for Compose
• Consider adding ActiveAndroid to the Tweet and User. See the persistence guide and this other guide for more details.

Here's 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, ActionBar, Navigation, Models, Authentication, API Communication, Persistence, et al) and see how they all fit together. We are close now to a turning point in the course where you should be hitting a "critical mass" towards your knowledge of Android.

[aphexcx]

Thanks for the feedback! I really do feel more and more powerful with each assignment.

I just added pull to refresh and fixed a nasty bug I noticed with the endless scroller caused by not encapsulating the tweet loading functionality into a single function. Would love your feedback on that and if there's anything else I can improve.

[nesquena]

Thanks for the feedback! I really do feel more and more powerful with each assignment.

Yep, the next should be fairly satisfying as we are going to push this twitter client to the next level and learn about how to use fragments properly.

I just added pull to refresh and fixed a nasty bug I noticed with the endless scroller caused by not encapsulating the tweet loading functionality into a single function. Would love your feedback on that and if there's anything else I can improve.

Ah yeah, I'm glad you fixed that issue with endless scroll! And great to see you were able to use that library for the refresh. Your twitter client is coming together.

[aphexcx]

I've just committed the rough first iteration of the required user stories for phase 2! I have to step out for dinner, but I'll be back on later tonight to finish up more optional user stories. I'll post updates as i do! @nesquena

[nesquena]

:+1: nice work overall although definitely bare as you mentioned. A few notes after checking out the code:

• Nice to see you were able to do some basic skinning with styles
• Consider adding progress bars to your app whenever a network request goes out
• For tabs, try following this approach for cleaner tab listeners and better memory management.
• Good to see you properly communicated the user to the user timeline fragment from the profile activity.
• For a future exercise, challenge yourself to move even more of the logic into the base Fragment class and out of the extension timeline fragments. For example, the scroll listener could be set in the base class and then the "onLoadMore" could call an abstract method which is defined separately in the extended class. This approach could be used to move almost all the logic into the base except for certain key abstract methods.
• Consider adding local persistence of tweets by using ActiveAndroid in the Tweet and User. See the persistence guide and this other guide for more details.

Here's 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.

This week (Week 5), we are going to cover the last major piece to the Android puzzle and that is using the hardware and SDK components such as the camera, photo gallery, location, maps, etc. After that, Week 6 and week 7 we will be covering a few important intermediate topics such as more about styling and animation as well as testing.

Following the bootcamp (May 12th), we are going to have a demo day to celebrate the progress you've all made with our next batch of Android students and multiple companies attending to see the group projects that you all have built. We are going to help however we can over the next few weeks to get the team project apps in shape for that.