Assignment 1: Hello Mobile Application Development (HelloMAD) on the App Store

Individual Assignment

The purpose of this assignment is to help you get started with the Android development tools. You will “publish” your first application on the Android Play Store. This application will evolve over the course into your final project. When you have an update, you will send it to the Play Store. We will grade the apps right off the Play Store.

Using the Hello Android text and materials on the Android developer web site (http://developer.android.com/sdk/index.html and http://developer.android.com/training/index.html), create a Hello Mobile Application Development (HelloMAD) application.

This is the program that you will update throughout the course.

Your app should have the following:

• A Titlebar with your name
• An “About” button that, when clicked, should display the following:
  • Your name
  • Your email
  • Your year in school (First-year, sophomore, middler, junior, senior, 1st year MS or PhD, 2nd year MS or PhD, etc.)
  • Your degree program
  • A nice head shot picture of you
  • The phone's unique ID (IMEI or MEID), generated programmatically (note that on the emulator this will appear as "0000000000000000")
  You can do this using another Activity or some type of dialogue box widget ... it is your choice. Format your text nicely so it looks professional.
• A “Generate Error” button that should intentionally cause an error in the code to crash your program (this will be used to test the Google error tracking feature).  You can cause an error at runtime in many ways. One would be try and access an object that has not been initialized properly.
• A “TicTacToe” button that should start the Ultimate Tic Tac Toe example from the Hello, Android text. This example can be found from the publisher's code site for the book. You should select the ticTacToev6 version of the code.
• A "Quit" button that exits the program.
• A unique icon that gets placed on the phone’s app list in the launcher.
• Any other bells and whistles you want to add. 

Your app should not be playing music from this main menu. You must change the Tic Tac Toe music file to some other non-copyrighted music file.

It is important that the only people who can run your app are people in the class and the instructors. This for two reasons. First, you will be adding your new code to this app throughout the course. You don't want to to prematurely "release" ideas to the public and have them reviewing what you do. Second, and more importantly, the Hello Android TicTacToe code is copyrighted, and you cannot release that as your own app. Google has an alpha and beta release option to facilitate this. You will use the alpha release functionality. Read about how this works from the Google page on Beta-testing and staged rollouts (We will used the closed option). The alpha group of testers will be the instructors and classmates who are members of this Google+ community: NUMAD17S. Click on this link when you are logged into Google and "Ask to Join" so we can add you to the group.

Your app should have the name NUMAD17S-[YourFirstName][YourLastName] on the phone (e.g., NUMAD17S-StephenIntille). Use the package edu.neu.madcourse.yourname (e.g., edu.neu.madcourse.stephenintille) for your code (this means you must refactor the package for the Tic Tac Toe example, as well).

When you post on the Play Store, you will be required to supply some icons and screenshots. You need to create a unique icon for your class app and create the other images required by Google. Your icon should not include any copyrighted imagery (if you do, Google may reject publishing of your app). A simple idea is to just use your initials. For now, your app description should simply say, "This is an application developed for Northeastern University's class on Mobile Application Development."

As you complete this assignment and have “aha!” moments where you figure out tricky things that might hold other people up, you should post those to the Piazza message group. Good contributions helping peers on Piazza throughout the term will be considered in borderline grade decisions at the end of the term, so please use the message group to help each other.

In addition to submitting your app on the Play Store, you will also need to setup an account on Bitbucket where you will submit your project files using the source control program GIT and track bugs as you develop your work. Follow these instructions on submitting assignments and using Git and Bitbucket. This will make it possible for the course staff to access your code for review. You need to learn to use Git properly so that you are incrementally committing your work to the Bitbucket repository. You should not include project specific files or build files in your Git repository.

We use Android Studio in the class. Android Studio is a merger of Google Android tools and the excellent IntelliJ IDE. IntelliJ has a great reputation and some very nice code checking/completion features and is the primary IDE for Android soon. Android Studio wants projects to have a slightly different directory structure than Eclipse, a tool many people used before Android Studio was developed, so be aware you will need to change project structures in many sample projects use may use.

It's always a good idea to test on an old, slow phone with a small display. In that spirit, test your app on the emulator with a Kyocera rise setting.

Hand in:

You submit your assignment by making it available for alpha testing on the app store by the assignment deadline. Your project should also be properly setup on Bitbucket and you should have granted access to the TAs and Prof. Intille.

By the deadline, you must have your app on the Play Store and your code repository setup in Bitbucket.

Send an email to the course assistants and Prof. Intille with subject line "Assignment1: [YourFirstName] [YourLastName]" (e.g., "Assignment1: John Doe") and include the link to your Bitbucket site and the link to your app in the app store.

Evaluation/feedback:

You will be graded based on how well you follow the instructions above. Details matter! As much as possible, we will provide feedback to you through Bitbucket as we will do in future assignments. Although it is subject to changes, this table will give you rough sense of how you will be assigned points.