This involves updating our data flows for new lesson requests, appointments, clock-in and out; this should not be taken lightly.
The only thing that wouldn't change too much is how we store attendees in each appointment Firestore document (where it's just an array of Profiles).
But we'd have to update the way we work with lesson requests (where there's only one fromUser and only one toUser field). And we'd have to update the UI to show all the different attendees and their various roles with the appointment (e.g. Do we have one tutor with multiple students? Or is there multiple tutors for a single student? Or a combination of both?).
This involves updating our data flows for new lesson requests, appointments, clock-in and out; this should not be taken lightly.
The only thing that wouldn't change too much is how we store
attendeesin eachappointmentFirestore document (where it's just an array ofProfiles).But we'd have to update the way we work with lesson requests (where there's only one
fromUserand only onetoUserfield). And we'd have to update the UI to show all the different attendees and their various roles with the appointment (e.g. Do we have one tutor with multiple students? Or is there multiple tutors for a single student? Or a combination of both?).