wtf is up with this design pattern on web apps where there are huge text fields for username and password on the home page and so you type in your username and password only to realize that the button below it says "Create an account!" and then you have to hunt for the tiny "ˢⁱᵍⁿ ⁱⁿ" button in the upper right-hand corner in order to actually sign in to your existing account?
@nightpool the new-user experience is important, since every user will see it, but they only experience it once. I don't think there's at all a zero-sum exchange between ease for new and returning users (perhaps minimal tension, but having clearly labelled buttons for signup/login seems fine), but shoving a common workflow behind an extra page load (several seconds and a mental context switch) seems unnecessarily ungracious
@nightpool @martensitingale Do you know of any studies that look at the impact of such design on the fraction of users who visit the site and then are still active after say 30 days? My guess is that the impact is pretty small since the users who wouldn't spend even a little bit of time looking for how to register are probably very likely to just drop off after registering.
@nightpool If you just treat them as raw rates and ignore how you're achieving changes in the rates, then sure. But let's say 10% of users who visit your site register and 50% of those are still using the app after 30 days, so the funnel to 30 days is 5%. If you were to make registration automatic by just sticking a cookie on their machine so they didn't need to do anything at all to have an account, do you really think that would result in a 1000% increase in people still active after 30 days?
@nightpool @martensitingale i understand your underlying point but there has to be a way to optimize for first-time users that isn't incredibly frustrating for returning users. the two use cases aren't zero sum. also consider that i (and others like me) are less likely to even sign up for a service that obscures the existing-user sign in
But just a note--how this thread appears depends on how & when one comes into it, so what you think may have been clear maybe wasn't so much. I read a lot of people's stuff. Sure, I probably could have known you were a Masto dev, but that wasn't context I brought to my read of your early comments. The Masto-specific aspects of this have been secondary to me because I tend not to use its front-end, it having this...property...is only part of the reason.
@nightpool What's more, I try to resist the notion popular in some corners of the fediverse that there's something ... insular, to try to put it kindly ... about the Mastodon portion of the fediverse. But it's hard not to credit that when comments about just one behavior of one web front end are conflated into a love-it-or-leave-it type of response. I use the Mastodon back end, because that's what the people who run our instance use, is the easiest way to put this.
@nightpool In short, I'm not trying to make you feel bad about this. It's feedback: This is a thing I dislike about so many web sites. So, this struck a nerve. This is a thing to which the fediverse's target user base is probably *more* sensitive to, since so many of us are more likely to do things to break the persistence of log in (private tabs, clear browser history, etc), so we encounter it more often across sites than the audience web developers typically target.
@deejoe I get that this can be a annoying behavior for people, and I respect that. but I guess I struggle so much with it because I expect people on the fediverse to be able to look past their own needs and see the needs of the community, and that rarely happens.
@deejoe I'm not saying the front end is love it or leave it. I'm saying you're approaching this whole conversation in a tribal, us vs. them way, and you have been since the very beginning when mastodon wasn't even on the table.
I tried to drive home how reductive and pointless that was by using mastodon as an example, and you responded by just getting deeper entrenched into your "outgroup" mindset.
Like, I don't think it's so great that mastodon.social still has open registrations at all, we should be directing people to other instances, reduce the centrality
You might disagree with me on that, but cybre.space does limit the rate of registrations, prioritizing the needs of existing users over prospective ones. I think that's fine, makes the community easier to moderate
Perhaps new instances should have different login pages than established ones
1. welcoming and supporting new users
2. maximizing the uptake of prospective users
The former has to be primarily a function of the community's treatment of new users, which eg. well designed moderation tools can help with
The latter, well, it might be in your interest if your objective is to supplant Twitter, but not everyone cares about that
@LogicalDash sure, "welcomes new users" doesn't necessarily mean supporting an unsustainable rate of growth, and having a NETWORK that makes onboarding easy doesn't mean individual instances should necessarily be open at all times. I don't think any of these really detract from the point I was trying to make.
Look. You can consider different classes or groups of participants, or not. You are doing it, I am doing it. The difference is I'm reporting directly on my own experiences and preferences, and you are speculating about what might be happening in a group you really aren't in. Sure, ok, you've taken on a responsibility to think about who design decisions might exclude, but that's no call to get so sanctimonious about it and start slagging me off.
Gonna mute this conversation because I've said my piece about this functionality. The rest just seems to be devolving into something not that useful or helpful to anyone.
@aparrish well I think there's a difference between "arriving on a site for the first time" and "going back to a site". retention is important and difficult to optimize for and deserves a lot of effort, but once you've literally typed https://mastodon.social into your web browser then like, you've already MADE the decision to come back.
as the saying goes, "acquisition happens on-site. retention happens off-site"
@nightpool @aparrish yeah, i....... also generally find this pretty irritating. ( especially on sites where, like, actually finding the log in part is difficult / requires typing in a different url. although they probably would rather you just ~stay signed in~. )
but, like, not irritated enough to, uhh, dooooo anything about it. 😣
(answer: because the only kpi reliably communicated to ux and devs is the number of new signups and they don't actually care about providing the service of the application as much as they care about hockey puck user count graphs and gathering your data for resale and sending you e-mail newsletters)
as in if you type your organization's email address and it sees the domain part matches an SSO integration, it redirects you to the SSO page
a click is a bit much, I agree. At least some pages still just let you tab
@aparrish At least _sometimes_ they're smart enough to just log you in if you just put in your username and password and click "sign up" but the ones that aren't... AAAAAAAARRRRGGGGHHHH
@aparrish I have like five accounts on CamelCamelCamel because it lets you set up an anonymous watch, but then if you go to sign in it gives you a little warning that it will create a *new* account, and I only see that warning after LastPass autofills and I click it and WHY WOULD IT CREATE A NEW ACCOUNT WHY