How to Use
Playing haptic feedback is as simple as calling the SendHapticFeedback client action. It takes two parameters: the Android type and iOS type, which correspond to their respective system haptic feedback constants (see implementation details below for what the possible values are, and what types of feedback they provide). This client action is non-blocking (e.g. does not wait for an "OK" plugin result and making use of $resolve()) unless there is an error, in which case it uses the standard CommonPlugin Error structure.
Android Implementation
The Android haptic system makes use of the View component pattern and all related constants (see below). Some of these constants require Android API level 34+, so keep that in mind when choosing your MABS version.
iOS Implementation
The iOS haptic systems makes use of the UIFeedbackGenerator subclasses and constants from UIKit, with the exception of UICanvasFeedbackGenerator. Some of the constants require iOS 13+ thus the plugin requirements. Note that these classes are generated on the fly when the feedback is sent in this plugin without making use of prepare() ahead of time, so keep that in mind when considering latency. Also, location-based feedback (passing location coordinates) is not supported, though I might add support in future releases. The constants are: