tiusty / cocoon Goto Github PK

When a user creates an account it should have to send a confirmation email and the user needs to verify the account before logging in. Also, in the email verification forms about terms and condition etc can be added later

We need 3 critical documents to engage and work with a client - a Hiring Contract, website Terms & Conditions, and a website Privacy Agreement.

When a zip code combination is not present the survey views function calculates the distance with google distance matrix. The api is responding with an error.

Feel like having a bigger circle for good homes would be helpful in finding them on the map. Therefore better scored homes should be bigger and be pushed to the front of the stack so they are on top of worse homes

Better implementation of grabbing photos form MLS and storing them. Also better implementation of rendering photos

On the top-let corner of the website, the Cocoon logo is separate from the word "Cocoon" even though clicking on either does the same thing - can we merge these together? Also when you mouse over the word Cocoon it'll get slightly bigger, which is cool, but the logo doesn't change in size at all when you mouse over that.

For example, a house if Favorited in the survey result page, then so the user goes to the user profile, then clicks the back button to go back to the survey result page, then the page will show the state of the favorite when the page was first loaded. Therefore, the house that was Favorited will no longer show up as a favorite even though in the database it is. The solution, maybe force a refresh of the survey result page if someone goes back to it.

Make some special login for brokers (Tomás and Bill) to be able to sign in and see all the info for each client.

If a person indicates they must have a parking spot, what do we do with homes that we don't know if they have a parking spot or not?

Frontend needs the naming overhaul that the backend got. Right now everything is blank on the frontend. After the naming is fixed make sure the functionality is mostly back

Instead of loading all 200 homes in a scrollable container, slowing down the webpage, loading the first 20-50 highest scores and allow the user to hit "next" and see more

Consolidate the existing "favorites" and "short list" into a single "my clients" page that saves surveys based on the client.

Fix the model to split the fields into classes. Switch getters and setters the properties. Write more unit teata

no one has used those, and feedback has been confused and oppositional. Let's scrap it, and keep everything simple.

This should really be a foreign key to make searching, adding, scalability better

If someone wants to look at a 1bed and 2bed, rather than crunch two parallel surveys lets allow them to consider both simultaneously. It'll hurt the comp efficiency, but will strengthen the survey considerably.

When someone is using a slider question on the surveys, let them have a box under the slider to have the option of typing in a number. Also, the slider itself should go in increments: $50 (or $100, doesn't matter too much) increments for rent, and 5 minute increments for commute.

The model needs to be split up the classes and have the getters and setters changed to properties

The unit tests should use a mock version of the distance matrix api instead of actually calling the distance matrix api. This is both to make the API call deterministic and also not be charged.

When the user scrolls through the list of homes on the survey result page, keep the google maps static and just move the list of homes

See Turbotax or Apartmentlist for good slideshow survey style execution. See google drive slideshow with wireframe for how the new survey will look.

A lot of time is spent manually writing an email with all the info and pertinent links for a short list of apartments. A button on the "favorites" page that emails all that info would be great, and save the agent team a lot of time per client. Sample min output might be something like this:

#1: 123 Main St., $1,800 rent, 2bed 1bath, hardwood floors, 15 minute commute...
#2 3 Bob St., $1,950 rent, 1bed 1bath, hardwood floors, 22 minute commute...

Need to make sure the algorithm is more robust. This starts by extracting the algorithm and the scoring struct into modules so that each part can be tested and also be more easily modified and added to

When a broker opens a client file, by law they need to save all their info for 3 years. So we need to create some sort of database with a folder for each account with all that person's info (including all surveys, account info, and digitized copies of documents such as their e-signed hiring contracts, privacy agreements, etc.)

Some people work from home, and therefore want us to bypass the commute portion altogether. In this case there should be a button that says "work from home" to skip the question cluster.

Makes it easier to add new survey types etc

How to deal with homes becoming available and then rented

Pretty simple - see Google Drive for new text for that page. Maybe include links to Linkedin, Twitter, fb etc.

Allow the survey to accommodate up to 2 commutes: ask a question at the start of the commute section that says 'how many commutes do you want to do?" with 0 (work from home), 1, or 2.
For 2, ask everything the same (ask for commute 1 and then for commute 2)

E.g. RentalBeast, Rent Lynx, YouGotListings, etc. So that Cocoon's algo has more apartments to work with.

As a sub-issue, we'll need to find a way to eliminate redundant apartment listings.

Update about us page to reflect information about the company

The photo takes a long time to load on the front page. Compress the photo to load faster

Right now the script needs to be run every day to update the move in day. Figure out the best method for storing move in day

The backend is currently in GMT. Make sure the backend updates to where the user is located

0bed sometimes appears, and those are the studios that we're currently missing out. All of our early clients so far have been open to studios, so we should be able to crunch those too.

Quick fix to avoid clash w/ MLS and other databases (temporary fix)

Compress those stock photos so people get an optimal first impression

I think the function should return true or false instead of an error code. It shouldn't matter why it failed, but the function returns whether or not the zip code is fully computed. The function that adds zip codes to the database will handle figuring out the issue

Split up the fields into classes better. Also, add better unit tests. Switch the getters and setters to properties

Scrolling with the nav bar causes issues with jumping. Also on the survey result page, with the mini survey open, the navbar can be problematic

The user may or may not want to account for traffic estimations when computing commute time

Right now this function does not support commute type. It should. So a filter element should be added to the query for the commute type.

A few changes to the small tiles:

• Show rent, exact commute, and once we have it, the neighborhood score. Those are the 3 things that market research indicates renters care most about. We'll have to subscribe to the neighborhood score for that, btw.