Press Destination
We presented our scenario video to the tutors in today’s tutorial, followed by a round table discussion. The main issue presented by the tutors was the social networking link that our design addresses is too weak, and that greater social interaction needs to occur between passengers waiting at bus stations not just passengers interacting with the bus driver. One possibility Patrick brought up with the tutors was the bus stops having the ability to be updated immediately with a ~20sec delay if people are getting on or off at any bus stop along the route. For example if you are waiting at the fifth bus stop along a route, for every stop before yours that there are people waiting to get on or off, the bus stop will show a progressive ~20sec delay to give the bus driver time to stop and pick up/drop off passengers.
Tuesday, September 21, 2010
Tuesday, September 14, 2010
Week 09 Tutorial
In the meeting today, Patrick, Kane and I had many detailed discussions about the aesthetics and behavior of the new concept for the bus stop. The main issue we discussed was the amount of LED's we would use for each bus stop. Originally we were to have one line of RGB LED's which would represent all the bus routes and individual bus numbers would be identified through colour. My argument against this interface was that people may get confused when they can’t see where their bus is going to end up at the end of the route. Also, during peak times only having one strip of LED’s might not be enough to handle the added routes during these times.
One solution was to represent each bus number along a route with separate lines and separate LED's along each path. This concept was good for showing people where they need to go, but it used four times as many LED’s as one strip. We compromised as a group as we liked the usability of have separate lines to show each bus number, and we liked the simplicity and elegance of having a single strip of LED’s to show busses on route.
To be continued…
One solution was to represent each bus number along a route with separate lines and separate LED's along each path. This concept was good for showing people where they need to go, but it used four times as many LED’s as one strip. We compromised as a group as we liked the usability of have separate lines to show each bus number, and we liked the simplicity and elegance of having a single strip of LED’s to show busses on route.
To be continued…
Impromptu meeting
Last Thursday Patrick, Kane and I had a meeting to further develop the bus stop flagger. The meeting mainly covered a new aesthetic for the design, and also new ways to interact with it.
The bus stops will now be personalized with the bus route actually being the shape of each bus stop, which you can see with the picture. In terms of behavior we decided to integrate LED’s into the surface of the bus route which gives users feedback about the locality of their bus.
The two parts sprouting from the top of the bus stop serve separate purposes. The part that would be over the gutter, facing the road will show the driver what bus needs to stop at that particular bus stop. The inward facing piece will contain a light and possibly a speaker if we decide to incorporate audio messages into the design.
The bus stops will now be personalized with the bus route actually being the shape of each bus stop, which you can see with the picture. In terms of behavior we decided to integrate LED’s into the surface of the bus route which gives users feedback about the locality of their bus.
The two parts sprouting from the top of the bus stop serve separate purposes. The part that would be over the gutter, facing the road will show the driver what bus needs to stop at that particular bus stop. The inward facing piece will contain a light and possibly a speaker if we decide to incorporate audio messages into the design.
Thursday, September 9, 2010
Tuesday, September 7, 2010
Behavior of the bus stop
Our design took on a new look and slightly new system after the group meeting we held after the Week 08 tutorial. As the user approaches the bus they have several ways of finding information.
Note: At the moment the design uses the inbuilt GPS in a bus coupled with twitter (each bus number has its own twitter page) which send tweets every time it leaves a stop on-route.
Firstly they can scan and slide their GO Card down the bus route, to their desired destination, which is lined with RGB LED’s (a different colour for each bus number). The quickest route will be shown by the LED’s along the route and the bus number will be displayed for the driver so he/she knows if to stop or not. The LED’s along the route will then go through a flash sequence followed by a new measuring system that shows how far the soonest bus going to their destination is away from their stop. The bus stops are represented by push buttons along the route which is another way for users to choose their destination.
Using the GO Card systems users can also gauge how full a particular bus is with the bus icons on the right of the interface. The squares are backed with LED’s and indicate how full a bus is in increments of 25%. The interface also houses a twitter feed of the busses on the particular route, which will work along with the LED’s to give a more accurate system of tracking busses.
We Endeavour to design a universal system which is why we are including multiple variations of interaction. Brail is already going to be included on the bus stop buttons, so a blind person could flag down a bus driver quite easily. One concept we discussed was to give blind people as much information as a visually able person by placing a dynamic texture above the LED’s along the route so they could feel how far away the bus is by feeling down the route (along the lit LED’s and raised the texture) to the position of the bus (to the last lit LED and the beginning of the low texture) in relation to their stop.
Note: At the moment the design uses the inbuilt GPS in a bus coupled with twitter (each bus number has its own twitter page) which send tweets every time it leaves a stop on-route.
Firstly they can scan and slide their GO Card down the bus route, to their desired destination, which is lined with RGB LED’s (a different colour for each bus number). The quickest route will be shown by the LED’s along the route and the bus number will be displayed for the driver so he/she knows if to stop or not. The LED’s along the route will then go through a flash sequence followed by a new measuring system that shows how far the soonest bus going to their destination is away from their stop. The bus stops are represented by push buttons along the route which is another way for users to choose their destination.
Using the GO Card systems users can also gauge how full a particular bus is with the bus icons on the right of the interface. The squares are backed with LED’s and indicate how full a bus is in increments of 25%. The interface also houses a twitter feed of the busses on the particular route, which will work along with the LED’s to give a more accurate system of tracking busses.
We Endeavour to design a universal system which is why we are including multiple variations of interaction. Brail is already going to be included on the bus stop buttons, so a blind person could flag down a bus driver quite easily. One concept we discussed was to give blind people as much information as a visually able person by placing a dynamic texture above the LED’s along the route so they could feel how far away the bus is by feeling down the route (along the lit LED’s and raised the texture) to the position of the bus (to the last lit LED and the beginning of the low texture) in relation to their stop.
Subscribe to:
Posts (Atom)