Start by initializing the AppRater Activity. You should query the AppContentProvider to retrieve a Cursor containing all of the Apps it contains. Use this cursor to initialize your AppCursorAdapter and ListView members.

• The Android Developer Guide offers instructions on how to Query a ContentProvider.
  
  
• The URI for the AppContentProvider is defined in the AppContentProvider.CONTENT_URI constant String.
  

You should be able to run your application and view a list of Apps.

When a user clicks on an AppView, you should start the Market Activity implicitly, meaning that you should not use an Intent that explicitly launches the Market Application. Instead, you should use an Intent object that should cause the Market application to be launched. You do this by specifying an Intent action-string and the data to be acted upon. When the Market application starts, it immediately displays the info page for the App that was clicked.  Note that the Market app is not included in the emulator.  You will need to attach a phone to test this portion of your app.  You should handle the exception that gets thrown if you are unable to launch the Market for an App - post a Toast message "Unable to get App from Market" when this happens.

If you are confused on how to implicitly start an Activity or for more details on Intents, see either the Android Documentation or the Android Developer Guide on Intents:

• You should use the App.m_strInstallURI as the data which should be acted upon.
  
  
• You should use the Intent.ACTION_VIEW as the action to be performed.

You should be able to run your application, click on an App, and have the Market application display the selected App's info page.

Hint: Consider implementing onItemClickListener in AppRater to handle clicks on your ListView.

The AppDownloadService needs to be started and stopped from the AppRater's Options Menu. Additionally, you may want to remove all the Apps from the ContentProvider in order to repeatedly test the AppDownloadService, so you will need to create a MenuItem for this as well. Implement the AppRater Activity's Options Menu as follows:

• Consider overriding the Activity.onOptionsItemSelected(...) method instead of implementing and setting OnMenuItemClickListeners.
  
  
• The "Start Downloading" MenuItem should use AppRater.MENU_ITEM_STARTDOWNLOAD as its ID and should start the AppDownloadService:
  
  
• Use the Context.startService(...) method with an explicit Intent.
  
  
• The "Stop Downloading" MenuItem should use AppRater.MENU_ITEM_STOPDOWNLOAD as its ID and should stop the AppDownloadService:
  
  
• Use the Context.stopService(...) method.
  
  
• The "Remove All Apps" MenuItem should use AppRater.MENU_ITEM_REMOVEALL as its ID and should delete all Apps from the ContentProvider:
  
  
• See Android Developer Guide on Modifying ContentProviders for information on how to delete rows from a ContentProvider if you're confused.
  
  
• Passing in null for the where and selectionArgs parameters will cause all rows in the ContentProvider to be deleted.
  
  

Run your application and you should see the pre-populated Apps. Click the "Start Downloading" MenuItem, and wait a few seconds for the Apps to download and appear in your ListView. You should see a notification in the Notification Bar. Click the "Remove All" MenuItem and all the Apps should disappear.

It is important to note that your AppDownloadService will continue to run. If you wait a few more seconds the ListView should repopulate itself with the Apps. The AppDownloadService will run even after you have closed the AppRater Activity. You must explicitly stop it by using the "Stop Downloading" MenuItem in order to shut it down. 

Fill in the AppReceiver.onReceive(...) method so that the AppRater Activity displays a Toast notification telling the user that a new app was downloaded:

• You should test the Intent argument to ensure it has AppDownloadService.NEW_APP_TO_REVIEW as its Action-String.
  
  
• Your Toast notification should use the R.string.newAppToast String resource.

In order for your AppReceiver to be notified when AppDownloadService.NEW_APP_TO_REVIEW action Intents are broadcast, you must register an instance of it with your Activity. Likewise, when the Activity moves out of the foreground, you need to unregister the AppReciever.

