TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Log in or sign up?

67 点作者 r11t超过 15 年前

12 条评论

drusenko超过 15 年前
Leah's asking the right questions, but I don't think the direction she took is the right one. Users rely on the UI to be familiar, and I've always found Amazon's UI strange in that I have to pause, analyze, and think when logging in/signing up. While Amazon might be able to get away with it, removing the familiarity from the UI is probably a bad decision for most. If an extra field is a barrier to sign-up, the user actually having to actively analyze and parse your sign-up form is a huge mental hoop to jump through.<p>We (Weebly) thought of this problem early on, and we tried to simplify things by just requiring an email/password when signing up. What we found was that our users <i>were extremely confused</i>, because the sign-up form didn't look like a sign-up form. When doing usability testing, we found that users would stare at the page for minutes. "us: Just sign up..." "user: I can't see where to sign up", even when it was right in front of them. They saw two fields and assumed it was a log-in form, even when it said in really big letters "Create a new account".<p>Users don't read your page, they scan it. People expect the log-in form to be in the upper right and the sign-up form to be towards the center of the page. You should absolutely make your site scan-friendly.<p>Users do, though, get confused and try to use the sign-up form to login. Our solution? If the user enters credentials into the sign-up form that already exist (like the correct username/password combo), we'll just log them in instead of creating a new user. You can try it out on weebly.com.
评论 #943277 未加载
评论 #942381 未加载
patio11超过 15 年前
Even if you're not going to go the full monty and change the user-visible interaction, you can file off some of the sharp edges. For example, I have the traditional sign in and register forms, and (predictably, given that my customers are not too tech savvy and the forms look similar if you read none of the words on them which, after all, is the default behavior on the Internet) many people use the wrong one.<p>Since user intent is clear if they try to register a user name and password that are already in your database, rather than giving them a "that account already exists" error I just log them in straight away.
rufo超过 15 年前
There's an interesting point made, but I'm not sure that I really like the direction Leah went in. To me, the fields stand out far more than the radio buttons, I stop reading the header after "Log in..." (what more do I need to know, it's a login form) and I really wouldn't notice that it's a sign-up form unless I look carefully - I had to look twice before I realized there was even a difference between the two screenshots.<p>I'd probably ditch the radio buttons and make the header more eyecatching, with "Join Now?" clearly a link. Clicking it changes the form in the way Leah shows, probably with a quick Javascript fade so the user notices.
评论 #942087 未加载
zck超过 15 年前
Especially in this case, when you don't ask for an email, it seems like a mistake to only get the password once. If someone mistypes it, there's no way to get them access to their account again.<p>And yes, I'm aware HN has this problem, unless you go in and put your email in your profile.
评论 #942068 未加载
Tichy超过 15 年前
I wish Amazon would preselect the "existing user" option, or at least have a JavaScript that selects it as soon as I type the password.
评论 #942434 未加载
vl超过 15 年前
I think that there are two problems with approach taken on hurl's homepage: 1) New user may be confused and not discover sign up functionality behind log in link. 2) Two buttons in the dialog require thinking each time when existing user logs in (i.e. common scenario).<p>When I was designing Memengo's homepage (<a href="http://www.memengo.com" rel="nofollow">http://www.memengo.com</a>), I was trying to provide streamlined execution path for 3 different scenarios: see demo, register, log in.<p>I hate web sites that have tiny log in link in the top-right corner. After all, I usually visit home page to log in immediately, so I expect email and password fields to be provided right there.<p>To streamline sign up there is a need to ask as few things as possible, preferably on home page as well.<p>Potential users should be aware that there is a no-strings-attached functional demo one click away, so this area requires some screen estate as well.<p>The final design: 3 equally sized boxes on the bottom of the page: 1 click demo, Sign up (with all required fields), Log in (with all required fields).
snprbob86超过 15 年前
We independently conceived of Hurl's approach. It looked like this: <a href="http://imgur.com/Th9yi" rel="nofollow">http://imgur.com/Th9yi</a><p>Maybe it was just a function of our design, but the feedback was that people didn't read and thought it was a login-only form. People are just conditioned to seeing long sign-up forms. A username/password pair just screams "login"!<p>There is enough innovation in the rest of our app to worry about, we didn't also need to be re-inventing authentication. Our login and sign-up forms are now on two separate pages and we added "Remember me" and "Confirm password" to the respective pages. Both pages have a link to the other.<p>We're trying to funnel users through the workflow such that we can present the correct page the vast majority of the time. For example, many features can be tried before making an account, but you get to them by clicking "try it now". Once you have an account, you get to them from your dashboard. This way, we can reasonably assume a user is new if they aren't authenticated already when they go to use such a feature.
thwarted超过 15 年前
<i>"Sometimes I put my log in information into the register fields." "Me too! I hate that not only do I feel stupid, I have to retype everything again."</i><p>I hate the page LinkedIn shows when you're not logged in, it asks you to signup, and the login page is actually a different one. I find the call to action to register stands out, but they seem to hide the link to the login page. I never feel stupid when I encounter this, I feel like the site doesn't want repeat users, they want new user signups, and don't care if you end up recreating your account (this may explain why I've seen so many duplicate and inactive accounts on LinkedIn).
NikkiA超过 15 年前
I agree with the direction one of the comments takes - if you're going to this trouble, why differentiate, if the username isn't taken, take the user straight to a 'confirm your password to create account'. One dialog box, two functions. Having to notice and choose the radiobutton is just another barrier to both types of users.
评论 #942008 未加载
评论 #941965 未加载
评论 #942033 未加载
评论 #941968 未加载
jeremyw超过 15 年前
Some Google research comes to the same conclusion Leah does, with slightly different behavior.<p><a href="http://sites.google.com/site/oauthgoog/UXFedLogin" rel="nofollow">http://sites.google.com/site/oauthgoog/UXFedLogin</a>
yummyfajitas超过 15 年前
Mathjobs.org uses something along those lines, though in my opinion better than this implementation.<p><a href="https://www.mathjobs.org/jobs?info-ja" rel="nofollow">https://www.mathjobs.org/jobs?info-ja</a>
aw3c2超过 15 年前
Don't rely on Javascript for things this important.