Mobile App Development: Final Project Instructions

Your final project is the culmination of all your hard work in the course. Your goal should be to produce an app that will be a strong addition to your programming portfolio that is creative, well-designed, addictive, useful, and robust. Your app must have a clean design that feels simple, operate smoothly and without sluggishness, not crash, and have a clever twist. The app must take advantage of one or more of the unique capabilities of the phone and have the potential to stay interesting even after extended use. No explanation should be necessary to use the app beyond what someone might read on the Play Store when downloading it. The design should respect the ideas we have talked about in class and be in the scope of helping with some health-related issue.

Your team will present your idea during one of the two last classes using the Final Presentation Template. The template describes the structure of the presentation. Your team should email your presentation to Mansoor the evening before your presentation. The class will be randomly divided into two groups. Group 1 will present on the 2nd to last class. Group 2 will present on the last class.

You will submit your assignment by publishing on the Play Store. You will also update your Git repository. Assignments are due on Wed Apr 17 (end of day) for those registered for the undergraduate version of the course, and Sat Apr 20 (end of day) for those registered for the graduate version. Teams can request a regrade up through the end of the day on Apr 26 (at which time the latest app on the Play Store will be used).

Please carefully follow these instructions:

• Both team members should add a new button to their apps on the Play Store: "Final Project". As in prior assignments, one team member will just call the Activity in the other team member's package. Your main app will then have all your prior buttons (e.g., About (with your team info), Generate Error (generates error), etc.) and your new "Final Project" button. Clicking this app should start an Activity that includes (1) the name of your app and (2) the 4000 char or less description of the app that would appear on the Play Store. This description should be well done, professional, and typo free. It should be credible and entice people to want to try your app. Please DO NOT put this description on the app store, because we do not want to attract attention to your app from people not in the course (this is why there is is this special screen)
• Please have your apk put a new icon that is appropriate for your app in the launcher, and name it "MAD-[Your app name]". Installation of your apk will lead to two icons being put in on the app launch screen. Your old NUMAD-[your name] and the new MAD-[your app name]. Clicking this latter icon will start your final project directly. It should NOT show the app description screen. In other words, clicking this button starts the app in the same way a person would normally start it, who had already read the description on the Play Store. Make sure you look at the slide from class so that you have this right.
• Please double check that your app installation is leaving no other icons on the app launcher screen.
• Your app must include all information needed to use it as part of the app. There should be no additional instructions, because people downloading the app from the Play Store wouldn't have anything like that. For apps that use Wockets, the app should include instructions of what someone needs to do with Wockets, but you can assume that your users know what they are and how to charge/use them.
• Update your acknowledgements screen so that it includes all content used for the final app and also indicates what models of phone you have tested on.

The heuristic checklist (and other items discussed in class) should be considered as you put the finishing touches on your app.