Status-react: Contextual bottom sheet on long press

Created on 11 Mar 2019  ·  18Comments  ·  Source: status-im/status-react

Problem

In order to remove a chat, we currently use a 'swipe to delete' approach in the chat list. We'd like to replace 'swipe to delete' in places where it is used with 'longpress to delete' and introduce this appproach in places where currently a top right overflow menu is used.

'Swipte to delete' is a pattern that is known to not be intuitive for users across platforms. Its main downside being discoverability. https://www.nngroup.com/articles/contextual-swipe/

In testing we experimented with long press and observed most users attempt long press when searching for a delete option. Next to this, long press provides the option to introduce a more scalable context menu, the existing [bottom sheet] component.

Related UXR report:https://docs.google.com/presentation/d/10qb5jRXwRT9lYkxrn8Ui5Bov_JRuf1WBaPqSXd0ZAtY/edit#slide=id.g3f411e60e9_0_168

Implementation

long-press should trigger [bottom sheet] component with the following contextual menu items:

Public chats:
-> Share chat
-> Delete chat -red-

Private chats
-> View profile
-> Delete chat -red-

Groups
-> Group info
-> Delete and leave group -red-

Acceptance Criteria

Notes

Future Steps

UUX improvements better-mobile-app bounty-m

Most helpful comment

focusing completely on this now, now that another PR that was also being worked on along with this is in ready-to-review state

All 18 comments

Link to Figma with an example of correct implementation, red is used to highlight destructive actions

Issue Status: 1. Open 2. Started 3. Submitted 4. Done


__This issue now has a funding of 300.0 DAI (300.0 USD @ $1.0/DAI) attached to it.__

Issue Status: 1. Open 2. Started 3. Submitted 4. Done


__Work has been started__.

These users each claimed they can complete the work by 11 months from now.
Please review their action plans below:

1) bitsikka has been approved to start work.

  • locate source where swipe to delete functionality is located
  • replace/fix/re-factor it with longpress to delete as described in the issue/shown in design

Having worked on several chat issues recently I believe I may have additional contextual background needed for this

Learn more on the Gitcoin Issue Details page.

@bitsikka Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

  • [x] reminder (3 days)
  • [ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

@gitcoinbot currently occupied with another bounty, will be on this soon.

@bitsikka Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

  • [x] reminder (3 days)
  • [ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

@gitcoinbot working on initial PR

@bitsikka Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

  • [x] reminder (3 days)
  • [ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

@gitcoinbot yes, still working

Just barely got my development machine in order after having it being broken more than a week ago

Please bare with me

@bitsikka Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

  • [x] reminder (3 days)
  • [ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

@gitcoinbot yes, working on it

focusing completely on this now, now that another PR that was also being worked on along with this is in ready-to-review state

@bitsikka Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

  • [x] reminder (3 days)
  • [ ] escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

@gitcoinbot ran into some more build system hiccups, but making good progress nevertheless. Almost ready with full PR with fleshed out feature.

Issue Status: 1. Open 2. Started 3. Submitted 4. Done


__Work for 300.0 DAI (300.0 USD @ $1.0/DAI) has been submitted by__:

  1. @bitsikka

@StatusSceptre please take a look at the submitted work:

  • (Link Not Provided) by @bitsikka

Narwhal ⚡️ A *Narwhal* Kudos has been sent to @bitsikka for this issue from @StatusSceptre. ⚡️ The sender had the following public comments: > Thanks Bitsikka! Great work! Nice work @bitsikka! Your Kudos has automatically been sent in the ETH address we have on file.

Issue Status: 1. Open 2. Started 3. Submitted 4. Done


__The funding of 300.0 DAI (300.0 USD @ $1.0/DAI) attached to this issue has been approved & issued to @bitsikka.__

Was this page helpful?
0 / 5 - 0 ratings