Upgrade to Pro — share decks privately, control downloads, hide ads and more …

IndyGo Tracker

IndyGo Tracker

A final presentation describing the user centered design process followed in order to develop IndyGo Tracker mobile app.

Aeshvarya Verma

February 16, 2014
Tweet

More Decks by Aeshvarya Verma

Other Decks in Technology

Transcript

  1. Setting and Project Scope • IndyGo bus commuters are unaware of

    the exact arrival time of the buses and also don’t have access to a quick and simple route chart, facilities viewer, no alert options etc. • Our App would provide on the fly bus information to the commuters. • We visited bus stops in & around Downtown for observation and contextual inquiries.
  2. Fieldwork Data I •  Following observations were made at the

    Ohio/Meridian bus stop: •  Some commuters were sitting inside the shed while many were standing & keeping a constant watch for their bus to arrive •  They were checking the route charts •  Almost all of them were smartphone users •  Some commuters were asking other co-passengers for the bus info •  Some were running towards the bus stop to catch the bus •  Poor display of bus route charts •  Performed contextual inquiry with one of the bystanders at the bus stop
  3. Requirements •  Functional Requirements The system: •  Should allow the

    user to access the contact information for the indygo bus system. •  Should display real time bus information for each day of the week. •  Should be portable. •  Should contain static and real time bus schedule. •  Should inform the user upon bus arrival. •  Should provide an easy access to leisurely activities while waiting •  Should display bus stop details. •  User Requirements •  User must be able to access information from his web-enabled phone •  User must possess enough knowledge to understand the information presented
  4. User Feedback •  Tasks •  Task 1: Consider you are

    new to Indianapolis and you live near the bus stop called New york St./Illinois St. You want to go to the Wal-Mart, Lafayette road to do some shopping. Since you do not know which busses go to Lafayette road, find your bus number. Also, put an alert for a particular arrival time for that bus. •  Task 2: Suppose you are standing at the New york St./Illinois St. bus stop, find the next arrival time for bus number 37 and look for all the facilities present at that bus stop.
  5. User Feedback •  Issues Identified •  Lack of affordance of

    some of the elements in the interface such as the button for determining the facilities in the shelter. •  The users expected the maps to be more interactive and provide more information than just the route. •  The user wanted to be taken to the screen for the bus numbers first rather than the screen for the maps. He felt that the bus map information was additional information and could have been made optional. •  Lack of information of the duration of travel.
  6. User Feedback •  Future Improvements •  Improve affordance so that

    the users would know that it is clickable. •  Include bus details information on the map itself because •  Include another button that lets the user explore local hotspots surrounding the bus stop by using data feeds from external sources. •  Showing the proper flow from the source to the destination •  Improving the alert process especially in case of late bus arrival. •  Improve the map view interface with more interactivity and information