Top Banner
TEAM ERIS: MOBILE AND GPS INTEGRATION
28

TEAM ERIS: MOBILE AND GPS INTEGRATION. WHY HFID WAS WORTH OUR TIME Balance simplicity with functionality Don’t design for edge cases Communicate affordances.

Dec 20, 2015

Download

Documents

Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: TEAM ERIS: MOBILE AND GPS INTEGRATION. WHY HFID WAS WORTH OUR TIME Balance simplicity with functionality Don’t design for edge cases Communicate affordances.

TEAM ERIS:MOBILE AND GPS INTEGRATION

Page 2: TEAM ERIS: MOBILE AND GPS INTEGRATION. WHY HFID WAS WORTH OUR TIME Balance simplicity with functionality Don’t design for edge cases Communicate affordances.

WHY HFID WAS WORTH OUR TIME

Balance simplicity with functionality

Don’t design for edge cases

Communicate affordances through clear UI

Page 3: TEAM ERIS: MOBILE AND GPS INTEGRATION. WHY HFID WAS WORTH OUR TIME Balance simplicity with functionality Don’t design for edge cases Communicate affordances.

Simplify the GPS interaction via smartphones

+

Page 4: TEAM ERIS: MOBILE AND GPS INTEGRATION. WHY HFID WAS WORTH OUR TIME Balance simplicity with functionality Don’t design for edge cases Communicate affordances.

PERSONAS

Page 5: TEAM ERIS: MOBILE AND GPS INTEGRATION. WHY HFID WAS WORTH OUR TIME Balance simplicity with functionality Don’t design for edge cases Communicate affordances.

RACHEL + ANN

Page 6: TEAM ERIS: MOBILE AND GPS INTEGRATION. WHY HFID WAS WORTH OUR TIME Balance simplicity with functionality Don’t design for edge cases Communicate affordances.

ALEX

Page 7: TEAM ERIS: MOBILE AND GPS INTEGRATION. WHY HFID WAS WORTH OUR TIME Balance simplicity with functionality Don’t design for edge cases Communicate affordances.

ISSUE #1:MULTIPLE CARS

Page 8: TEAM ERIS: MOBILE AND GPS INTEGRATION. WHY HFID WAS WORTH OUR TIME Balance simplicity with functionality Don’t design for edge cases Communicate affordances.

MULTIPLE CARS

Only allows linking to 1 car

1 screen for all settings

No clear distinction between address highlighting and car email

Page 9: TEAM ERIS: MOBILE AND GPS INTEGRATION. WHY HFID WAS WORTH OUR TIME Balance simplicity with functionality Don’t design for edge cases Communicate affordances.

MULTIPLE CARS

Page 10: TEAM ERIS: MOBILE AND GPS INTEGRATION. WHY HFID WAS WORTH OUR TIME Balance simplicity with functionality Don’t design for edge cases Communicate affordances.

MULTIPLE CARS

Page 11: TEAM ERIS: MOBILE AND GPS INTEGRATION. WHY HFID WAS WORTH OUR TIME Balance simplicity with functionality Don’t design for edge cases Communicate affordances.

Balance simplicity with functionality

Page 12: TEAM ERIS: MOBILE AND GPS INTEGRATION. WHY HFID WAS WORTH OUR TIME Balance simplicity with functionality Don’t design for edge cases Communicate affordances.

ISSUE #2:MULTIPLE DESTINATIONS

Page 13: TEAM ERIS: MOBILE AND GPS INTEGRATION. WHY HFID WAS WORTH OUR TIME Balance simplicity with functionality Don’t design for edge cases Communicate affordances.

SCENARIO: ALEX

Page 14: TEAM ERIS: MOBILE AND GPS INTEGRATION. WHY HFID WAS WORTH OUR TIME Balance simplicity with functionality Don’t design for edge cases Communicate affordances.

INITIAL SOLUTION: DESTINATIONS QUEUE

Page 15: TEAM ERIS: MOBILE AND GPS INTEGRATION. WHY HFID WAS WORTH OUR TIME Balance simplicity with functionality Don’t design for edge cases Communicate affordances.

RESPONSE FROM USERS

• “When would I need to have multiple destinations programmed in my GPS?”

• “What happens to the queue when I turn the car off?”

• “Couldn’t I just send over my next destination after I’ve arrived at my first?”

Page 16: TEAM ERIS: MOBILE AND GPS INTEGRATION. WHY HFID WAS WORTH OUR TIME Balance simplicity with functionality Don’t design for edge cases Communicate affordances.

REVISED DESIGN: NO ADDRESS QUEUE

Appears WHENEVER you send over an address from your phone

Page 17: TEAM ERIS: MOBILE AND GPS INTEGRATION. WHY HFID WAS WORTH OUR TIME Balance simplicity with functionality Don’t design for edge cases Communicate affordances.
Page 18: TEAM ERIS: MOBILE AND GPS INTEGRATION. WHY HFID WAS WORTH OUR TIME Balance simplicity with functionality Don’t design for edge cases Communicate affordances.

Don’t design for edge cases

Page 19: TEAM ERIS: MOBILE AND GPS INTEGRATION. WHY HFID WAS WORTH OUR TIME Balance simplicity with functionality Don’t design for edge cases Communicate affordances.

ISSUE #3:ADDRESS HIGHLIGHTING

Page 20: TEAM ERIS: MOBILE AND GPS INTEGRATION. WHY HFID WAS WORTH OUR TIME Balance simplicity with functionality Don’t design for edge cases Communicate affordances.

Browser plugin

Page 21: TEAM ERIS: MOBILE AND GPS INTEGRATION. WHY HFID WAS WORTH OUR TIME Balance simplicity with functionality Don’t design for edge cases Communicate affordances.
Page 22: TEAM ERIS: MOBILE AND GPS INTEGRATION. WHY HFID WAS WORTH OUR TIME Balance simplicity with functionality Don’t design for edge cases Communicate affordances.
Page 23: TEAM ERIS: MOBILE AND GPS INTEGRATION. WHY HFID WAS WORTH OUR TIME Balance simplicity with functionality Don’t design for edge cases Communicate affordances.

1st paper prototype

2nd working prototype

Single checkbox

Yellow highlightingLogo button

Button encompasses address and logo

Checkbox with explanation and sample image

Page 24: TEAM ERIS: MOBILE AND GPS INTEGRATION. WHY HFID WAS WORTH OUR TIME Balance simplicity with functionality Don’t design for edge cases Communicate affordances.

EXPERIMENT1 2 3

4 5 6

Page 25: TEAM ERIS: MOBILE AND GPS INTEGRATION. WHY HFID WAS WORTH OUR TIME Balance simplicity with functionality Don’t design for edge cases Communicate affordances.

EXPERIMENT

Page 26: TEAM ERIS: MOBILE AND GPS INTEGRATION. WHY HFID WAS WORTH OUR TIME Balance simplicity with functionality Don’t design for edge cases Communicate affordances.

EXPERIMENT1 2 3

4 5 6

Page 27: TEAM ERIS: MOBILE AND GPS INTEGRATION. WHY HFID WAS WORTH OUR TIME Balance simplicity with functionality Don’t design for edge cases Communicate affordances.

Explanation text: Communicating affordances through language

Button appearance: Communicating affordances through visual cues

Page 28: TEAM ERIS: MOBILE AND GPS INTEGRATION. WHY HFID WAS WORTH OUR TIME Balance simplicity with functionality Don’t design for edge cases Communicate affordances.

KEY TAKEAWAYS

Balance simplicity with functionality

Don’t design for edge cases

Communicate affordances through clear UI