Introduction
There are plenty of places on the internet to post your recorded music as a showcase and have people buy it and/or comment on it. There are also some scattered forums on the web where musicians can join and discuss the best hardware to use, the best software to use and to get help on problems they are having. But there is currently no online site where musicians can visit to post up their ideas as music files and have it criticised constructively, receive support from other musicians for issues with hardware, software and techniques, or a place to visit where other musician’s posts can give you inspiration and ideas.
Description
Sqeakr will be a social network for musicians that will give them a place to put their ideas, like a blog, a place to ask questions and seek advice, like a forum, and a place to meet similar minded people with the same tastes in music.
Sqeakr will be like a social network, blog and forum all in one, but it will be a mix of the parts of each that are best for musical collaboration, keeping the scope as focussed as possible to keep the site usable and the deadlines reachable. The final application should help fledgling musicians find the right tools and techniques to start recording their songs and develop their own style, while helping experienced musicians experiment with different sounds and keep their music fresh with a pool of inspiration.
It will incorporate a very clean, uncluttered navigation, keeping ease of use as the priority of the design. Complicated functionality will be kept to a minimum.
Objectives
While the scope of the site is potentially very large, with clear objectives set out to narrow the scope, it can limit the use of unneeded functionality that could bloat the application, make it harder to use and increase the build time.
Project objectives:
-
Create a place where musicians can come and get ideas, help and inspiration from each other.
-
The scope of this site could be huge, such as incorporating functionality for gig listings or having an area for a showcase of completed music, so it is essential to keep a narrow scope of the original idea of the site so it is possible for it to be completed.
-
Keep the site very easy to use, keeping navigation to a minimum. A good example site is www.bandcamp.com.
Research objectives:
-
Learning about Creative Commons Copyright. “Creative Commons defines the spectrum of possibilities between full copyright and the public domain. From all rights reserved to no rights reserved. Our licenses help you keep your copyright while allowing certain uses of your work — a “some rights reserved” copyright”. Using this form of copyright has the potential to let users define their own terms of how they want their music to be used.
-
How users will interact with each other, and designing the interface around making that as easy as possible. Looking into social interaction design which involves web design principles such as: information architecture, user interface design and experience design around a user centered design model.
-
Research into why some social networks fail while others thrive. For example why Myspace is getting less popular while Facebook is still expanding. Whether the problems lie in usability or too much complicated functionality.
Learning Objectives:
-
Become very well versed in PHP and MySQL, as well as learning to use the chosen PHP framework effectively making the final design very usable using technologies like XHTML, CSS and AJAX.
-
Develop my project management skills including time management, good use of development cycles and correct application of recourses. It is important with a project that has the potencial of having a very large scope to manage my time effectively between writing the report and building the system. Poor use of time could result in one of the parts having too much spent on it and finding there isn’t enough to complete the other.
Methods, Techniques and Processes
-
User Centred Design is an evolutionary process placing the users needs and wants in the central focus of the design process. I am using this process as it has the best chance of creating an environment that the user feels comfortable using with successful results.
-
Lo-fi and/or Hi-fi prototypes are a very useful way of finding faults with a system before it has even been built. This can save hours of coding time when trying to fix problems in the build of the application. I will use either a hi-fi or a lo-fi prototype or both depending on how the project is developing.
-
Competitive and Comparative analysis are useful tools to implement to see how similar successful sites have used web design principles to get their users to keep coming back.
-
It may also be necessary to use methods such as cognitive walkthroughs and/or cooperative evaluations so I can see the system in use and where the problems lie.
Resources and support required
-
Tutor support will be very helpful when writing the report for feedback, and if I get stuck on any particularly difficult pieces of code.
-
The Library has a wealth of books and journals available for all of the research aspects of the project.
-
Online recourses and tutorials e.g.: W3S. Similar to the library, the internet has a veritable font of tutorials and articles to do with the project.
Sources and references
The material I will use for this project will include coding textbooks, online coding libraries and books on interface design.
Welling and Thomson (2008) PHP and MySQL Web Development (4th Edition). Pearson Education Inc.
Harrisson (2009) WordPress MU 2.7: Beginner’s Guide, Packt Publishing.
W3Schools website http://www.w3schools.com/ [2009]
Bates (2006) Web Programming – Building Internet Applications. J. Wiley and Sons Ltd.
Online PHP Library (SPL) http://www.php.net/manual/en/book.spl.php [2009]
Spool, Scanlon, Snyder, DeAngelo (2007) Web Site Usability: A Designer’s Guide (Interactive Technologies) Morgan Kaufmann