4 ms·

Doesn't it? Compared to the nightmare described in the article?

CobrastanJorji 7y ago
I see this idea being proposed in an early design meeting. Then I see a product manager seriously consider it and then veto it. Why? Because their product's goal is to be the easiest to use camera system, and this makes using it much harder. But let's say the PM and the rest of management was convinced. So they make it require pairing and send it out for field testing. Field tests come back: "it's really annoying that I have to pair all of my phones individually with each camera." Management tells engineering to fix that. But let's say that the engineers once again convince management that this is a good idea. The product is launched. The review from CNET or Wirecutter or something comes back: "it's crazy in this day in age that I need to get a ladder and go around to all of my cameras to introduce them all to my new phones every time I do my yearly iPhone upgrade." CEO now has a crisis and demands this be fixed. Engineer pushes back again and is probably fired this time. Feature is removed. A few years later, this article comes out and it causes much, much less damage to the brand than the bad usability reviews. Everyone learns the wrong lesson.
- Udik 7y ago
  But why individually? Can't all the cameras in the local network share a single pairing code?
  - pbhjpbhj 7y ago
    Or they pair with a "controller" device and any user pairs direct with that? Could be a dongle with a button that plugs in to a router usb port.
    - semi-extrinsic 7y ago
      FWIW, this is what Ikea's system does, and all that lets you do is turn the lights on and off.
    - TeMPOraL 7y ago
      Also: pair the cameras with the hub before installation, so you don't need a ladder later on.
- uhoh-itsmaciek 7y ago
  I don't think the answer is to throw up our hands and say, "oh well, I guess security is fundamentally incompatible with usability in consumer electronics; caveat emptor is the best we can do." I concede there's a tension between security and usability (and that compromising on usability to achieve security makes your product less appealing), but we should demand that companies find better ways to design around that tension, instead of making the bare minimum concessions to security and adopting a "blame the user" mentality.

I see this idea being proposed in an early design meeting. Then I see a product manager seriously consider it and then veto it. Why? Because their product's goal is to be the easiest to use camera system, and this makes using it much harder. But let's say the PM and the rest of management was convinced. So they make it require pairing and send it out for field testing. Field tests come back: "it's really annoying that I have to pair all of my phones individually with each camera." Management tells engineering to fix that. But let's say that the engineers once again convince management that this is a good idea. The product is launched. The review from CNET or Wirecutter or something comes back: "it's crazy in this day in age that I need to get a ladder and go around to all of my cameras to introduce them all to my new phones every time I do my yearly iPhone upgrade." CEO now has a crisis and demands this be fixed. Engineer pushes back again and is probably fired this time. Feature is removed. A few years later, this article comes out and it causes much, much less damage to the brand than the bad usability reviews. Everyone learns the wrong lesson.

Udik 7y ago
But why individually? Can't all the cameras in the local network share a single pairing code?
- pbhjpbhj 7y ago
  Or they pair with a "controller" device and any user pairs direct with that? Could be a dongle with a button that plugs in to a router usb port.
  - semi-extrinsic 7y ago
    FWIW, this is what Ikea's system does, and all that lets you do is turn the lights on and off.
  - TeMPOraL 7y ago
    Also: pair the cameras with the hub before installation, so you don't need a ladder later on.
uhoh-itsmaciek 7y ago
I don't think the answer is to throw up our hands and say, "oh well, I guess security is fundamentally incompatible with usability in consumer electronics; caveat emptor is the best we can do." I concede there's a tension between security and usability (and that compromising on usability to achieve security makes your product less appealing), but we should demand that companies find better ways to design around that tension, instead of making the bare minimum concessions to security and adopting a "blame the user" mentality.