A few insights

Oren commented on our idea to include a touch screen below the map. 

• The screen below/beside the map is a turnoff. Screens are out, everybody use them, touch is everywhere - Wood or 3d printed map. As large as you can.
• LEDs for data feedback, and you can add 7-segment text display, like a ticker, to show the song name etc. 
• More statistics info - too technical and not poetic like the rest of the experience, but if you insist - it should be on the users mobile phone, like augmented reality above the map, I direct my phone to an area on the map and see the stats visualization on my little screen. That way, you do not need to bring the screens. But the stats is an overkill. Priority 4...
• Dive deeper into the flow details.
• How do I tag to an area, what if I'm between areas, how do you deal with GPS uncertainty, what feedback do I get for tagging, what incentive do I have to contribute.

We decided not to include touch screens for now. 

Lesson Notes

These are our action items and feedback:

Oren's feedback:

• Oren pictures the map as analog and made of old fashioned wood, with multiple metal jacks per area. 
• We agreed on the map's scale- blocks/neighborhoods/squares within a single city. 
• We need to decide if we want the experience to be targeted at a single user or multiple users.
• We need to somehow indicate that a specific location contains content (songs), an LED is recommended.
• Regarding our flow- we have two parts, data collection (this is the part we already have) and the listening experience.
• Touching the wall doesn't have the same affordance as jacking in with your headphones.
• We should thoroughly research similar projects.

Orad's feedback:

• We need to decide if we are targeting our project for the street or for a museum/show. We decided on the street.
• Statistics are secondary to the listening experience. We should focus on listening first, and display the previous ~10 played songs as a first step.
• Physically connecting headphones to Florentin (for example) is a much stronger experience than putting your hand on it and blocking it from your sight, and has a better affordance.
• The application that enables you to listen to the songs on your phone is secondary to the experience and should not be focused on.
• We should focus on the map and be very loyal to our definition of the experience: "Connecting to the musical world of people in our environment" 

Production: 

• We talked about a secondary screen that will display additional information below the map, we still haven't decided if it needs to be a touch screen (probably ideally), a tablet or an LCD.
• We need a PC/laptop that controls the screen
• Azure user- we've sent a mail to Noa regarding this
• We will need the map to be printed on canvas/wood, we still haven't discussed size.

While working on the flow and user experience ,we've encountered some issues:
We like the analog "operator" style jacks idea, but think it's gonna be problematic because of the following reasons:

1. If we go with an analog map, it means we can't display complex information on it. We are limited to the jack connection, and an LED that informs the user of new songs entering the queue, and maybe some indication of the number of songs in the specific location's queue. 

 2. This is the implication #1: If we think additional information about the songs is important, such as: the song's name (very important in our opinion), the list of songs in the queue, and additional statistics about listening patterns in a specific location, then an additional display is needed. That was the direction we were going in, a secondary screen below the map that will contain that information.

However, if we want the experience to support multiple users, we're having a hard time visioning the design. Will we have n screens (tablets?) for n locations? Will we have a single display that will automatically toggle between locations or display all locations at once? Will we allow only a single user to control the screen and decide what's showing?
Ideally, we would have combined a touch screen with the jacks and displayed the additional information on the map itself as popups next to the location. Although, we think that touch screens will ruin the magical experience of our product.

Meeting with Noa

Participated: Noa, Sharon, Itamar, Ran, Noam & Omri.

Mostly discussed ideas for changing the user experience.
The main concepts that endured throughout the meeting:

• Peeking into the musical world of people around me / around specific locations
• A concept/metaphor of an urban radio station (or playlist generator)
• Connecting the entire body to the experience (either by pressing a button on a map or by placing an NFC device)

These issues are still under discussion.

Meeting Summary

Following a short start-of-semester class, we had a meeting with Noa and Guy and discussed a new metaphor along with major advancements in CS front.

Participated: Guy, Noa, Sharon, Itamar, Ran & Omri

