haptic_feedback

What's Changed

• fix(ios): link FlutterFramework in SPM Package.swift by @kuailezhiyuan in #109

New Contributors

• @kuailezhiyuan made their first contribution in #109

Full Changelog: 0.6.4...0.6.5

• Fix iOS Swift Package Manager build: link FlutterFramework in Package.swift (resolves undefined symbols FlutterMethodChannel, FlutterMethodNotImplemented when using Flutter SPM).

What's Changed

• Add Swift Package Manager support for iOS by @Copilot in #96
• Add tests, update readme by @nohli in #97

Full Changelog: 0.6.3...0.6.4

• Add Swift Package Manager (SPM) support for iOS.

What's Changed

• Update readme

Full Changelog: 0.6.4...0.6.4+1

• Update readme.

What's Changed

• Update readme

Full Changelog: 0.6.4+1...0.6.4+2

• Update readme.

What's Changed

• Update pub.dev topic tag and version by @Copilot in #99

Full Changelog: 0.6.4+2...0.6.4+3

• Update pub.dev topic.

What's Changed

• Bump futureware-tech/simulator-action from 4 to 5 by @dependabot[bot] in #101
• Bump actions/checkout from 6 to 7 by @dependabot[bot] in #110
• docs: update haptic types guide link in README by @kamranbekirovyz in #105

Full Changelog: 0.6.4+3...0.6.4+4

• Update readme (article link).

What's Changed

• Use haptic primitives and native HapticFeedbackConstants for better vibrations on Android 11+ by @Copilot in #94

Full Changelog: 0.6.2...0.6.3

• Behavior change: Android haptics improve on API 30+ devices—especially those with advanced/HD hardware—using a layered strategy with explicit fallbacks:
  • Default: haptic primitives via VibrationEffect.Composition on API 30+ (Android 11+) tuned to the iOS patterns.
  • Fallback: waveform vibration on API 26-29.
  • Fallback: legacy timing-only vibration on API < 26.
• Add useAndroidHapticConstants parameter (default: false) to opt into Android's system-level haptic constants (CONFIRM, REJECT, etc.) on supported SDK levels; otherwise the layered primitives/waveform/legacy path is used.
• Use VibratorManager on Android 12+ for better vibrator access.

What's Changed

• Update readme

Full Changelog: 0.6.3...0.6.3+1

• Update readme.

What's Changed

• Update readme and changelog

Full Changelog: 0.6.3+1...0.6.3+2

• Update readme and changelog.

What's Changed

• Add tests, update readme by @nohli in #97

Full Changelog: 0.6.3+2...0.6.3+3

• Update readme.

• Fix legacy Android vibration on SDK 24/25 (Android 7.0/7.1): without a leading 0ms delay the first pulse became a pause and the pattern lost a buzz; prepending 0 keeps the intended multi-pulse sequence.

• Add optional usage parameter to control vibration category on Android 13+ devices. This allows you to specify how the haptic feedback should be categorized (e.g., for notifications, alarms, touch feedback, etc.), which helps the system handle vibrations more appropriately.

• Breaking: Flutter SDK constraint is now >=3.10.0 (Dart 3-only). Apps on older Flutter versions can’t upgrade.

• Update podspec version.

• Add an article link about using the plugin to the readme. Thanks @kamranbekirovyz!

• Update article link.

• Early return if platform is not supported (instead of an exception). Supported are iOS an Android. Thanks @rizerco!
• Upgrade Android dependencies (Gradle, AGP, Java, Kotlin).
• Widen flutter_lints constraints.

• Update package description.

• Update example.

• canVibrate() is now a method.
• Catching of native errors on Android: You can call vibrate() without checking canVibrate() first.
• Improve docs.

• Update podspec version.

• Fix typo in readme. Thanks @walid-ashik!

• Maintenance release.
• Update gradle, kotlin, and mockito.

• Update podspec version.

• Update package identifier.

• Refactor example.

• Small refactoring.

• Check API level before calling hasAmplitudeControl().

• Update version in podspec.

• Refactor Kotlin code.

• Improve docs.
• Add private constructor to Haptics.

• Improve docs.

• Format Swift code.

• Call fallback methods on iOS < 13 for .rigid and .soft haptics.

• Refactor canVibrate implementation for supporting lower iOS versions.

• Format native code.

• Refactor canVibrate method into a getter for improved readability and usage.

• Make methods static.

• Add namespace to build.gradle.
• Update Kotlin version of example.
• Upgrade Gradle version of example.
• Upgrade Android Gradle Plugin version of example.

• Fine-tune Android haptics.

• Update description.

• Initial release.