In-class 3-minute oral project presentation and/or screencast (3/30 -- strictly timed)
Preparation
You should have successfully completed the readings, homeworks, and tutorial lessons
described on the schedule.
Requirements
There are three functional requirements for this project:
- It must use the TinyDb component and the List data type.
- It must use one or more of the
sensors: Location, Orientation, or Accelerometer.
Write a socially useful app -- i.e., an app that helps your
friends, families, or community in some way -- that uses the above
elements. Your project proposal should address how you app will make
use of these elements and justify its social usefulness.
- The app must make significant and appropriate use of the above elements. Be creative!
- The app should have more than one view or screen.
- The app's code must make appropriate use of procedures, functions, and
arguments to reduce complexity and make the code easier to understand.
- The app's code blocks must be appropriately designed and documented (commented).
- The app must be the joint and collaborative effort of the two-person team.
- The app may be a variation of a tutorial or an existing app.
If so, it must make substantial (non-trivial) improvements or
extensions to the existing app. Make sure you give credit to the
original app in your proposal on your Portfolio.
- You must get instructor approval for the project idea by
March 16.
Teams for Project 2: TBA
- Evan Abraham and Kyle Garvin
- Jordan Adams and Edward Franca
- Sabastion Archibald-Kimmel and Elaine Rojas-Castillo
- Audrey Butler and Nykia Tanniehill
- John Daly and Robert Gau
- Katherine DuVal and Amelia Mostovoy
- Chloe Hirschowitz and Emily Horn
- Chudi Iregbulem and Rob Hamblett
- Dylan Mosenthal and Brian Plungis
- Jennifer Pelletier and Pamela Larromana
- Richie Khan and William Suttell
- Samuel Funnell and Isak Kurbasic
Getting Started
- Project Idea: Meet with your partner and find existing apps
that are similar to what your are thinking of doing. Search on the
Web or on the Android or iPhone Market. Come up with a name for your
app.
- Portfolio Page: Create a Portfolio page for your
projects under the Projects tab. You can create one page on one
partner's portfolio and the second partner can link to that page.
- Elevator Pitch: Write a 1-minute "elevator pitch" -- i.e., a brief
description of your project -- that you can use to "sell" your project
idea. Here's a possible template:
[name of app] is a
[kind of thing it is]
for [the people who would use it]
that, unlike [the major alternatives],
[the major distinguishing feature of your app]
Be prepared to defend your project idea in class.
- Design Document: Design your app. What will the user
interface look like? How will the user interact with it? What events
will be handled? On your portfolio page Include:
- A snapshot of how the screen will be layed out when the app starts.
- A series of event-response descriptions -- i.e., for each event
that will occur, how will your app respond.
- Implementation and Testing. Leave ample time to implement
and test your app. Have your friends try it. Leave time to get help
from the TAs or instructor when you run into debugging issues.
Submitting Your Project
Here are instructions on how to submit your project.