Design Doc Review, Part 1: MVP list

[RosemaryGonzaga]

Hi Nikki, I love your app choice and name - it looks like it will be a fun app to clone with lots of cool features to work on. Kudos on the hard work you put into your design docs as well!

We'll meet 1:1 today to 1) go over any questions you have about my feedback or the fullstack workflow, 2) iron out the MVP list, 3) discuss any suggested prep for over the weekend.

Below are my comments on your MVP list. I'll be sure to provide more detailed feedback on the rest of your design documents during our meeting and also in written form by tomorrow morning.

Wiki Page Home

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

Comments

• Looks good! Just need to add a placeholder for a link to the live page (which you'll ultimately update with actual link when you push your app to production for the first time on Monday evening)

---

MVP List

• [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

• These are some really cool features you've listed out, but it's more than can fit into the initial 10-day fullstack project sprint. Narrow down the list to 7 core MVPs (4 besides user auth, hosting on Heroku, and production README). Indicate which MVPs will be your bonuses. Finally, some of the listed MVPs can be further broken down into smaller and more "atomic" features. (Each MVP should focus on one main piece of functionality.) More specific recommendations below ...

• I recommend making Recipes your first feature after user authentication. Even though this is a read-only feature (users can browse recipes but can't create / update / delete them), this is a significant step in getting your app set up. Users first need to be able to view recipes before they can search for them, filter them, or save / favorite them.

  • This may take a bit more work than you'd expect.
  • First: the seeding will be important. You'll need to select a variety of recipes (I suggest 10 to start, and more after the initial 10-day sprint).
  • You'll need to setup an ingredients table and seed it with all the ingredients that are in the recipes that you choose to seed your DB with.
  • You also need to decide whether to store links to external recipes or internal recipes ... or both, though I strongly recommend sticking to just one to begin with (and linking to external recipes is easier b/c then you won't need to store recipe_steps in your database).

• Yummly's value proposition seems to center around 3 core pieces of functionality: semantic search, recipe storage (saving your favorites), personalized recipe recommendations. For this reason, I recommend you focus the remaining 3 MVPS on: Favorites, Search, and a Browse Feed. I'd love to hear your thoughts - we can discuss more during our 1:1.

• User authentication:

  • remove the 3rd bullet point ("Logged-in user (user) can opt for a subscription or 30-day trial"); we don't typically include account/subscription tiers as part of the minimum viable product. (However, you could definitely re-purpose the free trial component / button for your demo login)

• Don't forget to add time estimates to each of your main features (remember that you'll have a whole half-day to start User auth on Monday)

[petiteoh]

Hi Rosemary! Thank you for the feedback it's super thorough!

I understand you recommend having 4 MVPS on: Recipe, Favorites, Search, and a Browse Feed in addition to the 3 standard ones. However I am having some difficulties dissecting them.

1. Recipes will require a comment and a yumm feature is that considered an additional feature? I removed Tag as originally I had them all in one but have now moved Tags to the Bonus portion.

2. Favorites would need to be hosted on a users profile. Would that also include the Profile feature as a standalone MVP?

3. Browse feed I believe will come with search and recipes.

Let me know what you think about how I recompartmentalized the MVPs above. And any suggestions / feedback is SUPER welcome and needed. Thank you!