Execution Instructions

User Manual: Pdf

Open the PDF directly: View PDF PDF.
Page Count: 3

DownloadExecution Instructions
Open PDF In BrowserView PDF
UpNext Execution Instructions
Our app is a web app that is hosted on firebase. We developed this app and tested it for using
Google Chrome. To access our app, follow these steps…
1. Download Spotify Desktop here: ​https://www.spotify.com/us/download/other/
2. Go to the web address ​https://upnextdebug.firebaseapp.com
If you have trouble accessing the web address or have further questions or want the database
cleared, send an email to ​duffy18@purdue.edu
*Please note that this app uses a playlist name called “UpNextPlaylist”. This playlist is created
upon logging in. You can use this as a way to confirm some bugs.
Take note that the actual database is reflected on the home page. This should correspond to
the spotify playlist “UpNextPlaylist” except for the case of duplicates in the database. Also note
that spotify only allows 200 tracks per playlist.
Below are the components and their expected behaviors:

Header:
The header is the navigation bar of our app. It is a greyish-black bar located at the top of every
web page of our app.

Input

Output

User clicks “UpNext” in the header.

The app should navigate to the home page.

User clicks “Home” in the header.

The app should navigate to the home page.

User clicks “Search” in the header.

The app should navigate to the search page.

User clicks “Login” in the header.

The app should navigate to the login page
and display the user’s spotify playlist
populated with songs from the database.

Mobile version, user clicks the button to
expand the menu.

The menu should expand and collapse upon
selecting any options.

Home:
The home page is the heart of our app. It is the first page you should encounter. Here users if
logged in can listen to the shared playlist on repeat and also vote on the playlist’s songs. Upon
logging in and when the spotify application is open, the user should see a spotify player as well
as a currently playing banner appear. There may be duplicate tracks in the database/display on
the homepage, but the spotify playlist should not have more than one of the same track id/uri,
and duplicates should not cause any undefined behavior. Also note, only premium users are
able to press the back button on playlists, so do not worry about any strange behavior of the
back button, although anyone can use the forward button.

Input

Output

User clicks “Please Login” button.

The app should navigate to the login page.

User clicks the play button in the embedded
iframe.

The Spotify Desktop app should open, music
should start playing, and a banner displaying
what song is currently playing should pop up.

User clicks one of the voting buttons.

The number to the right of a song’s title
should adjust accordingly. The order of the
songs is based on the amount of votes.

User clicks the pause button in the embedded The song should pause.
iframe.
User clicks the skip forward button in the
embedded iframe.

The next song should start playing.

Login:
The login page is a bare bones means of initiating OAuth2 login through spotify.
*Please note that the absence of a logout button is NOT a bug. We never got to implementing
this.

Input

Output

User clicks the “Login Here” button.

A new window should pop up prompting the
user to enter their username and password.
(Keep in mind that an auth token is
generated. We store it so login is faster after

the first time. This is done to skip past
entering credentials).
If the user is already logged in, an alert
should show notifying them.
User successfully logs in.

The spotify pop up window should close and
the app should navigate to the home page
with all elements loaded including the iframe.

Search:
The search page is where users can search the spotify track library. They can then add songs
to the UpNextPlaylist to listen to on the web app.

Input

Output

User clicks the “Search” button.

A list of terms should show up with a green
plus button. (Very odd behavior with inputs
may be considered a bug). Please note that
the list returned is entirely determined by the
Spotify API. For edge cases, alert dialogs will
pop up.

User clicks the green plus button by a song
name.

The song should be added to the database
and the playlist.
Source Exif Data: 
File Type                       : PDF
File Type Extension             : pdf
MIME Type                       : application/pdf
PDF Version                     : 1.5
Linearized                      : Yes
Producer                        : Skia/PDF m67
Page Count                      : 3
EXIF Metadata provided by EXIF.tools

Navigation menu