YES! Betsy articulates something I’ve been uneasy about for a while: the small but constant reinforcement (drip, drip, drip...) that a logged-in user is the default state.https://twitter.com/betsythemuffin/status/947125157289713664 …
-
-
At http://caring.com I modeled this with a user record and subclass that represented the guest user. We set current_user to that instance when not signed in. It worked pretty well. Being able to associate data to guest users is super useful.
-
We should have done this but didn't because we historically haven't had the need. But it would probably have been very easy to do up front and allowed us to ship this feature earlier. I don't regret the decision (one of a million pragmatic decisions) but I agree with
@sarahmei -
Absolutely. As a website (instead of an app) our default experience was a guest user and new user acquisition was a primary design goal so it forced us to think that way
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.