EasyDrive Jaylen Van Orden Paul Marshall Mark Shamis Sandeep Lukose

Overall Problem and Solution Most people find driving a necessary evil People need mobility, but the details of driving are a pain: – Traffic laws – Congestion – Need to pay attention So how about a car that drives itself?

Overview Tasks Evolution of Design Final Design Demo Summary

Task 1 - Summon the car You are walking along the beach when you twist your ankle. There is a road nearby. Open your EasyDrive Mobile App and summon your car, then track its position as it comes to pick you up. Free your mind car! You don't need to care where the car is

Task 2 - Search You want to go to Bob’s Gadget Emporium. You have not been there before. Drive to Bob’s, then direct the car where to park after you get out of the car. Users will drive places; it’s what they do Will probably be most-used feature

Task 3 - Favorites You want to drive to your usual KFC, which is saved in your favorites. The other thing users do: go to their favorite haunts. – Work – Food – Friends

Task 4 – Schedule You’re planning a Fourth of July trip. Today is June 12th. On July 4th, you will drive to The Luxor Hotel in Vegas. Plan things ahead of time – Don’t scramble for addresses at the last minute Create trips for the things you usually do: commute from home to work, etc.

Task 5 - Emergency You’re driving down the road when you have a sudden pain in your chest. You think it’s a heart attack; go to the nearest hospital while driving as fast as possible. This is an emergency. Bad things happen. Emergency mode will break traffic laws.

Design Evolution: The Home Page The home page layout changed several times – Final result: simple, short words – Most common features on top – 6 main buttons, up from 4 Participants couldn’t always find “Search”

Design evolution: Trip Planning Trip planning was hard to do! Changes: make a simple trip easy Participants thought “Trip Name” entry was “Trip Destination”

Design evolution: Confirmation Dialogs User says: DO THAT. – “Are you sure you want to DO THAT?” Participants said we were trolling them We added more info to make it useful: – Distance and ETA to destination, address Trolling: User simply repeats Not Trolling: Useful information, not simple repetition

Demonstration Things left out: – Most of Trip Planning Headless driving – “Apps” (movies, internet, etc.) – Preferences Driving style (fast/slow) Permissions: Drivers vs. Cargo – Maintenance alerts

Lessons Learned the Hard Way: Studying the Participants Real people do weird things – Different people do different weird things We know our interface too well to test it Make it easy, people don’t care enough to read it

Lessons Learned the Hard Way: Designing is hard! Bikeshedding is bad – Everyone has an opinion on what color it should be Focus on common features, do corner cases later Drawback to prototyping: too hard to prototype? Change the design! – Both paper and interactive prototypes Frameworks == easy interactive prototype – …if we did this twice. There’s some ramp-up.