📋
Meesterproef
  • Rino.Pro Design Rationale
  • Table of contents
  • 1 - Debrief
  • 2 - Problem posing
  • 3 - The solution
  • 4 - Code
    • 4.1 - Projects page
    • 4.2 - Quicksearch
    • 4.3 - Expandable views
    • 4.4 - Filters
    • 4.5 - Music-player
    • 4.6 - Track information
    • 4.7 - Workspace playlist
    • 4.8 - Recommendations
    • 4.9 - Assign moods
Powered by GitBook
On this page

Was this helpful?

2 - Problem posing

Previous1 - DebriefNext3 - The solution

Last updated 4 years ago

Was this helpful?

The way that the sync industry currently works is that music supervisors have to do a lot of different things in a lot of different applications. They have to search for music, find the people who have the rights, contact them and dealing with all kind of different laws. This is a long, tedious and confusing process.

wants to put all the required aspects in one platform: looking for music, making playlists and projects, see who they have to contact and which additional steps they have to take.

was only an idea on paper. There wasn't a design or other resources that we could based of off. Because of this we had to start from scratch. Meaning that we had to lay our focus more on the design and user experience aspects rather than create a whole new application with added value for music supervisors. First we had to do design research and sketches based off this research and later we could begin to build. Because of this openness we had to do a lot of iterations; where we sometimes had to change the entire application.

As discussed with the client we decided to make the proof-of-concept only available for desktop. Meaning that the proof-of-concept isn't responsive and functional on other devices such as mobile phones.

Ringo.pro
Ringo.pro