On my Mac I've never had any problems over the years since I go my first Bluetooth device. The interface is pretty straight forward. I've connected keyboards, a mouse, and my non-Apple cell phone and headset. No problems on the computer interface side.
The only problem I've had is with my sister's mobile and Bull-ant bluetooth hands-free system - and there the problem wasn't interface; it was connection - no real feedback on what to expect or how long it should normally take. No warning to make sure the phone has a good charge before trying to pair for instance! Strong power supply = strong bluetooth signal! It all comes down to meeting a users expectations and if you don't tell them what can go wrong, then there is no way for a User to be able to act on a problem when it arrises. It brings up another question I've often thought about - should User Instructions have "what may NOT work" rather than how it should work? Are Troubleshooting sections on their own enough or should they be part of the setting-up process? regards Stephen Holmes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=47575 ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... disc...@ixda.org Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
