Is a "Login Successful" Message Necessary?

  • On an informational/forum website (say, similar to a StackExchange site), is it necessary to show a "login successful" message?

    Clarification: On the site in question, the users can log in by clicking a "log in" button in the header. This reveals a small panel (overlaying the existing page) where they can log in. Once logged in, the "log in" button becomes a "log out" button in the header. The user never sees a dedicated "log in" page, per-se. The images below depict the current experience, which I think is along the lines of what Adriano Repetti has described in his answer:

    The "Log In" button appears when not logged in

    This box appears when the user clicks the "log in" button

    When user is logged in, the "log out" button is shown

    just a comment: I would change the logout button to red. So it reads green to enter and red to exit

    Good point @Matías, and I suppose another benefit in the change in button color that would accompany the log in/log out action would be the "subtle visual cue" to indicate the change in authentication state. Perhaps red is not the right color though? Doesn't red typically signal that some error has occurred?

    I don't think so, you could also use a red button for a delete action. So I think the context in which is used may signal an error has ocurred or not. In this particular case I believe it is safe to use red.

    @Matías, what about users with green-red color blindness?

    @Izam They can still read "login" / "logout" text change

    Avoid the red. Extrapolating from the small clip we're seeing, I assume the page will look like a greenish UI with a distracting red button in the corner.

    and by "greenish" you mean "bloody everything is illegible against a single and garish shade of green"

    yeah, that white on the green could be problematic on lots of screen types and for certain users with low colour differentiation abilities. In terms of calling attention to the log out with 'red' or really just drawing attention to it generally...I'd say don't do it. It's kind of a given the companies make log out hard to find because they want to keep your session going. Try to log out of facebook or twitter or even stackexchange and you'll find it's buried beneath at least 1 click. It also stops accidental sign outs because you have to deliberately seek it out.

  • Let me post an answer contrary to existing ones. A "login successful" message is not just unnecessary but it's also wrong.

    Why Unnecessary

    Think if objects/devices you use in everyday life will give you feedback each time you use them: "OK, you're using right key, you can turn the car's engine on", "Welcome back Adriano, this is your house", "Your PIN is correct, press OK to do what you expected to do", "Unlock gesture was right, swipe again to unlock the screen", and so on...

    Count how many sites/applications confirm a successful login: to log-in is part of workflow. Unless you give a confirmation message for each step then you do not need an (unmotivated) exception. Established behavior is - even alone - a reason strong enough, unless there is a well-recognized need (see notes).

    It's now trendy (when technically feasible) to even avoid confirmation messages, favoring more subtle feedback in conjunction with an undo functionality. If confirmations can/should be avoided then this argument is even stronger for non-functional informative messages.

    On the other side, of course, we expect an error page/message in case of errors.

    Keep notifications for what really matters because it may fail or if you do not have any other PERMANENT feedback of their result (when application state is clearly changed - and it MUST be clear when you're logged in - message is just redundant).

    Standalone Login Page

    It's unnecessary because, when the operation completes successfully, you move from the login page to another page. It's what we expect, with no need for confirmation.

    EDIT: after your edit this paragraph doesn't apply anymore, just ignore it in your specific case (however next one is specific); I keep it here for the general discussion.

    Popup Login Form

    This is true even when the login form is not a standalone page but a simple popup.

    Usually the control where you interacted to open the login form will change to show you're now logged in. In this case you may consider a subtle animation to give a feedback however (I say even if it's obvious) visible application state has to change to always remind users they're logged in.

    What do do to make clear you're logged in can be a topic for another question, you may change your top bar (if any), change your login button to become logout (but it has to be clearly different without being visually prominent), use (in addition) a different color scheme (carefully!) or...anything else according to your site design.

    Why Wrong

    It's wrong because it's unnecessary (and we want to keep our interface simple). Moreover, unnecessary messages slow down UX experience, break workflow and reduce user attention to meaningful messages (errors, alerts or important notifications).

    It doesn't matter how you show them (message box, dismissable box, popup or toast) -- if it's unnecessary it's also annoying and redundant.

    Notes

    When (for critical operations or access to sensible/reserved information) there is a multi-step login process then you should have a clear standalone page to inform the user that they are logged in and can now access reserved data and/or be able to perform dangerous operations.

    Text Vs Something Else: if the purpose is to give feedback then text is worse than other options. With text you need to read but the message is simply a confirmation of something you already know. This kind of informational messages should be used sparely otherwise users will simply ignore them all.

    Exactly same reasoning may be applied to logout. Unless there is a special reason then no message is required. Also note that logout control may be more prominent if you want to remember your users to perform logout.

    In your screenshot I see "sign up" and "log in" fields, if your audience isn't only English native speakers you may consider to use a different wording (see also What is the difference between "sign in" and "log in" and how websites choose one VS. the other?).

    What you are describing here is similar to the experience I am currently working with (and I have posted edits to the question above to illustrate). I am in agreement with you in that less is more, and that less (unnecessary) reading is key.

    I saw your edit, in that page I'd just consider to add some subtle animation (or whatever your current design uses to give feedback for changes) to highlight transition in that button after login. Well I'd also consider to make it more visually different, not just text content but - for example - color AND layout. If its only purpose is log-out I'd also make it less visually prominent.

    "you move from the login page to another page" Your assertion here is incorrect from my reading of the question. Does that change your answer any?

    @jpmc26 yes, it has been added in a later edit but everything else still applies (anyway I did edit answer it clear). My main point is "it's redundant then useless. Because it's useless it's annoying, it breaks my workflow and if application is polluted with annoying messages I'll end up ignoring important ones".

License under CC-BY-SA with attribution


Content dated before 7/24/2021 11:53 AM