Design Concept: Navigation during a call

Transcription

1 Design Concept: Navigation during a call Anna Kaufman 15 May 2012

2 In-call navigation: the problem Obviously, users shouldn t be talking on the phone while driving, because it s not safe to be distracted while on the road But, the reality is that users still do drive and talk at the same time. So the real question becomes: how can we design the driving experience to be a simple and safe as possible while the user is talking on the phone?

3 In-call navigation: Windows Phone UI Current Windows Phone UI does not allow for navigation during a call Once there is an incoming call, as far as the user is concerned, the navigation is basically stopped because the navigation UI is in the background and the voice navigation is blocked by the call audio. There is no easy way to get from the call screen back to the navigation, and trying to navigate through the Windows Phone UI to get back to the navigation becomes too complicated of a process to do while the user is driving.

4 In-call navigation: users Travelers: In an unfamiliar place, so route guidance is most important. But they also are unfamiliar with speed, traffic cameras, road work, lane configurations, etc. Less likely to take calls or become focused on a phone conversation since they are aware that they are in a foreign place. Commuters: Going to a frequently visited place (usually home or work), so they know the route they are driving when to turn, which lanes to use, etc Since their route is habit, easier to loose track of things like speed limits and traffic cameras while on a call Local seekers: Familiar with the general city they are driving in, but going to a new location, so route guidance becomes increasingly important as they near their destination. More familiar than travelers with speed limits, traffic cameras, street names, road work, etc but not as familiar as commuters. Likely to take calls while driving because they feel familiar enough with the area to allow themselves to be distracted by a phone call.

5 In-call navigation: focus on local seekers Likely to be the most easily distracted group, since they have some familiarity with the area they are driving in, but don t know how to get to their specific destination Need lots of help with driving guidance both with driving directions as well as other information like speed limits, traffic cameras, road work, etc

6 In-call navigation: a user journey Let s take a look at a journey for one of these local seekers. First, with the current Windows Phone UI, and then going back again with how the journey should work

7 Current user journey Meet Bob. Bob is on his was to a meeting with a very important client in another part of the city. Since he s never been there before, he needs help finding his way to their office.

8 Current user journey So, Bob pulls out his trusty Nokia Lumia, opens the Drive application and enters the address of his client s office. He then starts the navigation and begins driving.

9 Current user journey While Bob is driving to the client meeting, his wife calls. Bob answers the phone and starts having an involved conversation with her.

10 Current user journey Bob s wife has a lot to tell Bob, so they talk for quite awhile. Bob is so engrossed in the conversation, that he doesn t realize that his phone has stopped giving him driving directions. Bob drives right past the client s office without even realizing it.

11 Current user journey Once Bob gets off the phone with his wife, the navigation returns to the foreground, and Bob finally realizes that he s driven past his destination. Bob is very frustrated at his phone for stopping the driving directions without alerting him to that fact.

12 Improved user journey Now, let s start this story over again. Again, here is Bob, at his office and needing to go to an important client meeting at an office he doesn t know how to get to.

13 Improved user journey Again, Bob pulls out his trusty Nokia Lumia, opens the Drive application and enters the address of his client s office. He then starts the navigation and begins driving.

14 Improved user journey And once again, while Bob is on his way to the client meeting, his wife calls. And again, Bob answers the phone and starts having an involved conversation.

15 Improved user journey But this time, once Bob answers the phone call, his phone continues giving him driving directions right from the call screen. Bob is able to have the conversation with his wife AND still is giving the driving directions of how to get to the meeting.

16 Improved user journey Because his phone still gave him directions to his destination, Bob arrives at the client s office on time to the meeting, without any of the frustration he experienced in the first scenario. And this time, the story has a happy ending.

17 In-call navigation: design considerations Make sure the user still has access to the important call functionality Allow navigation to continue running, without interrupting the call Show only the most essential information since navigation only uses a portion of the screen and help the user maintain focus on driving: warn for things like traffic cameras, when the user is over the speed limit, and if there is any unexpected traffic or road work ahead Display navigation information as simply and clearly as possible to avoid as much driver distraction as possible Create alternative cues for the user since voice navigation is not used during a call

18 In-call navigation: competitors Android: Google navigation continues playing voice guidance and phone call audio, so can be very distracting and difficult to hear either one. iphone:?? (would add if more time) Other?? (would add if more time)

19 In-call navigation: design concept

20 In-call navigation: design elements call area navigation window Street name for next direction Graphic for next direction Distance until next direction Remove extra call functionality that shouldn t be used while driving (ex. keypad and conference call) Icon to turn voice navigation on/off Distance and time until destination

21 In-call navigation: functionality Tapping in the navigation window reopens Drive app (call continues in the background) Tapping in the call area (other than the buttons) would open the normal full screen call UI Tapping on voice icon turns the voice navigation back on (toggles between on and off) Could have an auditory beep similar to when receiving s or texts to indicate when the next direction is close Direction icon could flash when next direction is close (for example, at 500 meters could flash once per second, at 200 meters could flash twice per second, and at the direction could flash three times per second)

22 In-call navigation: additional views speed camera warnings lane guidance road work alerts speed limit warnings

23 In-call navigation: portrait mode Navigation window is square, so the size remains the same in both landscape and portrait modes

24 In-call navigation: additional considerations If the user goes taps the navigation window to go to the Drive app, how can he get back to the call screen? Or, some way to end the call from within the Drive app? On the flip side, if the user goes into the full screen call, how can he get back to the in-call navigation view? Would the user want to go back? Would it be safer to remove all the call buttons, since in many countries the user isn t allowed to touch the phone at all while driving? Need to study when/how long to show speed limit, traffic camera, road work, etc and make sure they don t interfere with the navigation directions (or, in the commuter case, maybe they should take precedence)

25 Questions?

26 Thank you.