CS 342: Mobile Application Development

Wrapping things up

Demo: June 2 and 4 in class

You and your group will have ten minutes (including transition time!) to share your work with the class. Plan to organize your time roughly like this:

(2 minutes) Transition time. Getting set up to project your app.

(2-3 minutes) Demonstrate your app's features.

(2-3 minutes) Highlight some interesting design choice or technical challenge you faced in this project. (What do I mean? Consider some examples from my Android dictionary project: how I got my Java code and Javascript in a WebView to talk to each other; how and why I fooled the Android app packaging system into not compressing my data files; how I incorporated C++ code into an Android app; how to design the in-app store to make 35 dictionaries available for easy sale but not in an irritating or intrusive way; how I made a fast-scrolling list view with hundreds of thousands of items; etc.)

(2 minutes) Open the floor for questions.

Some logistics:

We will start class on Monday with the three groups who expressed an interest in going first. Then we'll draw group names out of a hat. Thus, you should all be prepared to do your demo on Monday if your name gets drawn. (Also, the two It's A Trap groups will present together or back-to-back, so figure out how you plan to coordinate that.)

I will contact the external clients for the two energy groups, the weather group, and the New Student Week group, and I may then doctor the schedule so that they can attend the demos. I'll let the relevant groups know the plan as soon as I hear anything.

If an emulator is adequate for demonstrating your app, make sure the latest commit to your version control compiles and runs, so I can have it ready to go on my laptop to minimize transition time.

If an emulator is not adequate, it's up to you to figure out (ahead of time!) how to project an actual device in our classroom. PEPS downstairs in Weitz should be able to help.

Delivery

Your completed project is due at 11:59PM Wednesday, June 4.

Submit it by making sure I have access to your git or hg repository, and that the main branch's latest commit is the version of the project that you intend to submit. I need to be able to do "git clone your-url" (or hg), read your readme.txt, and then open the project in Android Studio or Xcode and run it.

Your repository should include:

• All source code, data, and project files required to fully run and test the app.
• A readme.txt file at the root of the repository, containing:
  • A brief description of the project.
  • A brief description of the status of the project. (What doesn't work, etc.)
  • Any "getting started" guidance you think I need. The goal here is to make it as easy as possible by the downloader (me) to build and use your app.
• I do not intend to install any new tools on my test computer, so if you're using external libraries, they should be included in your repository.

Have fun!

I'm very excited to see the finished products.