Add a new section GR6 User Testing to your group's wiki page, with the following subsections:

• DesignDescribe the final design of your interface. Illustrate with screenshots. Point out important design decisions and discuss the design alternatives that you considered. Particularly, discuss design decisions that were motivated by the three evaluations you did (paper prototyping, heuristic evaluation, and user testing).
• ImplementationDescribe the internals of your implementation, but keep the discussion on a high level. Discuss important design decisions you made in the implementation. Also discuss how implementation problems may have affected the usability of your interface.
• EvaluationDescribe how you conducted your user test. Describe how you found your users and how representative they are of your target user population (but don't identify your users by name). Describe how the users were briefed and what tasks they performed; if you did a demo for them as part of your briefing, justify that decision. List the usability problems you found, and discuss how you might solve them.
• ReflectionDiscuss what you learned over the course of the iterative design process. If you did it again, what would you do differently? Focus in this part not on the specific design decisions of your project (which you already discussed in the Design section), but instead on the meta-level decisions about your design process: your risk assessments, your decisions about what features to prototype and which prototype techniques to use, and how you evaluated the results of your observations.

Design

Implementation

We developed for Android 2.3 using the Google Maps APIs and Eclipse. The server is PHP with a SQL database. Requests are sent from the app, and the servers responds with XML, which is parsed by the app. We tested our app on the Nexus One, Galaxy Nexus, and several other models of Android phones. The test phones included operating system 2.3, but also version 4.0, Ice Cream Sandwich.

Our app has a local front end, but the tour data is stored on our server. We made some simplifications to our system to make it fit into the scope of this class. For this reason, the landmark data is stored locally, and users cannot add new landmarks with their own pictures. Also, we simplified the database for tours by not allowing the user to chose a picture for a tour they create. These don't take away very much from the functionality of the app, at least in terms of what we think our users want/need to do. 

Users can add their own tours to the database, and in the future when they search those landmarks they will find their tour. This is not local to this user, so all users see all tours created. There is currently no way for a user to delete a tour, but this doesn't hurt functionality that much. 

Evaluation

Reflection

Designing a product is highly challenging and may be the most difficult task our group has ever faced together. We all had unique visions for our final product and merging those visions together with the other constraints of real life, such as time, was difficult and taught us all some valuable lessons.

the meta-level decisions about your design process: your risk assessments, your decisions about what features to prototype and which prototype techniques to use, and how you evaluated the results of your observations.