This document summarizes the development process of an app called Grub Grabber. It describes conducting interviews with students to understand their dining needs and create user personas. It then outlines designing paper prototypes that were tested with students and improved based on their feedback. The document discusses collaborating with another student group and plans for future work, including more prototype testing, design iterations, and implementing recommended features like directions, randomization, and privacy settings.

1. One Fateful School Day ...

2. Grub Grabber
TEAM SE7EN

3. Last time, on Grub Grabber...
THE PROBLEM

4. Last time, on Grub Grabber...
Interviews
❖ Each conducted 4~8
interviews
❖ Students from all
backgrounds

7. - James Bond
Significant Quote about
Something relevant to our
research and makes a clear
point about our project
“The review is more important
than the pictures.”
- 3rd Year Transfer

8. - James Bond
Significant Quote about
Something relevant to our
research and makes a clear
point about our project
“I eat at places only near
my classes.”
- 4th year off campus

9. User Personas
John Muir
Environmental
Studies Major
4th Year
Lives Off-campus
Has Car

10. User Personas
Background Goals/Needs Problem

11. What we’ve done since then
❖ Case Flow & Storyboard
❖ Wireframing & Design Choices
❖ Paper Prototype
❖ Paper Prototype Testing
❖ High Fidelity

12. Visioning: Early Stages
Home Screen: Log-In
❖ Filters:
Budget, Location, Transportation
Randomizer Option
Next Screen:
❖ Map
❖ Eatery names
❖ Directions based on transportation
❖ Extra Filters: Time and ratings

13. Visioning (Early Stages)

14. Visioning: Final Stage
Map home screen
Filters
❖ Distance
❖ Location (on and/or off campus)
❖ Budget
❖ Got rid of transportation
❖ No randomizer
Balloons on map
❖ Representing eatery locations based
on filters

15. Change in emphasis
❖ Filters Map
Facebook integration
❖ Mandatory FB sign-in Optional FB sign-in
Sliders
❖ Continuous slider Discrete steps
Design Changes

16. Key Features
OUR SOLUTION

17. Paper Prototype: V 1.0

18. Paper Prototype: V 1.0

19. Paper Prototype: V 1.0

20. Paper Prototype: V 1.0

21. Paper Prototype: V 1.1
Previous
V 1.0
Updated
V 1.1

22. Paper Prototype: V 1.1

23. Paper Prototype: V 1.1

24. Paper Prototype: V 1.1
Previous
V 1.0
Updated
V 1.1

25. Paper Prototype: V 1.1

26. Paper Prototype: V 1.1

27. Paper Prototype: V 1.1

28. Paper Prototype Interviews
Limited Amount of Time
Test around PC
❖ UCSD student population
Walk us through & talk aloud
Still confused? → Scenario time!

29. Paper Prototype Interviews
User Suggestions
❖ “Open Now”
❖ Personalize
❖ Menu
❖ Deals section
❖ Randomizer
❖ Iconography

30. Collaboration with 121 Group

31. Collaboration with 121 Group
❖ Created a low fidelity wireframe
❖ Began visioning with Tyler
❖ Discussed “What is possible?”
❖ Started working on a high fidelity wireframe

32. Collaboration with 121 Group

33. Future Directions
More Prototype Testing
❖ What works? What doesn’t work? Does our application solve the
problem?
More Design Reiterations
❖ Implement feedback from interviews & design changes, to test again
More Collaboration
❖ Implement all features with 121 instead of prioritizing due to time
constraints

34. Paper Prototype Feedback
Iconography
❖ Is it intuitive?
❖ Do users know what each icon
means?
❖ More iconography testing

35. Future Directions: Prototype Feedback
Randomize
❖ Similar to Google’s “Feeling Lucky?” feature, for users who want to
explore new places
Directions
❖ How do I get there? Walking? Bus? Car?
IOS vs. Android
❖ Swiping to go backwards VS. pressing a button

36. Future Directions: Prototype Feedback
Privacy Settings
❖ Who can see my reviews? Whose reviews appear on my
feed?
Tutorial
❖ Does our application require a lot of learnability?

37. Future Directions: New Features
Fully Functional Facebook Integration
❖ Personal recommendations to friends
❖ Number of recommendations by friends
❖ How to add a review
❖ When does the Login prompt appear?

38. Thanks for
listening!