search

martipal / SoundBubble

This project is implemented as part of coursework for CPSC463I at the University of British Columbia. This project is intended for users who are subscribed to the music platform Spotify. It will allow users, and other users within their “Group”, to view each other’s song logs and interact with the logs by “Up Voting” or “Down Voting” a particular log. The type of data we will be storing are Songs along with User Information. This data will be able to be shared among users to access within the group. Additional functionality that we may add/remove based on time constraints is the ability to recommend a played song to another user, and adding commenting functionality to a particular song log for users to provide their opinions (e.g. “This song is awesome!”, “This song is lame”).
0 stars 2 forks source link

Scrum Report 2 #9

Open martipal opened 5 years ago

martipal commented 5 years ago

In the previous sprint, I conducted research into Spotify's public API to examine which endpoints we are going to use in our application. I parsed a JSON response from Spotify's most-recently-played endpoint to gather info for each song, such as name, artist, album art, etc. I created a song component and a feed component to render this information in our web app. In the upcoming sprint, I will be further refining the styling of our existing components and adding additional components (your tracks, expand/collapse buttons, etc) to wrap up the UI design of our application. One challenge in the previous sprint was working with CSS and getting things to appear how I wanted them to in our app.

veronicz commented 5 years ago

For the previous two weeks, I looked into how Spotify authorization flow works and played with their demo code. I also created several components including the developer info and list of references on the About page, and parsed a sample user information payload from Spotify to display the current user info on the Account page. One challenge I faced was to display local images with meteor, which was solved by creating a top-level public/ directory. For the next sprint, I’ll be implementing login with Spotify and use the access token to get user info and song logs.

Talos6 commented 5 years ago

For the past iteration, I was mainly responsible for the front-end html structure. I implemented the headings and navigation bar component. Specifically for the nav bar, I used react router so that wrap the rest of the components into deferent pages. I chose to use NavLink which is a implemented component that can easily distinguish between active page and inactive page so that further styling can be realized. I found it is very hard for react router to be styled properly as it is not a simple anchor tag so that takes some time to go through the whole react router and found the proper CSS format. For the next iteration, I'll imported Redux into our project and use it to store different states. Reformat the component and create reactions, reducers to let the app more functional. I also going to create a login pages with link to Spotify login.