4 ms·

Just stop it A rant about entitlement in tech (not what you think)

16 points by robomartin 4y ago

I have grown really sick of two things, which often go together: - Devices that require (and only offer) control via an app on a phone - Devices that require you to create an account on a website and log-in to be able to control them - A combination of the above, sometimes even combined with a desktop app I won't go into all the reasons for detesting this other than to point out that there must be a degree of entitlement in device manufacturers. When I buy your faucet, water pressure monitor or 3D printer, I have no interest whatsoever in having my data go through your network in any way. You are not entitled to it just because you sold me a faucet. Or whatever. This rant was inspired by this new 3D printer I received today. The Bambu Lab X1 Carbon. All indications are that I cannot run this thing without creating an account with the manufacturer and logging in to both the printer and the desktop application (and maybe even the phone app). I have over 20 printers, a good deal of them custom built. Not one of them requires anything even remotely close to this. They can all be accessed and managed over the network without having to have an account on anyone's server and having data go outside our network. Our clients don't want anything to do with the potential for their data leaving our network. In some cases we are legally required to make sure it does not (ITAR). At home, we have a whole-house water monitor that checks pressure, flow and does a few more things. It's a valve with some sensors. And the manufacturer (Moen) wants to reach into my home and have access to my entire network as well as the data captured by this device. Why are manufacturers entitled like this? My guess is that consumers have no awareness at all when it comes to security and privacy and don't push back. If you can intrude into someone's life, grab their data and sell it, with their consent --because all of these gizmos have EULA's nobody reads, well, why not? Right? And then there's the question of obsolescence. My HP-41 calculator runs just fine, decades later. It does not depend on a server being up and running somewhere, or another consumer device being available at all. Imagine not being able to use your 3D printer or faucet in 10 or 20 years because the iPhone app is broken or the server it needs to talk to is gone. How is that good for consumers, at all? I hate over-regulation on the part of government. This, however, might just be a good case for it. A faucet or a water valve should not require a connection to a server and a spying account to function. Neither does a toilet, a 3D printer or a camera. I did say it was a rant...

