Welcome back! This is the second post in "Creating TravelNest - an AirBnB Functional Clone" series.
I am starting with a simple product requirements document that describes the core features of TravelNest.
I am using the following tools at this stage:
- A simple product requirements template from Atlassian
Goals
- We aim to create a software application that lets travelers book places offered by home owners across the world
- This will be initially created as a responsive web application, that is accessed via desktop and mobile browsers
- Property owners can register themselves and list properties for rentals (including location, images, description, rates etc.)
- Travelers can browse through properties and choose one that meets their criteria
- Once chosen, travelers can make a booking which must be accepted by the respective property owner
- Once accepted, the property is unavailable for booking by any other traveler on same dates
- Travelers and property owners can exchange private messages related to property, until a week after the last date of stay
- Payments are settled outside the platform (for initial release)
Assumptions
Here are some basic assumptions to help with the system design.
- Number of unique users => < 10000 unique users per day
- Number of active property owners => < 250 MAU
- Number of active travelers => < 2500 MAU
- Max. number of properties by a single owner => 5 properties
- Max. number of current bookings by a single traveller => 3 bookings
Further technical assumptions will be covered in system design.
User personas
Following are key user personas for TravelNest application.
- Property owner : Who owns properties and list them for rental using the platform
- Traveler : Who searches for and books properties for stay
- Site Admin : Who manages the platform and have elevated access to prevent malicious usage of platform (e.g., fake properties, fake bookings etc.)
Core user stories
What we are not doing
- Mobile application is out of scope for MVP
- No variable price for properties. Price per night is fixed for a property on all dates
- Date change on existing booking is out of scope for MVP. For dates changes, traveller must cancel old booking and create a new one
- Payment for booking are settled outside the platform between travelers and property owners
- Videos are not available as part of property listing
- Website design is not part of development. An opensource website template will be used
Next steps
Now that we have the product requirements in place, the next step is to get some C4 diagrams in place to describe the system to be built. See you all soon!
Posts in this series:
Top comments (0)