New Account Creation, Login & Demo Account

• Backend: DB, model, controller, views
• Redux Loop: ajax, actions, reducer
• Presentational Components and Containers
• Styling
• Smooth, bug-free navigation
• Adequate and appropriate seeds

Display Browse & Library Pages & Playlist CRUD

• Users can play songs or add to their playlists
• Users can create playlists
• Albums, playlists and artists display their songs or albums
• Users can update or delete their playlists
• Adequate styling
• Smooth, bug-free navigation
• Adequate and appropriate seeds to demonstrate the feature

Wiki Page Home

• Is the first page you see upon entering the wiki
• Contains a welcome message
• Contains a link/placeholder for a link to the live page
• All links in the right sidebar should contain each wiki page and link to the correct page
• Correctly formatted
  • each wiki page is listed in bullet points
  • all links route the correct page

Comments

• Good job on the proposal, let me know if you have any questions!

---

MVP List

• Should have 7 MVPs.
  • 3 of those are User Auth, Heroku, and Production README.
  • The other 4 are from the MVP List or they have clarified them with you
• Contains a description sentence of the app
  • Includes the following list for the 4 app specific MVPs:
    • Adequate styling
    • Smooth, bug-free navigation
    • Adequate and appropriate seeds to demonstrate the feature
• At least one CRUD feature, which states what CRUD operations are planned (creation, reading, updating, deletion)
• Estimates how long it will take the code each MVP
• Correctly formatted
  • MVPs are listed in an ordered list
  • Each MVP is broken down into bullet points

Comments

• For now, I would focus on playlists and songs (ex: don't do a search for albums/artists immediately or have artist/album pages).

---

Database Schema

• Contains correct datatypes

• Contains appropriate constraints/details

  • primary key
  • not null
  • unique
  • indexed
  • foreign key

• Contains bullet points after the table that state which foreign keys will reference to which table, or references to the associations which will be made

• Correctly formatted

  • schema is written in a table format
  • the table's name are back_ticked
  • the table header column names are bolded
  • columns names are lowercased and snaked_cased and back_ticked

Comments

• Looks good!
• Note that spotify allows the same song to be the same playlist more than once (so you can't enforce uniqueness on [:song_id, :playlist_id])
• Is your songs table going to have an artist_id?

---

Sample State

• State shape is flat!
• State's keys are camelCased
• All keys within the values in the state are accessible in the schema
• Correctly formatted
  • Sample state is rendered with triple backticks, and the language ```javascript...```). This will display the state as a code block instead of a giant line of text
  • Top level slices
    • entities
    • session
    • errors (here or in ui)
    • ui (if needed)
  • Should NOT have nested slices, aka comments inside of posts
    • Some info from other tables is ok, for instance:
      • the author username and imageurl for a post. basically any info that the user can't change
      • like count and a boolean on whether the user likes the post instead of a likes slice

Comments

• You should have a playlistSongs slice of state so you can map over all songs in a playlist
• You'll also want to store the current song being played in your store somewhere, and whether it's paused or playing

---

Backend Routes

• Contains the following sections: HTML, API Endpoints(Backend)
• Each route has a description
• API Endpoint routes contains wildcard variables written in snake_case
• Routes does not contain superfluous routes
• Have API routes that will allow the front end to get all info it needs and does not have unneeded routes:
  • probably doesn't need a GET likes api endpoint because that info comes through the post show

Comments

• I recommend having a search endpoint, like GET /api/search and have a SearchesController so you can search for playlists and songs at the same time.
• I'd rename DELETE /api/playlist_songs/:entryId to something like DELETE /api/playlist_songs/:song_id
• You won't need the GET /api/songs/:id as you'll never look at one song by itself

---

Frontend Routes

• Frontend routes contains wildcard variables written in camelCase
• Correctly formatted
  • Routes are displayed with inline coding text (backticks)

Comments

• Don't worry about a user profile until you get to follows.