[X] 3 of those are User Auth, Render, and Production README.
[X] The other 4 are from the Approved Apps List or your PM will 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
[x] Right now your timeline puts your project at taking 10 days, when we technically have 14 full days. I would consider allocating some of those extra days to Listings, Reservations, and Locations. Listings will include both an Index and Show page for Listings, so that will take more time than we think.
[x] I think Search qualifies as a Bonus for down the line. Search can be simple to implement once we figure it out, but I'd rather we not get slowed down during our 1st Feature when seeding our Listings table and rendering all of that data will take a lot of time and energy.
[x] Can Usersdelete their Reservations?
[x] Can logged outUsers leave Reviews?
[x] Hosting on Render and Production README should take at most 0.5 day for each in our timeline, so feel free to add that.
[x] I recommend leaving distinct CRUD labels next to your Reservations and Reviews features.
MVP List
Comments
Listings
,Reservations
, andLocations
. Listings will include both an Index and Show page for Listings, so that will take more time than we think.Search
qualifies as a Bonus for down the line.Search
can be simple to implement once we figure it out, but I'd rather we not get slowed down during our 1st Feature when seeding ourListings
table and rendering all of that data will take a lot of time and energy.Users
delete theirReservations
?Users
leaveReviews
?Reservations
andReviews
features.