Introduction• Vision: • To create a product which will make it easier for anyone to listen to and share music. Through wi-fi, it will be possible to upload music from your own phone to be played through any speaker set up.• Target audience: • Music enthusiasts. • Party hosts.• Video Demonstration: • http://www.youtube.com/watch?v=dtgAA0SSXqY
Description• This is an input you would put into your speakers that can play music from multiple sources.• Through an FTP server communication, a Android App will be able to upload songs to a database on the Raspberry Pi. Once logged into the ftp server it is hosting, one can vote for the song they want to hear next.
Contribution & Differentiation• Dakota was in charge of the development of the Android app.• Simon was in charge of the hardware and software development on the Raspberry Pi.• What is different? • Most wireless music players are sold as a complete set with speakers. Our product will be able to connect to any 3.5mm jack to any input audio device. This in turn will allow our product to be much cheaper so the user may make any of their speakers a wireless music player. • Multiple people can upload their music to this speaker.
Retrospective• This project was achieved through agile project management (SCRUM).• As shown here thereit shows the issues chart
Retrospective• The original product idea was achieved. Most of the intended goals have been fulfilled.• The final product was just a proof of concept though it is fully functional there is still much to work on.• Lessons learned: • Time management. • Nothing ever goes as planned when making a new product. • It is very had to prepare for what can go wrong.
Retrospective cont’d• Roadblocks: • Had to learn new coding languages in 10 weeks. This includes JAVA and PERL. These courses were not taught in our curriculum. • Raspberry Pi has a weak sound driver. Possible solutions is to put a external sound card through USB. • RIT’s wi-fi network is very restrictive. There are just so many restrictions on the network. There was much struggle getting the Raspberry Pi to work on the RIT wi-fi network.
Retrospective cont’d• If I had to do it again.. • I wouldn’t change a thing in terms of my decision for my product. • The only issue I had was I hoped we had more than 10 weeks to work on this. Time management was very crucial for this project. Procrastination is the enemy. • SCRUM agile development does not work as well in teams of 2 than it would within larger groups. • Before we started all of this I wish there was a introductory or maybe more tutorials on programs and sites we had to use • ie: Microsoft Project/JIRA/Confluence.
Future work• For more development, an option would be to make this completely embedded and add a RTOS instead of using the Raspberry Pi.• Use an application server along side a database for all the data. This will help with timing issues between the script and app.• Apply a wi-fi detect approach so one does not have to manually pull the IP address of the ftp server. This way we can truly make this product a plug and play.• Create a case for this device.