pedalpete 4y ago
Initially I thought you were talking about devices such as wearable electronics, etc. Do you feel the same way about those devices? If a device expects you to require/want cloud access to the data captured/used with the device, do you feel the same way, that it should be optional? I get that there is probably no benefit to having a faucet connected to an account, but a water pressure monitor that you can view remotely probably requires an account. That makes sense to me. Controlling some small IOT devices via an app is probably preferable to having controls on the device. Again, using your water pressure monitor example - and I have no idea what that is, or what it is used for - but if the device is small, and not readily accessible (is it attached to your water tank), I can see having controls via an app on your phone be better than the manufacturer adding buttons and a screen to the device. I have a horse in this race, as we are building a headband that monitors your sleep state, and uses auditory stimulation to improve the effectiveness of deep sleep (https://soundmind.co https://soundmind.co). We're intentionally designing many interactive elements to only be controlled by an app, rather than on the device. The reason being, as we add buttons to the device, there is a greater likelihood that the buttons will be pressed during sleep, and they also add ergonomics challenges that can be better managed in an app. What are your feelings on that?
- robomartin 4y ago
  I will not buy anything that requires a connection to the mothership unless I have no choice and I really need it. I suppose the phone itself is an exception. As to the valve requiring the manufacturer's server existing in the middle of the transaction, well, I don't think that's necessary at all. One can certainly connect to devices inside the network through other means. Of course, in some cases one has to be technically capable in order to accomplish this, I'll grant you that much. The average consumer isn't equipped to manage this sort of thing. And that's how, in the name of convenience, they give up privacy and personal data. Not sure there's a canonical solution for this. My thermostat should not need a connection to the mothership to work. It should be able to live entirely within my home network and no data should ever escape it. Same is true of my solar array. This is one of the reasons for which I designed, bought and installed my own system. Everyone wanted a connection to the mothership. That's just nuts. From the standpoint of consumer protection --in terms of privacy, security and product longevity-- I think all products should function under a "privacy-first" policy. What if the manufacturer goes out of business? The consumer's investment evaporates? Same thing in the case of a company being acquired. The acquiring company could very easily discontinue the service. Five, ten, fifteen years from now? Absolutely. Having devices tied to servers just to be able to function is not, in my opinion, a service to consumers. It's a service to the company making the device. Everyone is selling data now. I might also go this far with regards to wearable electronics or IoT. They almost have to have a consumer advisory warning, like cigarettes: "This device may become inoperable any time in the future as it depends on a connection to an external service for its operation". I guess I can say that, under certain circumstances, if the consumer if fully informed, no problem. I'll give you a personal example. Many years ago (iPhone 3 era) we authored about a dozen educational apps for kids. This was around the time that apps were on a slippery slope towards zero dollars. We maintained these apps out of just loving what they were doing for kids around the world. However, at some point, Apple demanded that they be updated to the latest and greatest. It made no financial sense at all do stay on that crazy rollercoaster. So, we made the only decision that made sense: We stopped updates. Within a year they were all gone from the App Store. Imagine that, but with hardware devices from a range of companies who, after many years, either have to move on to their support their latest products or simply go out of business due to realities of life. This is not good for consumers. Again, I will admit that in some cases this is a really tough call. However, there's difference between a product made by Apple and one put out by a startup with barely a year under their belt and a runway that might evaporate six months later if sales don't go well. I would say: Fight hard to make a product that can exist on its own. Make that a selling point rather than a deficiency. You can have enhancements that require getting outside the network, but think of the consumer. Put a different way: If a product cost $1000 and it turned into a brick if the company evaporated. How is that good for consumers?

16 points by robomartin 4y ago

pedalpete 4y ago

Initially I thought you were talking about devices such as wearable electronics, etc. Do you feel the same way about those devices? If a device expects you to require/want cloud access to the data captured/used with the device, do you feel the same way, that it should be optional? I get that there is probably no benefit to having a faucet connected to an account, but a water pressure monitor that you can view remotely probably requires an account. That makes sense to me. Controlling some small IOT devices via an app is probably preferable to having controls on the device. Again, using your water pressure monitor example - and I have no idea what that is, or what it is used for - but if the device is small, and not readily accessible (is it attached to your water tank), I can see having controls via an app on your phone be better than the manufacturer adding buttons and a screen to the device. I have a horse in this race, as we are building a headband that monitors your sleep state, and uses auditory stimulation to improve the effectiveness of deep sleep (https://soundmind.co https://soundmind.co). We're intentionally designing many interactive elements to only be controlled by an app, rather than on the device. The reason being, as we add buttons to the device, there is a greater likelihood that the buttons will be pressed during sleep, and they also add ergonomics challenges that can be better managed in an app. What are your feelings on that?

robomartin 4y ago
I will not buy anything that requires a connection to the mothership unless I have no choice and I really need it. I suppose the phone itself is an exception. As to the valve requiring the manufacturer's server existing in the middle of the transaction, well, I don't think that's necessary at all. One can certainly connect to devices inside the network through other means. Of course, in some cases one has to be technically capable in order to accomplish this, I'll grant you that much. The average consumer isn't equipped to manage this sort of thing. And that's how, in the name of convenience, they give up privacy and personal data. Not sure there's a canonical solution for this. My thermostat should not need a connection to the mothership to work. It should be able to live entirely within my home network and no data should ever escape it. Same is true of my solar array. This is one of the reasons for which I designed, bought and installed my own system. Everyone wanted a connection to the mothership. That's just nuts. From the standpoint of consumer protection --in terms of privacy, security and product longevity-- I think all products should function under a "privacy-first" policy. What if the manufacturer goes out of business? The consumer's investment evaporates? Same thing in the case of a company being acquired. The acquiring company could very easily discontinue the service. Five, ten, fifteen years from now? Absolutely. Having devices tied to servers just to be able to function is not, in my opinion, a service to consumers. It's a service to the company making the device. Everyone is selling data now. I might also go this far with regards to wearable electronics or IoT. They almost have to have a consumer advisory warning, like cigarettes: "This device may become inoperable any time in the future as it depends on a connection to an external service for its operation". I guess I can say that, under certain circumstances, if the consumer if fully informed, no problem. I'll give you a personal example. Many years ago (iPhone 3 era) we authored about a dozen educational apps for kids. This was around the time that apps were on a slippery slope towards zero dollars. We maintained these apps out of just loving what they were doing for kids around the world. However, at some point, Apple demanded that they be updated to the latest and greatest. It made no financial sense at all do stay on that crazy rollercoaster. So, we made the only decision that made sense: We stopped updates. Within a year they were all gone from the App Store. Imagine that, but with hardware devices from a range of companies who, after many years, either have to move on to their support their latest products or simply go out of business due to realities of life. This is not good for consumers. Again, I will admit that in some cases this is a really tough call. However, there's difference between a product made by Apple and one put out by a startup with barely a year under their belt and a runway that might evaporate six months later if sales don't go well. I would say: Fight hard to make a product that can exist on its own. Make that a selling point rather than a deficiency. You can have enhancements that require getting outside the network, but think of the consumer. Put a different way: If a product cost $1000 and it turned into a brick if the company evaporated. How is that good for consumers?