Haptics setting?

[RKBoss6]

As you can probably tell, I LOVE haptics. However, not everyone does, and adding haptics to the back widget has recently been met with complaints. So, what if we had a setting in system, along with a Bangle.setOptions({haptics:true}) to make a setting for haptics? When it's off, haptics in menus and back widgets won't trigger, and when on, they will, along with maybe haptics for prompts and alerts. To me, haptics are a physical way to make sure you hit what you wanted to, and I understand it's not for everyone. I've been wanting haptics in more system-wide functions like menus, and I think this is the best way to go about it. I've considered making an app, but realistically, it's probably better off as an option in system settings instead, as it affects all system-level stuff, and the storage space and load time would be massive with overriding 3 fw functions. What do you all think?

[gfwilliams]

I was wondering about this at the time the complaints came in.

I think it makes sense to introduce a Bangle.haptic method that the built-in functions can call (we can polyfill this in boot for older firmwares too). So you can call Bangle.haptic("back") or Bangle.haptic("press") for instance - by default it just pulses for 20ms or so unless disabled via an option, but someone could have an app that overloads the function to do different haptic responses for different types of event?

[RKBoss6]

That actually sounds really nice! We could do something like when the setting is off, just don't buzz in the bangle.haptic method.

[RKBoss6]

I think if we want, we can also add a setting for haptic strength later on, if the need is there. For now though, this plan sounds perfect. Should I make a PR for this then, or would you want to do it yourself?
Edit: like you said, for more customization on top of that, I think it's best if we did an app. I like all the haptic strengths now, so keeping those the same would be good I think.