After discussing the comments received from Ruth (Microsoft), talked about a new type of user experience. Most prominent topics were a tactile listening experience (such as AudioVersum's experience) and maybe using a map showing the locations of StreetBeat devices. Pressing on the map causes the music collected at the respective location to be played in a headset.
The base of our metaphor is listening to the sounds of the ocean through a sea-shell. 

Comments on the Project from MS Representative

Feedback from Ruth, part of the design expo competition:

In a world where nearly everyone is listening to music on their smartphone, why not see what everybody is listening to? The StreetBeat is public art display that senses what music is played near it and visualizes this music for the benefit of passers-by. It allows anyone to leave his or her own mark by having his music visualized as well as exploring and experiencing new music, played by others. To experience such music, you don't even need a smartphone, just plug in a pair of headphones. This isn't to say you can't take this music home on your phone. Beyond these, StreetBeat also shows the musical DNA of its location, be it a street, a neighborhood, or a town square. This is done by integrating data by artist or genre to show and display what's trending and who's popular.Blog: http://streetbeat2.blogspot.co.il/

1. Getting the musical pulse of a place is great. I saw that you got enough feedback on feasibility and copyright issues, so I’m not going to get into that

I want to focus on the installation itself. I think you should explore it more.

2. How can you make it more inviting? More playful? What would make someone stop and actually listen? You are creating something dynamic and entertaining. Your project is not about utility – it’s about fun and voyeurism. Can you reflect that in your design?  What if you had to have physical contact to hear the music, to feel the music? Laurie Anderson had a brilliant installation called the headphone table - you put your elbows in 2 little dimples on the surface, cover your ears and then your body would become the speakers through your hollow bones and you could hear the music. It was a very powerful thing to experience, but the other powerful thing was to see other people doing it, and watch them. What is the performance aspect that you are creating with your installation? What do you want your users to feel? How would you like them to react?

Another aspect of an installation is what do you get from various distances – what is the experience of someone on the other side of the street? What is the experience for someone passing by? For someone who touches it?I would suggest to you to rethink the experience. You can find some inspiration in places like ars technical (and others). Look at this image of a sound installation– http://www.audioversum.at/It’s simple, intriguing, there’s a performance element, an intimate experience element … it is a technical product, but doesn’t scream “technology”. This is just an example, and probably there are thousand others – just trying to open your mind to examine the experience you are trying to createMore stuff to consider:

1. You want to have it be outside, and you’re using light sequences as your main thing. Would work at night, but what happens during the day in the israeli sunlight?
2. Have you thought about directional audio that creates “sound bubbles”?  That way your users will be able to hear the music without headphones and without “polluting” the street with music [http://www.holosonics.com/?m?]
3. But what if it’s only me around? Can I play back yesterday? Or my birthday?
4. When playing the music on someone’s phone, instead of a youtube video, it might be more interesting to create connection to the location and show footage on what was happening there when this music was captured

Enough talk, now go and make a memorable, emotional and beautiful piece of art. 

Good luck!

Hangout Summary

Participated: Itamar, Ran, Noam, Sharon, Omri.

First on the agenda, Ran and Noam reported on progress from CS side:

• App:

1. Android app has been consolidated into single app
2. It can now identify the song being played on the device, regardless of what player initiated the playback. This makes the app player agnostic and is a huge boost of user experience as it frees users to choose their own player (instead of forcing them to use ours)
3. The app only needs to be converted to a service

• Cloud:

1. Website and WebApp already exist on MS Azure infrastructure.
2. DB (MS SQL?) is also set-up for the project
3. Basically all components should exist
4. REST API needs to be implemented for communication between the components of the system

Next up Sharon and Itamar started a discussion about the user experience (following comments received from Microsoft. Bottom line that was agreed upon was that the "barrel" design should be forsaken for another one. 
It was suggested to use a "seashell" metaphor: users can listen to music which was collected at other locations using headphones installed in the device (which will retain the data visualization aspect probably via a screen).

This is to be discussed with Guy/Noa tomorrow at class.

App Developments

Ran is keeping busy this semester vacation and has seriously bumped up the current apps' functionality.

See it live:

Ran presenting the functionality of the newly developed.
In here we can a list of songs on the player (currently simulated, later on to be delivered from server) and when Ran chooses a song, it is played, with its' respective video from YouTube.