2 ms·
> If I managed to write software that competed with Garmin on their own watches, so be it. That's fair competition I worked on a line of products that allowed
by Aurornis 2y ago
> If I managed to write software that competed with Garmin on their own watches, so be it. That's fair competition
I worked on a line of products that allowed user modifications of the software. We didn’t explicitly endorse it, but we also had instructions on the website for how to get into the hardware and we designed it so users could modify things and persist their changes.
It was fun to see what people did with the hardware, but the volume of support requests was also out of control after a while.
Companies wouldn’t actually care if you created alternate software for something like a watch if there was no downside to them. It would sell more hardware to people who wanted to customize.
The problem comes later, when many people casually modify their devices and then expect original customer service to get it back to the original state. You can try to place rules on customer support, but customers will lie through their teeth to customer support if they think it will get them what they want. We would get people demanding RMA replacements because their device “mysteriously” stopped working, then when engineering did random sampling of RMAs we would find that they had modified the software and didn’t know they could hard reset it.
It’s a real problem. HN imagines the average person who modifies hardware to be highly knowledgeable and self sufficient. In the real world it’s usually someone following an outdated guide online where they copy and paste different commands until something works. Those same people are the first to try to return the product or request customer support when it doesn’t work perfectly.
Prusa (IIRC) had an interesting solution where you had to break off a physical piece to void your warranty in order to try different firmware. People were up in arms about it, but I think it was the smartest way to handle this conundrum.
- brk 2y agoThis is very accurate. Most of the time the motivation behind restrictions and not releasing code is rooted in support costs. People can and will break things inadvertently, but they won't like that and will then go the route of requesting support, RMAs, etc. Additionally in some cases those people that developed random customizations will release them, and now other users will install or use them, and if an issue crops up, the support costs are now exponentially worse.
- AnthonyMouse 2y ago> the support costs are now exponentially worse. Is there any evidence that this actually happens? The percentage of customers who install custom firmware would be low to begin with, much less the percentage of those who then have problems with it and try to get the company to support it instead of the community that developed it. The idea that this type of support request is going to dominate support costs seems pretty farfetched.
- Zak 2y ago> Prusa (IIRC) had an interesting solution where you had to break off a physical piece to void your warranty in order to try different firmware. I'm not sure this would hold up to a legal challenge in the USA. "Warranty void if removed" stickers are illegal, for example: https://www.ftc.gov/news-events/news/press-releases/2024/07/ftc-warns-companies-stop-warranty-practices-harm-consumers-right-repair https://www.ftc.gov/news-events/news/press-releases/2024/07/...
- AnthonyMouse 2y ago> The problem comes later, when many people casually modify their devices and then expect original customer service to get it back to the original state. So design the hardware to make that (i.e. factory reset) easy and have the customer try it before any RMA. > Prusa (IIRC) had an interesting solution where you had to break off a physical piece to void your warranty in order to try different firmware. People were up in arms about it, but I think it was the smartest way to handle this conundrum. Sort of. What the customer is reasonably going to want is to have a separate warranty for the hardware and the software and void the software warranty. If someone replaces their firmware to fix a software bug and then their screen independently develops bad pixels, the customer is rightfully going to be upset that the company is using it as an excuse to deny a warranty replacement of their faulty hardware. This is also how you get customers lying to you about replacing the firmware. If you try to deny unrelated warranty claims over that they feel like they're being ripped off. But if the alternatives are "warranty void if firmware replaced" and "closed firmware" the first one is clearly better.