Instead of duplicating the data for contracts as suggested by #42, an approach similar to seasons should be implemented:
[ ] Global contract meta data
This will hold data like names, total xp amounts and colors
[ ] User specific states
Within user data only the state (active, paused, completed or ended) and the amount of collected xp should be tracked
When an admin creates a new contract, there is no need for a cloud function anymore, since the client pulls all contract meta data at startup und creates the corresponding user data if not existing.
Instead of duplicating the data for contracts as suggested by #42, an approach similar to seasons should be implemented:
When an admin creates a new contract, there is no need for a cloud function anymore, since the client pulls all contract meta data at startup und creates the corresponding user data if not existing.
Because of this, #42 will now be dropped