karlwithak / bnbwatcher Goto Github PK

The user should be able to select from a list of available currencies in the 'Price Range' section.

This would be nice.

This email will let them know they made a watcher and give them a cancellation link. Maybe a share link?

Whenever an email is sent, it should be checked if the delivery was successful. There is no reason to have watchers with invalid addresses, so these can be removed immediately.

I believe that airbnb considers dates that are less than 28 days apart to be priced by the night.

Soon there will be multiple pages, a base template for all of these should be set up so it looks super slick.

Right now all email text is very basic and not user friendly. It should be more descriptive and fancy?

Right now, after form submit (AJAXy) nothing happens. They should be taken to a new page that thanks them and asks them if they want to create a new watcher. Blocked by #11.

after setting checkin, the checkout calendar should start at the checkin date and be disabled before this date. Vice versa if the checkout date is set first.

There should be a new page that allows users to delete all watchers registered to their email address. This link should be sent in all of the emails sent to users.

Right now, if there is an error processing a watcher cancellation the user is told that the error could be because the watcher was already deleted. This should be checked explicitly so that this error message is less ambiguous.

Add a readme to give more info about this project. Could also include setup instructions.

This will hopefully prevent spamming.

I feel like people should not be greeted immediately by the form, and instead should start at a nice looking page that explains what the website does. Blocked by #11.

If a watcher's checkin(or checkout?) date has passed, some appropriate action should be taken.

In the email notifications there should be a link that the user can use to cancel the watcher.

Right now there is just a plaintext response, it should be a fancy page. Blocked by #11

When making a watcher that returns a lot of matching rooms, the app will often crash when parsing the json due to some garbage data in the response. Not sure exactly why this is happening or how to fix it, but it basically prevents the creation of a watcher for any popular city.

Before a user makes a watcher it would be nice to let them know how many rooms that have already been posted match their entered criteria. They could then potentially alter their criteria to get less or more alerts. It could also contain some sort of message if the number of rooms matched is very low (<10) or very high (1000+) and suggest they be less or more specific about their room.

This info could probably be put below or above the 'create watcher button' so the user only sees it after they have filled in most of the fields.

YAML made sense when it was also being used by the ruby scripts, but now that it's all javascript I think JSON makes more sense.

Some sort of location should be set up on the sign-up page. Maybe something similar to airbnb's?

Currently, it gets each page until the number of room ids found matches the listings count. It makes all of these requests sequentially while they could be make in parallel. Not sure how big of an improvement it would be, but it's worth looking into.

The current two input boxes for price min and price max should be replaced by a sexy price bar slider!