# MVP List

[andy-h-2016]

• [x] Should have 7 MVPs.
  • [x] 3 of those are User Auth, Heroku, and Production README.
  • [x] The other 4 are from the MVP List or they have clarified them with you
• [x] Contains a description sentence of the app
• [x] Includes two to three detailed bullets on functionality and presentation of feature
• [x] At least one CRUD feature, which states what CRUD operations are planned (creation, reading, updating, deletion)
• [x] Estimates how long it will take the code each MVP
• [x] Correctly formatted
  • [x] MVPs are listed in an ordered list
  • [x] Each MVP is broken down into bullet points

    Comments

[andy-h-2016]

Please refer to the Bluebird MVP List as an example of what the MVP List should look like.

Please also refer to the list of required MVPs for pre-approved clones. These MVPs need to have details filled in, but otherwise it gives you an idea of how to organize your data. In particular, look for the Tumblr section. Some of the MVPs you have written can be folded into the required MVPs. Please slack me if you if have any questions about this.

Specific feedback

• Formatting
  • Put your MVP#4 on a new line
  • Bold the top level MVP's
• Rephrase MVP#4 as CRUD of posts, with Active Storage of images as an option or subtask
• MVP#5: Recommend simplifying this into a separate likes MVP and follows MVP.
  • Likes should just be a bonus feature you can just tack on in the end. Relatively simple compared to the other MVPs.
  • Specify what the point of the Follows feature is (affects which posts are displayed on which page?)
• MVP#6: Reject. Seeding should be incorporated into all of your MVPs that involve database CRUD. If you don't have sufficient seeding, that MVP is not finished.
  • Recommend the home feed as a MVP to replace this one.
• Arrange your MVP's in the order that you will complete them
• Add time estimates

[andy-h-2016]

Closing this out since you have the gist of it. But final suggestion:

• Since the user show page, the dashboard page, and the explore page will have very similar functionality, at least with regards to showing posts, I would make the language for each of those MVP's very similar so it's clear to anyone reading (including yourself) that there is potential for modular and reusable code for those sections.