Back end

Database Structure Illustration

before vs after

Originally we wanted to use a similar option to what we used earlier where under a users collection each email would be a unique identifier then under each of these emails would be branches that lead to different lists identified by names that the user had created, but similar to the second iteration of our firestore data structure it would lead to the branches having the same identifier which would break the rules of the database. So instead of this we would restructure this part and the email would branch out into a generated unique ID and under this would be the listname and the items it contains. This way each list can be saved under its respected email and will be easier to retrieve. Once we had this figured out again it was just a matter of reworking what we had already created and learning to work with Realtime.