You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a user, when creating a new round, it could be nice to add "guests", meaning people that don't have Frolfr accounts and just want to keep their scores. We could then invite them after the round is over (or even before) via email.
However, I'm also open to the discussion of killing this "guests" idea. Could get messy, and it's really not that hard to make an account. I don't know which is a better user experience.
The text was updated successfully, but these errors were encountered:
Hmm.... I guess we could have scorecards with null user ids, which would indicate that whoever has that scorecard is a guest. (This would complicate things because we'd still need to store these guest's names or identifying information somewhere-- otherwise we won't be able to say whose scorecard belongs to whom if there are multiple guests on a single round.) Another approach might be to go ahead and create user accounts for guests when they're added to a round, but don't give them any login information until later: maybe once a round is over, the round owner can enter their email addresses, at which point we can send them a round recap and ask them to create an account.
From a UX perspective, it'd be nice because it would decrease the friction of using Frolfr: if you're at a park (or whatever) with your friends, you can just start playing rather than having your friends have to futz around on their phones for 20 minutes beforehand.
As a user, when creating a new round, it could be nice to add "guests", meaning people that don't have Frolfr accounts and just want to keep their scores. We could then invite them after the round is over (or even before) via email.
However, I'm also open to the discussion of killing this "guests" idea. Could get messy, and it's really not that hard to make an account. I don't know which is a better user experience.
The text was updated successfully, but these errors were encountered: