Description
I use FareBot regularly, and I'm convinced that it's a design mistake to vibrate as confirmation of an NFC connection. I understand that this detection event is relevant to the user and deserves some kind of feedback, but in my experience this kind of vibration pulse communicates that the desired operation is complete, which is contrary to the design goals.
I know all-too-well that FareBot triggers the phone to vibrate when it registers an NFC connection, but this feedback subconsciously signals successful completion of the data read, and I reflexively remove the phone from contact with the card when I feel it - every time - unless I'm purposefully concentrating on not doing so.
Ideally, the app would signal a successful data connection by displaying some kind of prompt/overlay with a loading animation and a helpful message like, "Reading card; please do not move your device," and then it would vibrate on completion.
There may be good reasons why it works how it does, or this may not be a development priority, but I doubt I'm the only user who finds this frustrating on an almost-daily basis and I think a change would be welcome.