tadaspetra / bookclub Goto Github PK

• return string from CurrentUser state, so you can show the platform exception and what the problem is.
• show snackbar when exceptions happen.
• no need to chech authResult != null, if youre getting the exception from the state

• decide whos turn it is to reveal the next book, and only they get access to the button that adds a new book
• all other people have a "waiting for _____ to add book"

Before the app goes to the home screen, it shows the log in screen quickly. We don't want that

If a user logs into his book_club app from a new device he will only have notifications from the first device where he created the account

When logging in, there isn't any form validation.

• in the root widget, also check for a group state and whether the user is in a group or not.
• if not take the user to the join/create screen

Hi Mr. Petra, how are you?

I am finishing an app and found your video on creating a user on Firestore according to auth's uid very useful. However, I could not find the additional help from your source code. Would you mind uploading the code corresponding to your video? I would appreciate so much!

Thank you!

• design how the database is going to look

When you finish reading, add a review and what you think about the book

notifications for

• when you need to reveal book
• when the next book has been revealed
• a week before book club
• a day before book club
• book club time

• streams consume less data, apparently
• you will have realtime data for users and groups, so it will be better

docid: uid

• full name
• when account created
• email

• create a root widget
• upon app start up go to root widget, retrieve the current User and if exists go to home screen