Skip to content

A note about "Exit" buttons #19

@nikolasleblanc

Description

@nikolasleblanc

So, just a reminder about the exit button, it’s not really a “thing”. I realize you’re trying to provide closure to the user, but I’d recommend that that be established via text over interaction, especially one that attempts to manipulate the user’s browser window (generally frowned upon by browser manufacturers to the extent that it's not allowed). Some examples of situations where an exit button could exist but does not:

  • After an online purchase
  • After a bank transaction (more specifically, a one-task transaction such as the receipt of an email money transfer)
  • SurveyMonkey

In all cases, the pattern is to communicate the finality of the action, and to provide ways for the user to move forward - either with related links or calls to action. In our case, that could be directing the user to a stakeholder website, or to the KT website, or to more information about how the tool was developed, what it’s based on, etc.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions