During class we decided on several issues and received help from Oren, Oran and Orad.
- We agreed that we have 2 powerful parts to our experience: The device and the app.
- Suggested to separate between a "tourist" use case and a "resident" use case.
- Suggested to try and get a sponsorship from an audio importer.
- Suggested to add a physical switch at each output jack to allow users at the device to toggle between songs, increasing their perceived control.
- Started discussing what is a good way to divide the city (and therefore be able to define each area in the division, musically).
- Suggested another form of user study: stopping people with headphones in the street and ask them what they're listening to.
- Discussed adding a critique of YouTube's licence agreement by adding a split-screen of videos or any other form of video display.
- Decided that demographics should be collected, but we still need to decide on the specific measures.
- Suggested adding a button to toggle between 2 songs at each output of the map.
- Decided to have another paper-prototype study, with a better model of our product.
Next steps are:
Communications:
Add music to App interaction flow
Prioritize all the features
Correct flow according to Orad's comments
Map design - MPOIs (Musical Points Of Interest), Switches, 7 segment display.
Decide which measures to display on the map.
Application mockups
CS:
Decide on core technologies for actual device
Package App for distribution (depends on reactivating Azure server)
Add tactile/notification feedback to App
Check battery consumption of the App
Remind Oran that we need Android boards and ADKs/IOIO boards
Psychology:
Revise theoretical background + add element of control to it
Think about possible demographics for control & get user feedback for it
And:
Design and implement second paper-prototype study
Perform street study (As Oren suggested).
No comments:
Post a Comment