Skip to content
This repository has been archived by the owner on Oct 12, 2022. It is now read-only.

Add warning/confirmation to tab closure on Send instructions screen #21

Open
on-ba opened this issue Jul 6, 2021 · 1 comment
Open
Labels

Comments

@on-ba
Copy link
Contributor

on-ba commented Jul 6, 2021

Improvement

Existing behavior

  1. Sender selects or drops a file to send from the Send / default screen.
  2. On the Send instructions screen, they are presented with a code/link to share with the intended recipient.
  3. After the intended recipient has successfully opened the link or entered the code, and has accepted the download, the Sender will see the Send instructions screen switch to the Send progress screen, and if uninterrupted, to the Send complete screen.
  4. However, if they close the tab or navigate to a different page before reaching the Send complete screen, the file transfer will fail.

We are communicating on the Send instructions screen that the sender needs to keep the tab open. However, this message may not be read or clearly understood.

Based on user testing, people seem to be less familiar with synchronous file transfers and do not commonly expect that they need to keep this tab active for the recipient to be able to download the file.

New behavior

To help avoid people closing/navigating away from the Send instructions screen, we want to experiment with adding an "Are you sure?" step to this.

This could take the shape of a dialog along the lines of whether the user is sure they want to discard existing changes--something that can help alert them to the fact that this action will have consequences, and possibly bring closer attention to the copy explaining that the tab needs to be kept open.

If we can customize the copy in this dialog, it could take the form of:

Closing this tab will cancel the file transfer.
Are you sure you want to close the tab?
Yes, cancel transfer / No

Risks/tradeoffs

For users who intentionally close the tab while understanding the consequences, this will add unnecessary friction.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant