0% found this document useful (0 votes)
0 views11 pages

Introduction

The document discusses the interface design of five music player applications: Default, PlayerPro, Mixzing, Roar, and Trax. It evaluates their designs based on principles from Shneiderman's 'Eight Golden Rules of Interface Design', highlighting aspects such as user shortcuts, memory load reduction, consistency, error handling, and intuitive use. The analysis includes screenshots and detailed comparisons to illustrate the strengths and weaknesses of each application.

Uploaded by

sharifah
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
0 views11 pages

Introduction

The document discusses the interface design of five music player applications: Default, PlayerPro, Mixzing, Roar, and Trax. It evaluates their designs based on principles from Shneiderman's 'Eight Golden Rules of Interface Design', highlighting aspects such as user shortcuts, memory load reduction, consistency, error handling, and intuitive use. The analysis includes screenshots and detailed comparisons to illustrate the strengths and weaknesses of each application.

Uploaded by

sharifah
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 11

1.

0 Introduction

Music player is one of the mobile applications that attract users to use it. Music player
applications can make the user choose which kind of music player that they like it. Through
this application, I will discuss the similarities and differences of interface including its bad
and good design.

2.0 Interface design of five music player with screenshot

2.1 Default music player

Figure 1.0 Screenshot for Default music player

2.2 PlayerPro music player

Figure 1.1 Screenshots for PlayerPro music player

1
2.3 Mixzing music player

Figure 1.2 Screenshots for Mixzing music player

2.4 Roar music player

Figure 1.3 Screenshots for Roar music player

2
2.5 Trax music player

Figure 1.4 Screenshots for Trax music player

3.0 Bad and good design with reference to design principle

Principles of design are discussed to see the comparison of the interface design and to meet
the criteria in the principle for every application. To view certain aspects regarding interface,
user-system interaction and user experiences, a comparison of the five application music
player which is Default music player, PlayerPro music player, Mixzing music player, Roar
music player and Trax music player will be described in detail.

3.1 Enable frequent user to use shortcut

The number of user-system interaction should be reduced based on users


requirements since the use of application is increase from time to time. The keys
of “Eight Golden Rules of Interface Designs by Shneiderman’s” are very helpful
to an expert user. Based on the features that can directly access to other tab of
function, Default and Mixzing music player are combining the principle of enable
frequent user to use short cut. For example, users do not need to open each
interface as intermediate to get back to main menu. For Default music player
example, from the front user interface, the user can just click to any tab they
want [Artist|Albums|Songs|Playlist]. Second mobile application that apply the
rule is Mixzing music player, which is the tab has [Artist|Albums|Songs|Genres|
Playlist] in every interface. More screenshot at figure 1.0 and 1.2. The multiple
tabs on the top of each interface can speed up the interaction of users with the
application. Users can experience the shortcut in the application which can allow
users to be an expertise.

3
3.2 Reduce short term memory load

In “Eight Golden Rules of Interface Designs by Shneiderman’s” says that the


