Publicité
M. Watkins - Chromaroma - Geomob October 2010
22 Oct 2010•0 j'aime•371 vues
0 j'aime
Soyez le premier à aimer ceci
afficher plus
vues
Nombre de vues
0
Sur Slideshare
0
À partir des intégrations
0
Nombre d'intégrations
0
Signaler
Technologie
GeomobLDNSuivre
GeomobLDNPublicité
![Agree product[1]](https://public.slidesharecdn.com/_next/static/media/rec_thumb_placeholder.82109866.jpeg)
M. Watkins - Chromaroma - Geomob October 2010
- Chromaroma Ambient Gaming
- Proliferating Location Knocking at the mainstream
- Locative Game Player Old - Active, Engaged, Outside
- Locative Game Player New - Social, Bragging, Indoors
- Swiping Lo-Tech User Interface
- Bus Swiping Lo-Tech User Interface
- Bike Docking Lo-Tech User Interface
- Scraping Getting the data
- Division of Development Serial Processing
- Playing a Lag Waiting for 48 hours
- Visualising Journeys Trains - Topographical
- Visualising Journeys Bikes - Geographical
- Visualising Journeys Items - Placing, Collecting…
- Visualising Journeys …and Trapping
- Security Protecting your location
- Changing Behaviour
- Thanks Matt Watkins CTO Mudlark Twitter: mazwat Developed with: Ruby on Rails AS3 / Flex Modest Maps - Flash/Open Street Maps Resources: wearemudlark.com chromaroma.com tfl.gov.uk opendata.gov.uk
Notes de l'éditeur
- I Chromaroma is a team game played on London Transport. Where you play as one of a coloured team- red yellow or red. But you also play as an individual and within groups you can define with your friends
- Location gaming has come of age there are a lot of different applications out there.
- Dedicated time frames, happening outside, interacting with a time based narrative. Highly orchestrated. Commited early adopters
- The new player is using it a social event informing other of their whereabouts. Checking in. actively locating.
- Lo-tech. Only requiring an oyster card. Creating an imaginary layer on regular activity Passive in the background, happening despite yourself
- Assigning relevance to pre-defined activity
- Adding significance to physical infrastructure
- Ruby used
- Compared to standard web development there is a lot of complexity associated with processing a lot of events and applying game mechanics to it. The cost of change is high
- Like slow food - slow gaming A user has to wait 48 hours to receive the results of their play. we like to think of it as a turn based game.
- Events are processed as Acheivements, Missions and Collections
- A mission. Some are simple like Goose other more complex.
- Create an excting playback of the events you planned before. Getting rich feedback and creating visual replay of real event
- Show bike journeys
- Items creates interaction within the interface enabling people to place.
- Show bike journeys
- If you can follow someones path you can observe a number of interesting behavioural activities. You can choose who sees your journey history. You can find your friends via Twitter and, very soon, Facebook. But be aware, because your Journey History at TFL is 48 hours behind, so is your game data
- The goose mission - people discovering that the difference between getting off one stop earlier. Can sometimes be as small as a five minute walk Mother and daughter team discovering London together and apart. Filling in the gaps Discoveing the benefits of auto top-up Swipe out and in within a certain time frame does not incur a cost. Sebastien Detarding talk about gamifying life adding badges and easy rewards is not a game. But we are trying to create an additional act of determination sharing activities coming to gethe to take stations by hitting barriers all at once. Altering behaviour because the existing behaviour is tedious
- Adding bus journeys is a big ask: 600 stations versus 1500 routes and 55,000 stops
Publicité