Assignment 11: Trickiest Parts of Project and Half-way Done

This is a TEAM assignment.

The purpose of this assignment is to help you make progress on your final project. Your goal is to develop the trickiest parts of your final project app and make a convincing case that your application is half way to completion. Significcant aspects of the application must be working smoothly and robustly. For teams using sensing, this will often include the component of the app that uses sensors.

Take the following steps:

Both team members should add a new button to their apps on the Play Store: "Trickiest Part." One team member will just call the Activity in the other team member's package. Your app should then have 9 buttons: About, Generate Error, Sudoku, Dictionary, Dabble, Communication, Two Player Dabble, Trickiest Part, and Quit. Do not add a new icon and launcher for this game ... It should be launched from the home screen of the same app you had for Assignment 1.

Those using sensors who do not have access to phones will probably need to come to help sessions to test on real phones.

This is a team assignment so you should pick which student's BitBucket will be used for the rest of the course by the team and then use that (let's call it the primary BitBucket). The non-primary BitBucket only needs updating to add the new buttons for this assignment and the final project assignment. We will test by installing BOTH student assignments on the phone for each team.

Turn in:

Grades will be assigned as follows:

One member of each team should send an email with subject line "Assignment11". Name the PDF file [TeamMember1FirstName][TeamMember1LastName][TeamMember2FirstName][TeamMember2LastName].assign11.pdf and send to both Mansoor and ...@neu.edu.