Upgrade to Pro — share decks privately, control downloads, hide ads and more …

SweetCooking Presentation

Alex Irion
November 17, 2016

SweetCooking Presentation

IDB3 final presentation

Alex Irion

November 17, 2016
Tweet

Other Decks in Education

Transcript

  1. Sweet Cooking - IDB 1 Patrick Lyu, Alex Irion, Evan

    Carrillo, Jake Mayo, Rafik Rizik, Kris Lin, Kris Vandercook
  2. About us • Patrick Lyu ◦ Front End ◦ Issues:

    6 ◦ Unit Tests: 3 • Alex Irion ◦ Back End, Dev Ops ◦ Issues: 10 ◦ Unit Tests: 5 • Evan Carrillo ◦ Database design, Flask app ◦ Issues: 18 ◦ Unit Tests: 8 • Jake Mayo ◦ API’s, Front End design, Issue tracking ◦ Issues: 13 ◦ Unit Tests: 6 • Rafik Rizik ◦ Back End ◦ Issues: 6 ◦ Unit Tests: 10 • Kris Lin ◦ Front End ◦ Issues: 8 ◦ Unit Tests: 3 • Kris Vandercook ◦ Flask app, Wiki, DB models ◦ Issues: 11 ◦ Unit Tests: 28
  3. Team Total Stats • 287 commits • 7 branches •

    58 closed issues • 4 unresolved issues • 66 Unit Tests
  4. Tools Used • Frontend: React, Bootstrap, JavaScript • Backend: Flask,

    Python • Database: Sqlalchemy, PostgreSQL • Hosting: AWS • API: Spoonacular API • API documentation: Apiary • Communication: Slack • Source Control: Github, Github issues, Github wiki
  5. What is our product? Why did we create it? •

    Our group is a bunch of fatties at heart, so we decided to build a site that allows people to look up information about various recipes, ingredients, and food products • Problems we based our idea off of: ◦ Ever have a long day and get home only to realize that you have no idea what you're going to do for dinner? ◦ Has lunch time come around on one of those lazy Saturdays and you have no clue what you want to eat? ◦ Having that special someone over for the night ;-) and need some good breakfast ideas for the morning? ◦ Broke college student and only have a few ingredients left in the kitchen. Want to see what meals you can scrap together with what you have?
  6. • Even if you have quite the large cookbook, chances

    are you'll cycle through everything in a month or two. Our API has thousands more recipes and can be updated instantly, unlike a book! • Let's try going to one of those cooking websites and see if we can find something there. If you're lucky, there's something on the front page that looks tasty. Of course you still have to spend ten minutes closing all the annoying pop up adds and trying to scroll through all the excess crud on the homepage.
  7. Pillars 1. Lifestyles 2. Products 3. Recipes 4. Ingredients a.

    Need Ingredient List table to join Recipes and Ingredients
  8. Self Critique What we did well • Functionality… everything works

    • Separation of duties What did we learn • Coordinating stuff sucks • Rate limited APIs are a hassle • Strong group leadership helps What can we do better • Better designs for individual pages, everything is bulleted • Lifestyles table attributes were difficult to think of (wasn’t the strongest pillar) What puzzles us • Lingering space in search breaks stuff
  9. Artsnob.me Critique What they did well • Pretty splash page

    • “Back to table” button What did we learn from their website • Table on the landing page for extra links looks very nice • Search on each Pillar is cool What can they do better • Search results not showing • About page formatting • Apiary docs are off What puzzles us about their website • What is “States” tab? • Running Unit Tests? • Tables load slow sometimes