ASUEat Android App Benjamin Dummer Brian Clee Christian Zavala-Santos Kyle Huff Dr. Tashakkori’s Spring 2012 STEP Group:

Initial goals  To make an app for a mobile platform.  Choose to target the Android mobile OS  Should do one thing and one thing well  Should be fast, intuitive, and helpful  To make the App useful for AppState students  Nutrition info for food served at ASU is available online  We wanted to make that info easily accessible for students when they’re not at a computer

Google Android What is Android?  Lightweight operating system originally designed for smart phones  Is available through Google as open source freeware  Comes installed on phones, tablets, media players, TVs, and even a refrigerator!  The number of Android users is approaching 1 billion

Google Android Why do we use Android?  Uses mainly Java and XML languages which are easy to use and we are already familiar with from our CS courses  Documentation, tutorials, and how-to’s are readily available from many different sources  Developing requires no proprietary tools or even an actual Android device. All the tools needed plus a device emulator are available online through Google

Development Process Planning Phase  Came up with several different app ideas and analyzed the feasibility of each one  Decided to make an app that ‘does one thing, and one thing well’  Eventually narrowed down to a nutrition app for ASU students Design Phase  Began by outlining possible features we wanted  We assigned each feature a ‘priority level’ so the most important features get done first  Made diagrams of the user interface screens, of the database, and of the programmed components used in the app

Development Process Design Phase  Several diagrams were made during the design phase to make development easier and more efficient  To the left is an example of a diagram we made, it is a relationship diagram of the app’s SQLite database

Development Process Development Phase  Initially, development went slow as we had to learn the Android OS. Eventually progress got faster as we followed through several books and guides  The Eclipse Java IDE was used as our development environment  Also used the Google ADT plugin for designing, building, and testing our Android code Testing Phase  The app was built and installed on several Android phones and tablets  We were able to monitor the app in Eclipse via DDMS when the device was plugged in through USB.  DDMS allowed us to watch the app execute in real-time as well as provide advanced debugging support.

The ASUEat App  The ASUEat app was designed to allow ASU students to view nutrition info of food served here on campus  Since it can be used offline on a phone, a user can look up nutrition info while they’re in a cafeteria trying to find something to eat  The app can also tracks meals you eat and report how well you eat over time

Live Demo