• Override and fill in Activity.onResume(...).
  
  
• Initialize AppRater.m_receiver.
  
  
• Construct a new IntentFilter that only listens for the AppDownloadService.NEW_APP_TO_REVIEW action string constant.
  
  
• Intents can be broadcast from any android component to any android component. Declaring an IntentFilter allows you to specify which Intents you want to listen for by specifying certain Intent characteristics. In this case we're only interested in Intents that have an action string of AppDownloadService.NEW_APP_TO_REVIEW.
  
  
• Use the Activity.registerReceiver(BroadcastReceiver receiver, IntentFilter filter) method to register m_receiver for Intents containing the AppDownloadService.NEW_APP_TO_REVIEW action string.
  
  
• Override and fill in Activity.onPause(...).
  
  
• Use the Activity.unregisterReceiver(...) method to unregister m_receiver.

Run your application and click the "Remove All Apps" MenuItem to clear the AppContentProvider. Then click the "Start Downloading" MenuItem. After a few seconds the AppRaterActivity should display the new app Toast notification as new Apps are added to the ListView.

The Context menu should use a CheckBox MenuItem for selecting whether the App has been installed, and a group of four RadioButtons for selecting the rating to apply to an App. 

Implementation Requirements:

• The "Installed" CheckBox should use AppRater.MENU_ITEM_INSTALLED as its MenuItem ID.
  
  
• The "X Stars" Rating RadioButtons should use AppRater.MENU_RATING_GROUP as their Group ID, and should use the AppRater MENU_ITEM_RATING1, MENU_ITEM_RATING2, MENU_ITEM_RATING3, MENU_ITEM_RATING4 constants as their individual MenItemID's.

Functional Requirements:

• If the App has not been installed you should not be able to give it a rating and all the RadioButtons should be disabled (but still visible). 

• Once an App has installed, the RadioButtons should be enabled to allow the user to edit the rating. 

• If the user has installed and rated an app, then the ContextMenu should have the proper CheckBox and proper RadioButton selected respectively. 

• If the App has not been rated, then no RadioButton should be selected.

Hint: If you have problems with your app not responding to a long-click, check to see that you implemented onItemClickListener in AppRater, rather than an onClickListener on AppView for handling normal clicks.

The tricky part here is figuring out which App to make the changes to. You need to identify the AppView that was clicked when the ContextMenu was generated. From the AppView you can retrieve the App. Follow these instructions to retrieve the AppView and its App:

• When the onCreateContextMenu(...) was called, your ListView that generated the ContextMenu provided the method with an AdapterView.AdapterContextMenuInfo parameter.
  
  
• When you add a MenuItem to a ContextMenu the ContextMenuInfo gets added to the MenuItem.
  
  
• The AdapterContextMenuInfo has a public member variable that references the AppView that was clicked.
  
  
• Retrieve the ContextMenuInfo from the MenuItem.
  
  
• You'll need to cast it to an AdapterView.AdapterContextMenuInfo.
  
  
• Retrieve the targetView member from the AdapterContextMenuInfo object.
  
  
• You'll need to Cast it to an AppView.
  
  
• Retrieve the App from the AppView.
  
  
• This is the App that was clicked. So simple right :)

Here are the Functional/Implementation Requirements you should statisfy:

• When the user clicks the "Installed" MenuItem, you should toggle the App's m_bInstalled member variable and reset its m_nRating to App.UNRATED. 
  
  
• When the user clicks a "X Stars" Radio Button, you should set the App's m_nRating to the ID of the clicked MenuItem. 
  
  
• When the user clicks any MenuItem you should update the ContentProvider with the new data for the App.
  
  
• When the user clicks any MenuItem this should cause the background color of the AppView to change.
  
  
• Should change to red if the app has been uninstalled.
  
  
• Should change to yellow if the app has been installed.
  
  
• Should change to green if that app has been rated.

An additional use case for uninstalling a previously installed and rated App is pictured in the screenshots below. Notice that the rating should be reset to App.UNRATED if it is re-installed.

Hints:

• You've changed your underlying data, don't forget to update your Cursor & Adapter.
  
  
• The Android Developer Guide offers instructions on how to Update a ContentProvider.
  
  
• The URI for the AppContentProvider is defined in the AppContentProvider.CONTENT_URI constant String.


