Group project - creating NYT bestsellers app.
This app displays a list of books in a Collection View from the New York Times api. Each book is loaded onto a collection view cell, filtered from another NYT endpoint that contains a list of book genres. When selecting a cell we segue to a Detail controller that gives you the options to purchase or favorite the book. A favorited book is displayed onto a separate tab called "Favorites". There, you are given a second chance to visit up to 4 popular website where you can purchase the book or simply remove it from your favorites list. The "Settings" tab allows the user to select their topic of choice which is then reloaded in the "Best Sellers" tab.
| BEST-SELLERS |
| DETAIL VIEW |
| FAVORITES |
| SETTINGS |
Conflicts arose upon the absence of a "Git flow" in the production of code. Specifically, because we only branched off of a master branch as we worked on separate individual features. The master branch was to act as production code which would be showcased. Also, as we updated the code to master, we would branched off of it, again... etc. Unfortunately, only using the master branch caused a conflict in its code, when we finally tried to merge. To solve this, we created a git branch flow of "individual feature codes". We could then branch off of the new master which we called, quality assurance (qa). The qa branch allowed multiple small pull requests to be merged from everyones individual branch. Upon large iterations of qa, it would eventually be merged alongside the production (prod) branch. This 'prod' branch became our new master that would contain all updates and changes to be publicly showcased.
Bienbenido Angeles
Melinda Diaz
Tiffany Obi
Luba Kaper