UCSD Mobile App Redesign
0 likes682 views
The document summarizes the work of a student group called M.A.R.Z. in developing a mobile app for UC San Diego students. It describes their process, which included interviews, personas, prototypes, and user testing. User testing provided feedback that informed changes like allowing customization of the homepage and adding widgets. The group addressed other issues raised like making navigation and login/out easier. Their goal was to satisfy student needs through a task-based interface with relevant notifications. They next steps were finalizing their findings to share with the campus.
UCSD Mobile App Redesign
- 1. M.A.R.Z. | ASHWIN KHURANA | FABIAN RAMIREZ | JENNY LYONS | RAMYA KEDLAYA | | MICHELLE JOW | JEONGHO CHO | VINCE VOONG | ZISHAN BUDHWANI | (Still Pending)
- 2. “ ” We mean to create a UC San Diego mobile app that satisfies the needs of the average UCSD student. -M.A.R.Z. Mission Statement
- 3. Since the beginning of time… Interviews Narrowing Focus Affinity Diagramming Personas Competitive Analysis
- 4. Process Timeline Low-Level Visioning • Week 8 Storyboarding • Week 8 Initial Prototyping • Week 8 Prototype Expansion • Week 9 Prototype Finalization • Week 9
- 5. User Testing (v2.0) • Grid view vs. Creative (Bubble) view • Bubble view: • Pros: • “Looks more interesting than the standard grid format” • "Likes the personal touch" • Cons: • “Hard to direct my attention” • “Looks messy” • Grid view: • Pros: • “More familiar with it” • “Allows me to categorize” • Cons: • "Boring" • "Not personal" • Results: • There's pros and cons for both views, we can accommodate both by allowing the users to switch between different views vs
- 6. User Testing (v2.0) Surveys sent for naming scheme Provide a task, ask which is more intuitive 100+ responses “Ah, the power of social media!” Results Participants tend to choose the more “standard” wordings as opposed to colloquial wordings 21% 79% I want to check the menu for OVT Hungry? Dining 21% 79% I want to find events with free food on campus What's Going On? Events 84% 16% I want to check the hours for Main Gym Recreation Stay Active 0 10 20 30 40 50 60 70 80 90 100 110 120 6/2/2013 6/3/2013 Survey Responses
- 7. Presenting: UC San Diego Mobile PENDING DESIGN 06/02/2013
- 8. POP Demonstration You can find a live demo of our prototype at: http://tinyurl.com/ucsdmobilefilnal
- 9. “ ” Homepage menu organization not relevant to me. Problem One
- 10. Profile Selection • Customization based on type of user – current student, prospective student, faculty and staff • Relevant features correspond to the user status.
- 11. “ ” I want to customize the menu Problem Two
- 12. Customization: Drag and Drop • Drag and Drop System • Homepage Icons • Widgets • Enter the edit mode by holding the icon for 1.5 sec. • WYSIWYG: Drag and Drop on the homepage. • Trashcan holds all the removed icons • Tap to bring it back
- 13. “ ” Need to dig through the App to find the information I need. Problem Three
- 14. Task Based Tools • Tools are accessible via a task- oriented scheme • Individual tools may be favorited • Based on persona scenarios
- 15. “ ” A widget for shuttles would be helpful. Problem Four
- 16. Widgets • Quick-View into most relevant tools • Weekly Schedule, Shuttle Times, etc. • Based off breakdowns and insights from data.
- 17. “ ” I want to be notified when the balance is due. Problem Five
- 18. Notifications • Current Balance Changes • Bill due date approaching • Holds • Study Rooms (Upon Reservation) • Exam Dates (TED Integration) • Unique User-Defined Reminders
- 19. “ ” It’s stupid that I have to go to the homepage to go to another feature. Problem Six
- 20. Navigation • Navigation menu available upon left sweep • Accessible from any level within the hierarchy • UC San Diego logo navigates back home • Navigation consistent across all hierarchical levels.
- 21. “ ” Why do I have to sign in so many times? Problem Seven
- 22. Easy Log In/Out • Setting on the left navigation feature allows users to log in and out anytime throughout the application. • Avoid users sign in and out multiple times. • Save the user’s authentication locally.
- 23. What’s Left to Do Finish Paper Assemble our binder Share our findings with the Campus Web Office Feature our findings online Possibly do more user testing for user feedback.
- 24. Thank You!