Todos

Airbnb listing - "Airbnb has two ways for searching for listings. Guests can use search filters based on defined categories which are set by the hosts. Guests can also search in a text box on the nav panel which looks for key words in free form text in the listing descriptions. When you get to section 6 in the road map are you thinking about implementing one or both of these options for finding and viewing listings?"

Create listing form - "As you go through section 5 do you think you could do a multi-step form for the listing creation?"

Paypal/Stripe

Reservation and chat - "Another thought about this. Airbnb guests and hosts message one another in relation to a specific reservation rather than just in relation to the listing. From a psql table hierarchy you would have: message belongs to reservation belongs to listing belongs to a user (rather than message belongs to listing belongs to user). Just thought I'd highlight this nuance before you get started with implementing the database in case you want to do it this way. Related to your roadmap you'd need to create reservation request between section 6 and 7."

Reservation - "When guests send a reservation request to a host, they also send the first message by default alongside the reservation details. Then the guest and host speak to each other in the chat in relation to that specific reservation request. Once agreed, the host approves the reservation."

pre-approve, approve cycle with complex status of the reservation

Read the roadmap sections 5–7 and inspect the existing listing, reservation, message, and database entry points. The issue raises search, multi-step listing creation, payments, reservation approval, and reservation-scoped chat, so first clarify which proposal is in scope and agree on the data model and acceptance criteria before implementation.

Written by the indexing model from the issue text.