Wiki source code of A12TeamCacti

Last modified by Zachary Clark on 2010/11/17 15:49

Content · Comments (0) · Attachments (0) · History · Information

Hide line numbers

 1: = Title =
 2: 
 3: Footprint
 4: 
 5: = Authors =
 6: 
 7: Zac Clark, Thomas Cavalier, Aaron Stockton, Jacob Burton, Luke Mattingly
 8: 
 9: = Abstract =
10: 
11: As portable devices become more powerful and ubiquitous, businesses will need to leverage these devices in order to stand out from their competitors. Any service that utilizes the location of a person's device is referred to as a Location-Based Service, or LBS. One such LBS is Foursquare, a location-based social networking application that allows its users to "check-in" to the locations they visit. While Foursquare is mainly used for social networking purposes, can it be used for other purposes, such as to help people become more aware of their energy usage when traveling? 
12: The goal of this project is to extend Footprint by exploring human-centered computing concepts such as user interface design and system usability. There are a wide range of possible areas of work, such as concepting/prototyping, front-end programming, and back-end programming. 
13: 
14: = Keywords =
15: 
16: Energy, Foursquare, Web2.0, Mapping, Anti-consumption
17: 
18: = Problem / Goal =
19: 
20: The idea that cars are bad for the environment is not new or unusual, but its specific applicability to individuals is hard to see and quantify easily. By hooking into an already existing system that tracks a user's travel (Foursquare), Footprint can show the user statistics about their travel with relatively minimal investment. One does not need to be vigilant about tracking their gas expenditure, average travel distance, etc. As long as the user frequently checks in to venues when arriving, all they need to do extra is to tag these trips with some meta-data about their travel (ie: by car, by bike, etc). This is an important problem because raising awareness of carbon emissions is important to help reduce our footprint and lead to more sustainable lifestyles. Also, the project is interesting because it allows us to actually work with data and visual representation, rather than abstract concepts and reasoning.
21: 
22: Initially, our role in the project was to refine the interface to make the application as easy to use as possible. The rational behind that decision is that by lowering the amount of work required to use the system, the barrier of entry is reduced, making it more likely to be used by more people. We were to improve visual design, as well as the logical flow between pieces of the application. As part of the visual design piece, we need to figure out how best to show the statistics we are collecting in a way that will motivate the user to make changes.
23: 
24: After some work on the project we realized that some "invisible" changes had to be made before we could start, such as cleaning up the existing codebase and integrating it into a version control system such that multiple developers can work together on changes to the product. This took more time than we had anticipated, and became a large part of our initial work.
25: 
26: = Methodologies =
27: 
28: Wireframing, Sketching, Product Flows, Software Development, Distributed Version Control
29: 
30: = Relationship of your Project to the Themes discussed in the Course =
31: 
32: Energy (the core of the project)
33: 
34: Motivation (how to encourage users to change their habits)
35: 
36: Design (visual and interface)
37: 
38: Meta-Design (designing the development eco-system to promote application design)
39: 
40: = Characterization of the Individual Contributions =
41: 
42: Team Leader: Zac Clark
43: 
44: Back End Development: Jacob Burton, Aaron Stockton
45: 
46: UI: Thomas Cavalier, Luke Mattingly
47: 
48: = Findings and Results so far =
49: 
50: We have a working application that we will demo during the class presentation.
51: 
52: = Further developments planned till the end of the semester =
53: 
54: Documenting our changes. We want to make sure that the work we put in is adaptable and useable by later developers on the project. In an effort to encourage this we will be documenting how our code and changes work, with the methodologies behind it. This includes storing all our mockups and designs in a central space, as well as providing some written work on the state and design of the application.
55: 
56: Updating User management. We want the application to be as easy to use as possible, so we figured that everything should revolve around a user's foursquare account, since it is required to use Footprint. A user won't need to register an account, simply to link their foursquare account to our service.
57: 
58: Google Maps. We are going to investigate adding mapping to the checkins so a user can see the path they took.
59: 
60: = References =
61: 
62: http://foursquare.com/
63: 
64: http://groups.google.com/group/foursquare-api/web/api-documentation?pli=1
65: 
66: https://github.com/
67: 
68: http://www.joesiewert.com/2010/04/how-to-use-the-foursquare-api-with-oauth-and-php/ 
69: 
70: http://xwiki.cs.colorado.edu/bin/view/HCCF2010/Project-5
71: 
72: http://xwiki.cs.colorado.edu/bin/view/HCCF2010/Footprint

Course Pages

Recently Visited

Progress Report 2: Model Authoritative VS. Model Democratic | Project1 | Documents on this Wiki | Assignment 10 Posted

Recently Modified

MSC Final Project ...
MakeShiftCrew Proj...
Embedding Content
Human-Centered Com...
Assignment12KyleMa...

See More Changes

Recently Created

WebPreferences | RatingStats | palen | ksiek | kena

Wiki source code of A12TeamCacti

Course Pages

Recently Visited

Recently Modified

Recent Comments

Recently Created