Simple Twitter Client v1.0 finished

[mttlee0]

Twitter Client is finished.

No infinite scroll or load more tweets button, but all other requirements are satisfied. For persisted data I used SharedPreferences instead of SQLLite for offline support.

/cc @nesquena @timothy1ee

[nesquena]

👍 Looks good Matt, a few points of feedback:

• Properly leveraged RestClientTemplate and configured TwitterClient to authenticate and send requests to API
• Leveraged UniversalImageLoader to load all remote images
• Setup login with OAuthLoginActivity and handled onLoginSuccess
• Properly setup Tweet and User models extracting relevant data from JSON
• final constants should typically be all capitalized
• Properly setup home timeline request through TwitterClient and tweets are displayed in timeline ListView
• Handled failure cases where there's no network connectivity
• Did not use ActiveAndroid but used SharedPreferences to persist latest successful tweets result
• Setup compose window, displaying relevant information and properly posting tweet
• Setup character counter for compose window (limited to 140 characters)
• Reloaded home timeline to display the tweet after tweet was submitted
• Didn't add pagination, you might want to check out our guide on endless scrolling.
• Should consider playing around with ActiveAndroid to get a feel for ORM usage with Android

To answer a few of your embedded questions:

// TODO: Check with Tim & Nathan if commit to SharedPreferences is sync or async. Documentation says sync

commit is synchronous so it is blocking the main thread BUT apply is not. In a lot of cases apply is preferred but for simple cases (i.e small writes) the difference is negligible. In production, I would recommend using apply though in most cases. Here's a related stackoverflow answer.

// TODO: Ask Tim & Nathan if onSuccess and onFinish are sync or async. Guessing its async

The onSuccess and onFinish are firing once the asynchronous request has gone out but the methods themselves are running on the main UIThread (since onSuccess) is so commonly affecting the UI. So the network request is async but the actual callback is on the main thread.

// TODO: My failed attempt at bringing up the soft keyboard

The soft keyboard is kind of disabled with the emulator unless you uncheck "hardware keyboard present" in the emulator configuration (in Virtual Device Manager) for Nexus S

// TODO: Ask Tim+Nathan if onFinish() or onSuccess() is the better place to close the Activity and return th result

onSuccess and onFinish is simply the difference between finish being called if the request gets a response while onFinish is called whether or not there was a response. Typically you can just hook up onSuccess since onFailure typically has different logic.

// TODO: Is there a way to simulate no network activity besides disconnecting my wi-fi?

Best way is using the DDMS perspective and go to Emulator Control Tab. Set 'data' to 'denied':

You can simulate and tweak all sorts of stuff using the DDMS tabs.

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.