Chauffeur is a mobile application designed by Michael Iseri as a student project at General Assembly's UXDi program in Winter 2013. The app is intended to help users navigate public transportation in the Bay Area, especially for first-time users or those wanting to rest on long trips. It provides real-time schedule updates and notifications about how far users are from their destination using open data from BART and SFMTA. Research involved competitive analysis of similar apps and identifying opportunities like using GPS. Prototyping and user testing helped iterate the design to improve information presentation and usability.

1. PASSENGER
Michael Iseri
General Assembly UXDi. Student Project. Winter 2013.

2. PASSENGER
About the Product:
!
Chauffeur is a mobile application catered primarily towards both the first-time
user of public transportation and those who would like to rest on much longer
trips. Chauffeur is intended for use with Bay Area public transportation and
unlike other applications of this kind, Chauffeur provides information and
notifications on how far you are from your destination.
!
About the Project:
!
Chauffeur is a student project designed with the constraint of working as a
mobile application. It utilizes the open sourced information from BART and
SFMTA.

3. PASSENGER
Research
Competitive Analysis
BART Usher
BART Runner
UBER

4. PASSENGER
Research
Competitive Analysis
!
Notification
GPS Usage
s
Real-time
Departure
Alerts
Multiple
Transportations
No
Yes
No
No
No
No
Yes
Yes
No
n/a
Yes
Yes
n/a
Yes
Favorites
Schedules
Usher
Yes
Yes
No
Runner
Yes
Yes
G Maps
Yes
n/a

5. PASSENGER
Research
Competitive Analysis
!
Opportunities!
Can use GPS to help find stations
!
Can use GPS to follow location
!
Real-time schedule updates could help ease the user
!
Estimated arrival times are useful

6. PASSENGER
Research
Analysis
!
Problem!
Primary map doesn't seem to
give an accurate depiction

7. PASSENGER
Research
Personas
!
Information!
Darren is from Sacramento and just move to San Francisco to attend
GA’s WDi program. He has never taken BART until very recently.
During his first trip, he was extremely anxious and was constantly
unsure of where he was and how much longer he had left on the
train. During longer trips between stations, he found himself
wondering if he had actually missed his stop.
!
Tech Knowledge!
Darren is 25 and constantly on either his phone, his PC, or his laptop.
He is very knowledgable of the technology of today and can easily
navigate most applications and websites. He often uses his custombuilt computer primarily to code and play computer games.

8. PASSENGER
Research
Personas
!
Information!
Justin is also from Sacramento, yet has worked the finance industry
in San Francisco for a few years now. He commutes from
Sacramento to San Francisco every day with a mixture of
automobiles and BART. He Frequently finds himself exhausted at the
end of every day and would prefer to be able to rest on the train
without fears of missing his stop.
!
Tech Knowledge!
Justin is 25 and uses his phone for work and a little bit of social
media. He also has a strong knowledge of computers and
technology and uses only high-end computers for his gaming habits.

9. PASSENGER
Research
Scenarios
!
Ideated and created different
scenarios depending the user. This is
the scenario more fitted towards the
heavy commuter. But can also be
used for beginning public
transportation users.
!
Opportunities!
Know which bus/train to take.
!
Be able to specify where you’re going.
!
Use some kind of alert or alarm system
to know where to get off.
!

10. PASSENGER
Prototype:
file:///Users/karenchong/Documents/Axure/Prototypes/pratice%20chauff/
start.html
!

11. PASSENGER
Design
Flows and paper-prototypes
!
Method!
Sketched out different frames to find how information should
be presented and laid out. Did personal run-throughs to see
how the user would navigate through the application.
!
Findings
Some maps, especially the standard BART one, is unclear
as it doesn’t provide a good scale for distance.
!
A lot of drop down menus caused both aesthetic and
navigational issues.
!
Certain pieces of information seemed useless on its own.
Parts of information should compliment each other, not fight
for dominance.

12. PASSENGER
Design
Iteration
!
Method!
Wireframed and prototyped the
application to find problems with the
design and presentation.
!
Findings!
Some pages had an information
overload.
!
Some parts were hard to see.
!
The lay-out could utilize space a lot
better to reduce clutter, while still
presenting the same (or more)
information.

13. PASSENGER
Design
Prototype Testing
!
Method!
Tested my final prototype on three separate
subjects to test flow, user-friendliness, and
the first-run experience.
!
Tasks!
Decide on a start and stop location.
!
Find a train to take.
!
“Ride” train to final stop.
!
Locate how to adjust notifications.
!
Findings!
The needed information to know when to get
off was there.
!
The application was easy to navigate.

14. PASSENGER
Thank You
Michael Iseri
mr.iseri@gmail.com
General Assembly UXDi. Student Project. Winter 2013.