0

I've been looking for any standards around haptic feedback of a mobile device when it tries to send out an alert for security but failed. I haven't found any clear answers so hoping I'll get some guidance here. :)

So the app I'm designing is for the security of the user that when they find themselves in a threatening or dangerous situation, they will call for help by pressing a button on the device. But if the device couldn't send the alert for some reason, the user should be made known that the device cant help you, it failed to send the alert.

I have checked a similar answer saying the distress signals are sent in sets of three, but this is not a distress signal, it's a feedback that the distress signal could not be sent. Any recommendations?

0

I don't think you're going to find any standards, what you are going to have to do is ensure that the positive outcome and the negative outcome are discernable.

I'm making an assumption that the reason you're using the haptics is because the device can be kept on the person, and the user would not need to hold the device in their hand to receive feedback on whether there request for help had gone through?

I would caution a couple of things: why would someone utilise this against calling a recognised emergency service? I have a background in law enforcement and, not always the case, but occasionally the fact that an operator can tell the caller to inform any perpetrator that the call is being recorded, the police are on route and they can hear everything being said, can be a deterrent. Furthermore, here in the UK (you'd have to check local policies if you're not UK based) people are advised, even if they can't talk, to dial 999 and when the operator answers - key 55, the operator will put the call through to the police as an emergency call, with similar actions taken as to the above.

Secondly; a cellular call is often more reliable than a data send, the reassurance provided by an app could be severely damaged if it doesn't achieve the aim of the application.

If there is another user case for actually doing this - I would ensure that the response is as identifiable as a result - i.e. a double buzz of the haptic is used far too often by many apps that provide notifications.

I would suggest you would look at a pattern that is:

  1. Easily identifiable
  2. Not easily confused with other notifications, including those within the same app
  3. Any ongoing notifications required to indicate that, perhaps, the app is trying again and then changes to a success or continues to indicate failure.

I hope this help.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.