cs373-BananaFish

Transcript

1. BananaFish Ruben Baeza, Nico Vasquez, Alex Ventura, Steven Zvonek
2. Purpose Problem: Most gaming websites let you read reviews but don’t provide a link to jobs at that company Solution: Create an IMDb like website to let users browse video games, companies, and find jobs pertaining to the games they like
3. Front-End Technologies AngularJS - MVC framework with shitty long term maintainability but excellent short term churn out Lodash - FP functionality library for JS Restangular - Because $http and $resource blow Angular UI Router - Because ngRoute is so bad they stopped bundling it when 1.2 came out
4. Front-End Build Technologies Gulp - Because Gruntfiles are unintelligible by actual human beings (minification, concatenation, the usual) Bower - Twitter’s JS dependency manager (a must on any web project) Yeoman - Scaffolding tool (great for newbs but easy to outgrow due to individual project specificities)
5. BananaFish Critique • What we did well… ◦ Created a responsive site that asynchronously loads and displays content ◦ Got a working website with very little actual work (I mean seriously)
6. BananaFish Critique • Some problems... ◦ Unable to limit number of results or amount of detail when querying api for our models ◦ Our search only uses Postgres’ pattern matching with ilike. Can be slow sometimes. ◦ Some of our data is html that should have been processed (broken links) ◦ Image load times and formatting
7. Elementalists Critique What they did well • Interactive periodic table • Dynamic animations on timeline • Website is tightly linked together What we learned from their website • Search incorporated into navbar is nice
8. Elementalists Critique What they can do better? • Timeline of elements is massive, sort by periods or groups What puzzles us? • Charts tab doesn’t display anything when you move the sliding bar • Fun run API map unable to load Google Map API