Skip to content

Give haptic feedback (errorNotification) when showing an error dialog #2338

Closed

Description

@chrisbobbe

showErrorDialog is our single "something went wrong" surface, so it's a natural place to add tactile error feedback rather than wiring it per-feature. Proposal: fire HapticFeedback.errorNotification() in showErrorDialog, so every error dialog gives a consistent error haptic (iOS UINotificationFeedbackTypeError; Android HapticFeedbackConstants.REJECT, API 30+).

Scope it to showErrorDialog only — not showSuggestedActionDialog, which is a choice rather than an error.

Came up while reviewing #2325 (double-tap to react); keeping it out of that PR since it's an app-wide change worth deciding on its own.

Activity

  1. added this to the MXB: Future milestone on Jun 12, 2026
  2. sharayuwadghule commented on Jun 17, 2026

    @sharayuwadghule
    Contributor

    Hi @chrisbobbe,

    I'd like to work on this issue if it's available.

    The proposed change seems straightforward and localized to showErrorDialog, and I'd be happy to implement it while keeping the scope limited to error dialogs as described.

    Please let me know if I can take this up.

    Thanks!

  3. added 9 commits that reference this issue on Jun 22, 2026
    505e167
    6965eaf
    bda790e
    01049a8
    4abbbd2
    d4aa384
    3d8ef9d
    f0674cf
    f4c2a68
  4. added 4 commits that reference this issue on Jul 3, 2026
    6c1064f
    b5e8358
    3fa6dbd
    ba220b2
  5. added a commit that references this issue on Jul 17, 2026
    6d72e05
  6. added a commit that references this issue on Jul 25, 2026
    30443ef
  7. added 2 commits that reference this issue on Aug 4, 2026
    91eda98
    0a95dc4
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

a-designVisual and UX design

Type

No type

Projects

Relationships

None yet

Development

No branches or pull requests

Issue actions