API Rules for designers: use one encoding, not two "If you haven't tested your code, it's probably wrong" Today's bad API example is from the Bluetooth Heart Rate system. Most of the protocol is fine: you get a notification every so often with updated heart rate information (e.g., heart rate in beats per minutes (BPM) plus optional stuff for overall energy and the "RR Interval" for fine-grained…