limitation of human information processing in short-term memory will need to
kept a simple displays, combination of multiple page displays, reduce window-
motion frequency and the enough training time be allotted for codes, mnemonics
and sequences of actions. If the information too length, it will cause to user
memory load. There are three applications in music player that has been chosen
apply this reduce short term memory load which is Default, Roar and Trax music
player. The Default music player (refer to figure 1.6 (1)) show the short cut to
choose a songs. Users no need to go to others interface to looking for a song or
to setting the music playlist because they can use > button to see the details
about the playlist or others information. For Roar and Trax music player also
apply this rule to make easier for user to choose information (eg: albums, artist
and folder) (refer tu figure 1.6 (2) & (3).

4
3.3 Strive to consistency

Consistency is one of the principles by Shneiderman’s in “Eight Golden Rules of


Interface Design". Among the five music player application, only PlayerPro music
player and Mixzing music player applied the consistency rules on the top of each
interface. PlayerPro music player applied the consistent icon for search features
while Mixzing music layer has search icon and Mixzing logo. As Shneiderman’s
says, consistent commands should be employed throughout. This will make the
user experience in the music player application interface design because the
icon is located at the same point at the top of each interface.

But for the Mixzing music player, the arrow icon next to search icon does not
appear in second interface (refer circle in figure 1.7 (2)). This design is violated
the principle because the icon is for short cut to music player (refer to figure

5
1.8). The icon will bring user to music player instead of if user clicks the “music
box” it will bring user to playlist song. This situation will make user a bit confuse
and show the design violated.

3.4 Offer simple error handling

Shneiderman’s proposed principles prevent error in “Eight Golden Rules of


Interface Design". As Shneiderman’s remarks that “design the system so the
user cannot make a serious error. If an error is happened, the system should be
able to detect the error and offer simple, comprehensible mechanisms for
handling the error”. In this case, PlayerPro music player, Mixzing music player
and Trax music player have this principle in the application. The user will be
given information of error when their wanted to clicks certain icon in the music
player application. For example, in Trax music player, users have to grab the
folder or track to move it over the playlist. If user keep click on the play icon, it
will not working and the instruction will come out to prevent error. For PlayerPro
music player, when user clicks on the lyrics button, it will pop out “lyrics not
found” because the application does not provide the lyrics but the instruction will
help the user to search the lyrics. In Mixzing music player, to prevent error, the
application show theuser about the back button behaviour which is user can
make a selection either want to change or keep this setting.

In each application
below, it is show box to
prevent error from the
user.

6
(1) (2) (3)

Figure 1.9 A screenshots of Trax music player (1), PlayerPro music player (2) and
Mixzing music player (3) application

3.5 Flexibility and efficiency of use

Principle of flexibility and efficiency of use is that it can speed up the interaction
of expert user and also to both inexperienced and experienced users and it allow
user to tailor frequent actions (Nielsen, 1995). This principle is suitable for the
five music player which is Default, PlayerPro, Mixzing, Roar and Trax music
player. For example, in Default music player, when user clicks on the song it will
pop out the media player that have arrow button either user want to heard
previous song or next song quickly and pause/play button (refer to figure 1.10
(1)). Same goes to others music player which is PlayerPro (2), Mixzing (3), Trax
(4) and Roar (5) that shows the media player with arrow button and pause/play
button when user clicks on the song. It can make facilitate the user’s accuracy
and precision, provide choice in method of use and provide adaptability to the
users.

7
Figure 1.10 A screenshots for the five application that has been chosen

3.6 Simple and intuitive use

According to Dix, et al., (2004) simple and intuitive is any people can
accommodate it without difficulties. Intuitive are involves utilising knowledge
gained through other experiences (Blackler, Popovic & Mahar, 2003). In this
case, music player are one of the application that make it user be learnable
because of simple music player design. It is not so complicated to user when
they use it. For example, Roar music player show the chunk of menu for user to
choose what they want. Design principles for android wear (2014) has supported
that if the design show in a chunking, it will only show what user need. These
music player design is very easy to understand, even user have no experience,
language skills and knowledge. Let see the example of Roar music player with a
chunking design when user click the music symbol at the top left interface (refer
figure 1.11 (1)). Other music player that follows the simple and intuitive use can

8
refer to screenshot of Figure 1.1 PlayerPro music player, Figure 1.2 Mixzing
music player, Figure 1.3 Roar music player and Figure 1.4 Trax music player,
highlighted in the green rectangle.

When user clicks at


the icon in figure
1.11(1) (in blue
circle) it will show
user the chunking of
menu in figure 1.11
(2) that this music
player have.

(1) (2)

Figure 1.11 A screenshot of Roar music player application

9
Design principles for android wear. (2014). Retrieved from
http://developer.android.com/design/get-started/principles.html

Dix, A., Finlay, J., & Abowd, G. D. (2004). Human computer interaction (3rd ed.).
Upper
Saddle River, NJ: Pearson.

Blackler, A., Popovic, V., & Mahar, D. (2003). The nature of intuitive use of products: an experimental
approach. Design Studies, 24(6), 491-506.

Nielsen Norman Group. (1995). Retrieved September 26, 2015 from


http://www.nngroup.com/articles/ten-usability-heuristics/

10
http://www.mattsoave.com/old/cogs187a/iu_site_eval/7efficiency.html

http://www.whatwasithinking.co.uk/2009/02/27/explaining-usability-heuristics-a-
quick-guide/

11

You might also like