Team config, lineup, and scoreboard are now persisted to Firestore. We are one big step closer to sharing.
How this works is a unique ID is generated by the client and this is used as the Firestore document ID. (The ID is kept in local storage on the client. If it is lost/forgotten, the client will create a new one and lose access to the old data.)
It is important to note that this is not secure, however, as these IDs are not encrypted and can be queried through the Firestore API. We are only trying to implement a rough proof of concept, though.
Team config, lineup, and scoreboard are now persisted to Firestore. We are one big step closer to sharing.
How this works is a unique ID is generated by the client and this is used as the Firestore document ID. (The ID is kept in local storage on the client. If it is lost/forgotten, the client will create a new one and lose access to the old data.)
It is important to note that this is not secure, however, as these IDs are not encrypted and can be queried through the Firestore API. We are only trying to implement a rough proof of concept, though.