yarn install
yarn run serve
yarn run build
yarn run test
yarn run lint
Their & My are used to name components. This holds context on the component. Later when we are doing security, we will need to validate each visit by who can see it.
- Traveller: Create Trip
- Google API for location from
- View Requests for location to
- Requester: Create Requst
- Google API for location from
- Google API for location to
- Request Status to "Pending"
- Payment Form or Credit card
- Traveller: Accept Request to my trip
- Request Status to "Accepted"
- Traveller: Counter Request to my trip
- Request Status to "Countered"
- Requester: Accept counter offer (should just be accept with new price... or new endpoint?)
- Requester: Decline counter offer
- Requester: If request is over XX$, show credit card form (and charge)
- Traveller: Update attached request status
- Status to "Purchased"
- Requester: their money is put in ESCRO
- status to "On the way" (after start date of trip)
- Traveller: Generate QR code for request scan
- Requester: Read QR code when traveller
- Request Status to "Delivered"
- Escrow
- Create mock API which shows transactions
- Charge requester - Move money out of requester ESCRO (charge requester)
- Pay traveller - Deliver money to traveller
- Authentication
- Security
- Form Validation
- All forms
- Deploy to production
- Website
- How does it work (video?)
- What we do
- Why does this exist
- Help Center
- Automated Chat Bot
- Contact us
- Terms & Conditions
- Traveller
- Requester
- Save Google places name, only look up if location name is empty.
- Design / Redesign
- Mobile Application (iOs/Android)
- Traveller: Add multi-location trip
- Traveller: Add dimension available for request
- Requester: Set request dimensions
- Traveller: Accept terms to create trip
- Requester: Accept terms to create request
- Request by location view. Check items off a list you can grab and bulk add to your trip.