[Android Bootcamp] Day 4 Assignment

[prajaa]

My app is ready , please review. /cc @codepathreview @codepath. Name: Prajakta Link to Video - https://github.com/prajaa/MyInstagramClient/blob/master/app/src/main/res/drawable/day4.gif

Covers user stories:- Add pull-to-refresh for the home feed with SwipeRefreshLayout. User can open the Instagram client offline and see last loaded feed. Each media item is persisted into SQlite and can be displayed from the local DB. Create a background service to make the network request, load items into the DB and populate the view (for the user's home feed).

[codepathreview]

Good job finishing all the stories. Below we've captured the most common issues with today's stories. Read through this point-by-point to determine how you could improve your submission.

• What operations should occur in the Service
  • We definitely want to make the network request in the service.
  • While we're already in the service context, which runs on a background thread, you should do the following in the service as well:
  • parse the network response when it comes back
  • load the parsed objects into the DB
  • return the parsed objects to any listeners
  • If all you're doing is a simple DB query (e.g., when the network is unavailable), it's fine to do it on the main thread since databases are optimized for speed.
  • If you find the query takes relatively long, and the UI starts to suffer in terms of responsiveness, then push it off to a service.
• Default value for a Service's exported attribute
  • When declared in the AndroidManifest.xml file, a Service is by default not accessible by other applications (i.e., exported = false) if it has no intent filters. See Service elements in Manifest File for a detailed explanation.
• Avoid nested ViewGroups. Flatter view hierarchies are more performant
  • If possible, try to keep the view hierarchy as flat as possible. Nesting ViewGroups should be avoided, since this can affect the time that it takes to render the layout. See the following article on how Android draws views. A good number of ViewGroups do multiple traversals of their view hierarchies to calculate how much screen real estate all of its contents should receive.
• When clearing rows in the DB, foreign key constraints must be taken into account
  • Because posts reference user and image rows, you cannot delete a user if the DB contains a post that references it.
  • Emptying the database needs to be done in this order:

  // this is the join table for posts and comments
  db.delete(TABLE_POSTS_COMMENTS, null, null);

  // posts reference both users and images
  db.delete(TABLE_POSTS, null, null);

  db.delete(TABLE_COMMENTS, null, null);

  // users and images refer to no other tables
  db.delete(TABLE_IMAGES, null, null);
  db.delete(TABLE_USERS, null, null);

• Wrap transaction operations in a try / finally block
  • To ensure that db.endTransaction() is called regardless of whether an operation fails or not:

   db.beginTransaction();
   try {
     ...
     db.setTransactionSuccessful();
   } finally {
     db.endTransaction();
   }

• Convert InstagramPost class to Parcelable for easy array serialization
  • Because the InstagramPost class implements Serializable, to package a list of posts into an intent, a serializable wrapper is needed. This is fine for the assignment.
  • Parcelable: A cleaner alternative
  • The problem with InstagramPost is that it contains nested objects. See this article, which shows how nested parcelable objects are marshalled and demarshalled.
  • Once InstagramPost implements Parcelable instead of Serializable, you can do this:

  List<InstagramPost> posts = new ArrayList<InstagramPost>();

  Intent intent = new Intent();
  intent.putExtra("posts", posts);

  // Extracting data on receipt of intent
  List<InstagramPost> fetchedPosts = getIntent().getParcelableArrayListExtra("posts");