Skip to content

HapticFeedback: Support UINotificationFeedbackType.success/warning/error on iOS #150029

Closed

Description

@yuukiw00w

Use case

When notifying the user of the success or failure of an action through vibration, I would like to use the standard API on iOS.
As an alternative, I am currently using one of HapticFeedback's heavyImpact/lightImpact/mediumImpact/selectionClick/vibrate, but this does not provide the expected vibration feedback on iOS.

Proposal

iOS provides an API called UINotificationFeedbackGenerator, which is designed to notify users of the outcome of an action. While HapticFeedback currently supports three types of vibration (UIImpactFeedbackGenerator, UISelectionFeedbackGenerator, and kSystemSoundID_Vibrate), adding UINotificationFeedbackType’s success/warning/error would allow for standard vibration notifications for the success or failure of a user action. Therefore, it would be great if the following HapticFeedback API could be provided:

  • success(): UINotificationFeedbackType.success on iOS, HapticFeedbackConstants.CONFIRM on Android
  • warning(): UINotificationFeedbackType.warning on iOS, HapticFeedbackConstants.REJECT on Android
  • error(): UINotificationFeedbackType.error on iOS, HapticFeedbackConstants.REJECT on Android

Note that there may be room for discussion regarding warning(), as there is no direct equivalent on Android.

Activity

  1. added
    in triagePresently being triaged by the triage team
    c: new featureNothing broken; request for a new capability
    platform-iosiOS applications specifically
    frameworkflutter/packages/flutter repository. See also f: labels.
    c: proposalA detailed proposal for a change to Flutter
    team-iosOwned by iOS platform team
    and removed
    in triagePresently being triaged by the triage team
    on Jun 11, 2024
  2. added
    P3Issues that are less important to the Flutter project
    triaged-iosTriaged by iOS platform team
    on Jun 12, 2024
  3. jasminder commented on Jul 17, 2024

    @jasminder
  4. JustinFay01 commented on Jun 2, 2025

    @JustinFay01
  5. self-assigned this
    on Oct 28, 2025
  6. moved this from To do to In progress in Nevercodeon Oct 28, 2025
  7. moved this from In progress to PR submitted in Nevercodeon Oct 29, 2025
  8. moved this from PR submitted to Done (PR merged) in Nevercodeon Nov 7, 2025
  9. github-actions commented on Nov 21, 2025

    @github-actions

    This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

  10. locked as resolved and limited conversation to collaborators on Nov 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

P3Issues that are less important to the Flutter projectc: new featureNothing broken; request for a new capabilityc: proposalA detailed proposal for a change to Flutterframeworkflutter/packages/flutter repository. See also f: labels.platform-iosiOS applications specificallyteam-iosOwned by iOS platform teamtriaged-iosTriaged by iOS platform team

Type

No type

Projects

  • Status
    Done (PR merged)

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions