1. Pre-Final Presentation
Team 7
Hazard reporting iOS app
Customer: Amelia Regan

2. Initial Problems Our audience was very limited
The elderly lived in cities that are well maintained
No audience from busy and less maintained cities (LA, NYC, etc..)
There’s no perfect way to organize all hazards found
Our categories might be too broad or too specific
We didn’t know how often the elderly would use apps on their smartphones

3. Methods We conducted user interviews to address our problems
We had meetings with our users during and after the interviews in order to narrow our scope and focus more on specific functions.
These methods allowed us to keep on track with the progression of our app
Conclusion:
We did not want to develop features in which no one found useful.

4. What we’ve done - prototype app implementation
Implemented fully functional iOS application
Log in / Sign Up feature
Swipe gestures to transitions between views
Automatic time, date, location and username tracking of submitted reports
Detailed database of registered users and hazard reports

5. What we’ve done - interviews and user tests
Focus group:
Caretakers
Mobility impaired
Visual impaired
Interview:
Learned about user habit and their needs
Documented all answers and user requirements
User tests:
Tested users to use the application without instructions
Recorded videos of walkthrough process
Dana Point Sea Bluffs

6. What we’ve done - results from user tests cont.
Caretakers:
Interview:
Willing to send report
Good at using phone applications
User Test:
Difficulties to describe the hazard in detail
Talking is prefered over typing
Interactive tutorial would be helpful

7. What we’ve done - results from user tests
Visual Impaired:
Interview:
Seldomly uses smartphones
Voice control is highly preferred
User Test:
Typing difficult, unable to complete tests
Mobility Impaired:
Not used to using touch keyboard for typing
Had trouble with smaller screen sizes

8. What we’ve done - Illustrator prototype v2
Evaluated feedback from the interviews and user tests
Decided to focus on mobility-impaired people for now after talking to customer
Produced new Illustrator prototypes to reflect some feedback
Made description optional
Streamlined categories, reducing a step from previous prototype
Added clear instructions on many screens

9. Insights
Visually impaired and mobility impaired have very different requirements for the app.
Visually impaired need everything to be voice based
Siri
VoiceOver
Tailoring the needs to both the mobility impaired and visually impaired became apparently difficult
Focus on mobility impaired
The mobility impaired had a very different idea of hazards compared to what we thought
were typical hazards
Stairs
Uneven sidewalks

10. Insights (continued)
It was difficult to differentiate between different types of obstacles such as recurring obstacles and temporary obstacles
Different obstacles were relevant to different people
This could cause difficulties as irrelevant reports may produce inefficient routes for users
We did not want to cause unneeded difficulties for our target users.

11. Insights (continued)
Figuring out the correct keywords to describe obstacles could be difficult for users
Inputting the description for obstacles could take too long and deter users from reporting obstacles they find.

12. Difficulties encountered
Drastically different needs between mobility-impaired and visually-impaired
Too many types of obstacles
Some visually-impaired users can use graphical interfaces but tend to avoid using them
Users disliked having to type a description to report an obstacle
Time consuming
Difficult for people who use english as their second language
Creating an account took longer than reporting obstacles
Keywords may help avoid descriptions

13. Decisions to be made
Decided the application should be tailored mainly to the needs of the mobility impaired
The application may have support for the visually impaired sometime in the future
Whether or not a submission should require a brief description of the hazard
During user testing some users mentioned dislike for the description requirement
Pictures are currently required
Efficiently categorizing hazards
Makes finding/submitting hazards easier
Makes it easier for users to filter relevant hazards

14. Project Timeline WEEK 8 WEEK 9 WEEK 10 WEEK 11
May 17th-20th Worked on Illustrator V.2 prototypes [Hao and Lu]
May 20th-22nd Prepared for presentation [everyone]
WEEK 9
May 23rd Presentation
May 27th Final meeting with customer
May 26th-29th Organize all gathered materials (prototypes, recordings, etc) [everyone]
WEEK 10
May 30th - June 3rd Work on final report [everyone]
June 5th-7th Prepare materials on USB drive [everyone]
WEEK 11
June 8th Final and turn in USB drive
June 9th Go over final report before turning it in [everyone]

15. SEE OUR DEMO

16. DEMO VIDEO WILL BE ADDED HERE

17. Thank you!
Any questions?