I have been searching all over for this, and I just haven't been able to find a clear answer to my questions.
I'm developing an app for a client and using Firebase as my backend (it's my first time). I need each user account to have it's own calendar.
I will be using the Firebase O-Auth but I don't want my app to see or edit a users auth account calendar (ie: if a google user logs in I don't want to edit their google calendar). I want our database to store a unique calendar for each unique user.
Will the calendar API allow me to do this? The app could potentially have thousands of calendars. I've seen some docs about limits, but it seems like limits on api calls, which I don't have any estimates for at this time.
Would a service account be appropriate for this application?
I've checked these other posts, but they don't quite answer my questions:
How to create a scalable calendar service backend for an Android app?
Google Calendar API - Designed for?
Any kind of insight would be much appreciated. Thanks!
Generally what we do in this case is create calendars using documents and collections within Firebase. Here is an example of a calendar app that uses Firebase to store its appointments. It is written in Flutter, but the backend design for Firebase should be easy to understand.