ABSTRACT
This project is about the mp3 music player application
development using Reactjs. The biggest difference between the
music player webapp and existing applications is that it is
completely free for users to use. It will integrate the advantages of
existing music players on the market, as far as possible to mining
out the existing music players' function, and then do the filtering in
order to eliminate functions that are not practical or low
cost-effective. Also, it will be kept improved based on user
feedback.
In addition, depending on the user's usage scenario, the music
player will also add some modes, such as driving mode and night
mode, to allow users to use the application in any situation or
environment. Moreover, the music player web app will have
audio trim features, allowing users to trim the best part of their
favorite song into a phone ringtone or alarm. On the other hand,
the existing music players pay less attention to the control of
gestures. Therefore, the music player will solve the limitation by
adding more gestures and shaking the phone feature for media
control to make it more user-friendly and humane.
In a nutshell, the methodology for developing the mp3 music
application used in this project is the agile development cycle.
The agile development cycle consists of six phases, which is
requirements analysis, planning, design, implementation or
development, testing, and deployment. Due to the iterative and
flexible nature of this approach, it is able to effectively adapt to
users with changing requirements
1. Problem Statement
The problem domains on this project are:
1. Bloated software and user interfaces
Due to the fierce competition between music player applications, many
developers tried to add many features, advertisements and content to their
respective music player in order to retain their users and attract new users.
This trend has made it harder for users to get content from their music
player, which also means it's harder to filter the content that they want. With
the continuous iteration of applications and a growing number of features,
the music player will become even more bloated and the user's experience
will become less smooth.
2. Lack of gestures to control
Most music player web apps use touch buttons to play, pause and switch
between previous and next songs while ignoring the convenience of using
gesture swiping to control the music webapp. For instance, when a user is
working and intends to skip to the next song in the music webapp, he/she
has to switch their attention to the console from work and click the button.
This problem does not affect the music webapp properly, but it does have
some inconvenience. However, according to Scacca (2020) said that as
our physical devices and appliances develop the button-free design,
consumers will become more comfortable and confident in this way of
interaction, so we should consider using gesture control on more mobile
applications.
3. Lack of sorting and searching features
When users continuously add new songs into the playlist, the difficulty of
the songs the user wants to filter will increase. After the songs in the
playlist are added to reach hundreds of songs, the user can only search
songs by continuously swiping up or down. If not carefully check the
content, it is possible to miss the songs that the user wants to filter, and
then repeat the behavior until the result is found. Therefore, it is an
extremely poor experience for users.
Software Requirements Specification (SRS)
1.Introduction
Building the music player web app will involve using the
ContentResolver class to retrieve tracks on the device, the
MediaPlayer class to play audio and the MediaController class to
control playback. We will also use a Service instance to play audio when
the user is not directly interacting with the webapp. You should be able to
complete this series if you're an intermediate Webapp developer, so if
you've already built a few apps, then this series shouldn't be a problem for
you.
In this tutorial, we will create the app and query the user device for
audio files using the ContentResolver and Cursor classes. In the
next part, we will use an Adapter instance to present the songs in a
list view, starting playback when the user taps an item from the list. In
the final installment of this series, we'll use the MediaController
class to give the user control over playback, implement functions to
skip forward and back, and include a shuffle function. After this series,
we will explore other aspects of media playback that can enhance the
app, such as handling audio focus, presenting media files in different
ways, and playing streaming media.
1.1 Purpose
The purpose of this document is to provide a debriefed view of
requirements and specifications of the project called "Music player
Webapp ”.
Goal of this project is to provide recommendations on your online music
collection that you have on your web locally. This document discusses the
whole system from backend to user interactions.
The tools used in this project are described in this document as follows :
➤Libraries used for back end control of application
➤Libraries used for UI and UX design of the application
➤Database used for music referencing
➤Classifiers used for classifying
➤Data and yielding recommendations
1.2 Scope
Online Music Recommendation is an area of webapp development
that is yet to be fully explored as there has not been enough attempts
to develop a webapp to fulfil this need.
Browsing over the internet one may get enough music
recommendations online but that is the real catch here, they are
mostly online.
Here we develop and try to build an online music recommender
webapp to fulfil users' need of getting music suggestions based on
their music collection.
➤ Online Music recommendation will involve recommendation of
familiar tracks and familiar genres of music available on the internet
and from online libraries.
➤ Name of the project is "Music player webapp". It is a WebApp.
➤ It plays music and provides suggestions based on the track which
the user is listening to from both online libraries which are available in
the user's machine as well as on the internet.
Advantages
➤ It provides suggestions from the local music library.
➤Works with slower internet connection because it needs less
bandwidth for providing recommendations.
➤It uses MusicBrainz database for getting metadata of all the music
present in the user's local library and recommends tracks.
➤ It is not platform or service specific.
I➤t is not bounded with any music provider services so it is
suggestions are not limited to particular service.
➤There is no specific audience for this Webapp. Anyone can use it
