Kits have the following two characteristics:
a) If they are auto-detected, the user cannot modify them.
b) They "grab" compatible devices if none is set yet.
In combination, a) and b) lead to an unwanted side effect.
Real-life example: An SDK pre-configures one or more Kits with the device left empty, so the user can set the right one (the device id is not known a priori, e.g. because the devices will be auto-detected). Now the first device that is added and matches a Kit is set as the Kit's device automatically, without any way for the user to change this. This means users are forced to clone the now useless pre-configured Kits, which beats their purpose somewhat.

Possible solutions:

• Only make those Kit properties unmodifiable that were actually pre-configured.
• Do not auto-assign devices to auto-detected Kits.