This is a group project I worked on with other developers + a project management team. This was the third project I completed for my Web Development Immersive Course at General Assembly. Created using a combination of Node.js, Express, MongoDb, Mongoose and the Semantic UI framework.
Clone or download
Pull request Compare This branch is even with beggers23:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.


###Technologies Used

We used a combination of Node.js, Express, Mongo, Mongoose, and Semantic UI to create an app that utilizes two APIs (Google Maps and Foursquare) to give users a custom HipScore based on form inputs. Users are persistent, and can change their neighborhood preferences. We serve the users and locations up from our own homebrewed API.

###General Approach We Took

As a team, we decided early on that the best way to tackle the project was to play to our individual strengths. Brendan took ownership of the back end, Carolyn took ownership of the front end, and Blake ran back and forth between the two as necessary. Our PMs supplied graphics, copy, user stories, wireframes, usability testing and support.


These are our original product sketches:

[landing page]

[hipscore quiz]

[register or login]

[custom hipscore]

[profile page]

We also have a paper prototype:

[paper prototype]

This is a higher fidelity wireframe based on user testing done by the PMI team:


###User Stories See User Story File

###Screenshots Of Our App In Action

[landing page]

[hipscore quiz]

[login / signup form]

[custom hipspace score page]

[custom hipscore neighborhood with options checked]

[ads & apartment listings]

[profile page]

###Unsolved Problems & Major Hurdles

Unsolved Problems: Getting third party real estate APIs to play nice in the amount of time we had was problematic. Full and awesome form validation using Semantic UI was also problematic. We were unable to get the forms to submit without hitting enter, too.

Major Hurdles: We didn't have any super major hurdles - learning Semantic was less easy than zero effort; getting APIs to play nicely together was not instantaneous; and contemplating what was needed for creating the scores was also a trick of logic.