1. Take Me There Drew Bregel Joe Woo Joel Shapiro Marianne Goldin YOUR PUBLIC TRANSIT GURU CSE 441 Winter 2009

3. When is my next trip possible? What’s the address? Can I get to the stop in time? 3

4. Did the 75 go by already? How do I get there from here? Where is the time table? 4

5. Planning the same trips, again Scheduled timetables versus reality Info sources that aren’t mobile ready 5

6. Predict your destinations Real-time transit data Destination focused route planning 6

7. Easy –Find when the next bus home arrivesModerate –Plan a trip to a favorite destinationDifficult –Plan a trip to a new destination 7

8. 8 Frequent trip At work Time to go home

9. 9

10. 10

11. 11 Go to favorite bar Not normal time

12. 12

13. 13

14. 14

15. 15

16. 16 New destination Needs to search

17. 17

18. 18

19. 19

20. 20

21. 21

22. 22

23. 23

24. 24

25. 25

26. Task Refinement UI Design Evolution Evaluation & Usability Results Future & Related Work 26

27. First Task: Reduced from four screens to two. 27

28. Second Task: Changed from planning new trip to retrieving a saved trip. 28

29. Third Task: Changed from “tagging” conditions of a trip to planning a new trip. New trip screens reduced from six to four pages in Take Me There vs. MyTransitTracker. 29

30. Planning a trip in MyTransTracker Planning and taking a new trip in Take Me There 30

31. When the scope of the program changed, so did the tasks –Tagging proved to be a confusing idea for users. Why our three final tasks? –They represent the final and most important three features of the program. 31

32. The Home Screen tells users where they are and what trips they might want to take. –Trips are based on their habits at said time. 32 MyTransTracker “Home” screenTake Me There “Main” Screen

33. MyTransTracker focused on multimodal transportation. Didn’t take into account time well in planning screens.

34. 34 Take Me there asks users in plain English what they’re looking to do. Ease of use was priority in new trip planning, tends to be overcomplicated.

35. Web-Based Usability Study –23 completed testing –80% used the same routes most of the time Emulator-based Usability STudy –Median age = 22 3 males, 2 females –All used web-based transit applications 3 of 5 used mobile applications –Users used busses on average 6.8 times/week 35

36. Users were generally impressed with real-world applications. Confused by terminology –Tabs were changed from “Home,” “New,” “Saved” to “Main,” “Plan Trip,” “My Places.” Confused by icons and labels –Clear separation of buttons vs. text was implemented. 36

37. Static Location Data –Jim’s house, work Current Location Information –GPS Information –Map and Direction Information Transit Information –Bus Status –Trip Planning Destination Classifiers –Track and learn users travel patterns 37

38. Google maps mobile Location information Trip planning Map content Detailed trip information One Bus Away (.org) UW CSE, Go Dawgs! Explore your neighborhood Back end ready to go now Starting to build a mobile app 38

39. Predict your destinations –Plan once, travel many Real-time transit data –Just what you need Destination focused trip planning –Finding a way to get you there Coming soon to you –Putting all the pieces together 39

40. 40 Thanks to: Susumu Harada James Landay

41. 41