Difference between revisions of "Quilage"
Line 4: | Line 4: | ||
[TODO: endeavor to explain what the point of quilage is] | [TODO: endeavor to explain what the point of quilage is] | ||
+ | |||
+ | == How it works == | ||
Quilage consists of two main components: a client that runs on a Android phone and a web-server back-end. | Quilage consists of two main components: a client that runs on a Android phone and a web-server back-end. | ||
Line 23: | Line 25: | ||
"bob is eating lunch at the happy hotel" | "bob is eating lunch at the happy hotel" | ||
− | == | + | == User requirements == |
* An android phone with GPS and a data contract. | * An android phone with GPS and a data contract. |
Revision as of 08:49, 7 October 2009
Quilage is a passive RPG based on the player's real life movements, as tracked by their mobile phone.
Contents
Intro
[TODO: endeavor to explain what the point of quilage is]
How it works
Quilage consists of two main components: a client that runs on a Android phone and a web-server back-end.
Client
The client runs on the user's phone and every 15 min turns on the GPS to get a location fix. When it has successfully got a fix, it compares it with the last location fix and uploads the result to the server.
Server
When the server receives an update from a client, it compares the two location fixes and generates a twitter post along the lines of:
"bob walked for 2.52 km in a SE direction"
As well as posting to twitter, the server also stores certain anonymous data so that interesting maps can be built up over time.
If a user stays in the same place for two consecutive updates, the server marks this place as a location and assigns it a generated name with the structure "<adverb> <verb>". Examples include "happy forge" and suspicious hotel. This will then result in a twitter post such as:
"bob is eating lunch at the happy hotel"
User requirements
- An android phone with GPS and a data contract.
- A sense of humor.
Development road map
Main page: Quilage Development
Links
- Previous project page EQA