• IMPORTANT: You must restrict your update to a single App row in the ContentProvider or you will end up persisting your change to all the Apps. The section on Querying a ContentProvider offers advice on how to restrict your URI to affect only a single record.
  
  
• If you create your URI correctly you can pass in null for the where and selectionArgs parameters.

When the Service is first started, the onCreate() method is called. You should initialize your Timer and TimerTask.

• You should read the Documentation on the java.util.TimerTask Class. A TimerTask represents a java.util.Runnable object that your Timer will execute.
  
  
• Your TimerTask should only call the AppDownloadService.getAppsFromServer() method.
  
  
• You should read the Documentation on the java.util.Timer Class. Timer's are essentially threads which can be scheduled to execute TimerTasks at specified rates.
  
  
• Your Timer should schedule your TimerTask for "fixed-delay" execution.
  
  
• Your TimerTask should be scheduled at a period of AppDownloadService.UPDATE_FREQUENCY milliseconds.
  
  
• Feel free to adjust this number for testing purposes.
  
  
• You shouldn't create a daemon Timer.
  

When the Service is stopped, its onDestroy() method is called. You should free up any resources that you have allocated in this method, including threads.

• If you don't explicitly cancel your Timer and TimerTask, they will continue to run indefinitely.
  

This method should download a list of Application Name and InstallURI pairs from a server. For each Application Name and InstallURI pair, the method should construct an App object and hand it over to the AppDownloadService.addNewApp(...) method.

• You should use the two argument App constructor.
  
  
• The method should download from the URL that is stored in the AppDownloadService.GET_APPS_URL String constant.
  
  
• If you visit the URL, you will see the format the data comes in:
  
  
• The individual Application Name and InstallURI's data pieces, which correspond to the same App, are separated by a comma ',' character .
  
  
• Application Name and InstallURI pairs, which represent separate Apps, are separated by a semicolon ';' character.
  
  
• Example: (Three separate Apps - Green; Red; Yellow)
  
  app-name-1,market://details?id=com.package1.app1;app-name-2,market://details?id=com.package2.app2;app-name-3,market://details?id=com.package3.app3;
  
  
  

This method should first test to see if the App already exists in the ContentProvider. You should query the AppContentProvider. If the App does not exist, then you should insert it into the ContentProvider and call the AppDownloadService.announceNewApp() method.

• Two Apps are considered equal if they have the same name.
  
  
• The Android Developer Guide offers instructions on how to Insert and Query a ContentProvider.
  
  
• Note: Do not add the ID to the ContentValues for the new App you are inserting, which will be -1 if you used the correct constructor. The Database will automatically generate a unique ID for you. Trying to insert a new App with an ID of -1 will cause an SQLException.
  
  
• The Android Developer Guide offers instructions on how to Broadcast Intents.

This method should broadcast an Intent containing the AppDownloadService.NEW_APP_TO_REVIEW action string, and launch a Notification.

• For the notification, use the following resources:
  
  
• Content Title: R.string.app_name
  
  
• Content Text: R.string.newAppNotificationText
  
  
• Ticker Text: R.string.newAppNotificationTicker
  
  
• Notification Icon: R.drawable.icon.
  
  
• When you click on the notification, it should launch the AppRater Activity.
  
  
• The Android Developer Guide offers instructions on how to Create Notifications.

The AppRater Activity class is currently using the AppDownloadService implementation that was provided to you. You need to remove the import statement at the top of the AppRater.java file. Delete the following line:

import edu.calpoly.android.appraterkey.AppDownloadService;

You should now test your application to ensure that it functions as it did before.

You will need to add your Service to the AndroidManifest.xml file. You can look in the file to see how it was done for the appraterkey.AppDownloadService.

The AppRater class and AppDownloadService class are currently using the AppContentProvider implementation that was provided to you. You need to remove the import statements at the top of the AppRater.java and AppDownloadService.java files in order to use your implementation. Delete the following line from each of these files:

import edu.calpoly.android.appraterkey.AppContentProvider;

You should now test your application to ensure that it functions as it did before.

You will need to add your ContentProvider to the AndroidManifest.xml file. You can look in the file to see how it was done for the appraterkey.AppContentProvider.