karyum/delivery-connect

delivery-connect's Issues

db structure

Everything here is open for change 😄

deliveryUsers

id	name	phone	password	mobile?

We need a better name for delivery users, delivery person and delivery guys/gals. so please if you have a better name or code name suggest it 😭

deliveryUsersSessions

id	startTime	endTime	deliveryUserId

a session is where the delivery person clocks in and is open to take orders

businessUsers

id	email	password	lat	lng	name

typically it would be a restaurant owner/worker

deliveryHistory

id	deliveryUserId	businessUsersId	created_at

once an ordered has been delivered it would be added to the history

signupInvites

id	expiresAt	code	wasUsed

authorize users who has received the invite to be able to sign up to the app.

early planning

Techinical questions:

1. can i remember a mobile device ? (is there always going to be consistent indicator to connect the mobile device with the user in the db maybe)

reason to ask that question is cause i web development we use cookies and sessions to identify users, while applications don't really seem to ask you to sign in over and over again.

• Resources:
  • here is an article explaining react native auth flow, in the article he mentions AsyncStorage API for react-native

2. How can we deploy Expo app to AWS ?
3. Can we use Waze to for navigation ? (not have a Waze map in the app, more like a link that opens Waze)

my though process here was, the delivery person might receive an order but is not sure where the restaurant is located, while we would know. so it would be cool to add a link to Waze or Google maps that helps with navigation.
which then led me to my other question

4. should we have the restaurant owner/worker to also insert the client's address to help the delivery person find the place faster?

this not really an MVP thing

DB table

• deliveryUsers
• deliveryUsersSessions
• businessUsers
• deliveryHistory
• signupInvites

• firebase

there would an issue here linking for more details on each table
the tables names are open for change
signupInvites is so not everyone has an option to sign up and be a delivery person (cause they might be fake), instead they would get an invite link from the restaurant owner this needs a lot of thought

Notes:

• a user can only signup when invited to the app, the invitation link needs to hold a unique to be able to identify him.
• it would be awesome if we managed to somehow connect Waze to the app.
• use firebase for real fast updates, an example would be once someone updates their location or moves around, it would be instantly shown on the other user's map.