Big Code Update!

We just finished our SGM and pushed out another huge code update. :) We now have our Autogeneration playlists that we have been planning to do since our initial prototyping and needfinding! Now, when you click on the "Autogen" tab on the far right of the menu bar, it brings you to a page with a list of all genres of tracks in the universal library.

• Our "+" button on the Autogenerated tracks page, when clicked, will add all of the tracks in the given genre to the queue. This is to provide maximum opportunity for passive listening and ease of use for the driver (one-click task completion). 
• Alternatively, users can select a single track on the genre page and it will add only that track to the queue. This is to provide more flexibility for users who only want to hear certain songs 

 

In order to account for different groups of people using our app, we have also introduced group functionality. Now, when you first launch the app, you are prompted to type in the name of your group (or listening session name) so that you only get the tracks in your universal library of the other members in your group. Below, you can see screenshots of both the host and guest views typing in the names of the groups. 

Code Update!

It has been a while since our last update, but we've been working hard! We had another SGM yesterday and Jay was very happy with all the progress we have made.

• We did a complete overhaul of our code to no longer use multi-peer technology, but instead rely entirely on our Parse database - this has solved a lot of our initial issues, and the app is now working a lot more reliably
• Queue is now sync'd on everybody's phone (whether user is signed as guest or host)
• As soon as a song finishes, it is removed from the database and updates each song's metadata as soon as the previous song finishes
• The host's view updates the scrobber bar to show the progress in the song 
• The universal library now pulls and shows all local songs from each user's phone

We are still running into some threading issues, which we hope to figure out this week. We are also currently working on a draft of our contract of deliverables to send to the Audi liaisons and the teaching team. 

Small Group Meeting #7

Here are the notes from our meeting:

• next week: new hire assignment
• put out some media characterizing the culture - about us as a team
• email our ideal candidate description to teaching staff
• make a 5 minute pitch next Thursday during LGM to a hypothetical candidate
• 2 things to do:
• think about who we want to hire
• e.g. these are the last 5 minutes before they walk out
• if we could hire two people on our team, what kind of people do we want
• graphic designer
• sales person
• alum will come in and play the role
• make the case for why they should work here
• do more user testing - observe the ideal users of our software

We also had a reflection of our performance as a team last quarter.

• what did we do best?
• what do we need to do better?
• what do we want to accomplish this quarter?

Below is our self evaluation:

How much have we taken advantage of the following?	Self rating (0 = not at all, 9 = as much as humanly possible)	How much can/did this help our project? (0 = no help, 9 = huge help)	Notes
Agile programming methodologies (sprint concept, frequent short status meetings)	8
Rapid prototyping	6
If your team's maximum capability as a unit all working together is 10, what kind of output score would you say you had in Winter? What do you feel like is a realistic expectation for this score given that unlike in the real world, not everyone is primarily committed to this project over other professional responsibilities?	7	N/A	There were some lulls. Really good with a deadline.
Group dynamics theory/practice (Did you use these to resolve conflicts, reflect about how to work better, etc?)	5
Tools - Source control (branching, code review)	9
Tools - Issue tracking (e.g., Github)	6
Tools - Collaboration (Blogs/FB/Google groups/group messaging etc) to enhance internal and external communications	9
Use of media (photos, video, etc.) to capture IP, team culture and to generally communicate effectively	7
Meeting with human beings who are likely targets for your software	4.5
Observing use of your software in person	N/A		Increasingly important
Observing use of your software via analytics	0		Valuable for this quarter
What did we do best?
What was our weakest point?
What do we want to accomplish this quarter?