3 ms·
I've had a startup business in the back of my brain for a few years that's driven by this syndrome: 1. It vendors would contract with IoTZombieCo to have their
by dboreham 7y ago
I've had a startup business in the back of my brain for a few years that's driven by this syndrome:
1. It vendors would contract with IoTZombieCo to have their product covered. Like a form of insurance mixed with code escrow. They pay a premium for this and can put a brand label on the product that tells consumers it can't be EOL'ed. Vendor sells more product or can charge a premium price due to customer assurance of continued service.
2. My IoTZombieCo staff are given access to their code and ops resources (in the ideal scenario the vendor outsources running the backend services to us too).
3. When the vendor goes broke or decides to EOL, IoTZombieCo takes over the customer relationship, charges the customer a reasonable fee to continue providing service. Fee to be limited by some covenant that allows reasonable but not excessive profits.
- 14 7y agoBut unless IotZombieCo can ensure it too doesn’t go out of business isn’t it just the same risk to the customer however with 2 companies instead of one? I think that 2 companies with the ability to keep a device running is better but the real solution is fully open sourcing the code of these devices since the company is no longer going using them or supporting them. Instead the company is offering a disingenuous offer where you can get some Ring equipment for a discount but really that discount is a minuscule fraction of what one would pay just going to the store and if I were to guess they probably made some back room deal with Ring as well that they could convert ‘x’ amount of customers to their service and got some sort of back pay. This was just a shit deal but it is good it happens from time to time because we need people to start to become aware of this and demand open source.
- dboreham 7y agoTurtles all the way down. But the difference is that IoTZombieCo has an obviously viable business model as long as consumers want their devices to work and are willing to pay the cost. Many of the original vendors don't have viable business models which is why they go out of business. There are many devices used in business scenarios for example where the consumer is likely to take a keener interest in long term viability and also has a higher tolerance for paying for that.
- 14 7y ago"as long as consumers want their devices to work and are willing to pay the cost" This is what is upsetting the current customers. All they have to do is buy a Ring device and they essentially get their service to continue. Or you propose they continue to pay IotZombieCo and they get to have their software run on their device. So either they pay for the device or software in order to keep a service that worked perfectly fine before, and really does not need some other person's servers controlling it when a person could set that up on their own network (not against cloud services as they can provide added value but the ability to run on your own network should be an option too).
- Dylan16807 7y ago> All they have to do is buy a Ring device That's expensive. Much more expensive than basic firmware updates and a couple servers from a system that by design is going to put a priority on keeping the cost of firmware updates low.
- michaelt 7y agoSeems to me there are two related problems: 1. IoT device stops working when the vendor drops support. 2. IoT device stops getting security updates and ends up on an DDOS botnet when the vendor drops support. If you want to solve 2, whoever takes over support needs control of the auto-update mechanism, something to deter them from abusing that control, and no unpopular devices or cheapskate customers to fall through the cracks.
- SkyBelow 7y agoWithout enough instances of people losing support at EOL, consumers won't put a premium on such a brand label and thus I do not see companies willing to pay the premium and contribute the labor needed to complete step 1. By the time that consumers are accustom to the point where they are worried about EOL support, they would likely be looking for systems that are more open, and that is assuming we ever get to the point where consumers care that much (they have notoriously short memories sometimes). Such a business might have a chance at the point when the cross over from not caring to caring occur.
- vbezhenar 7y agoThe only guarantee is open sourcing server code and providing means for end devices to change server address.
- dboreham 7y agoWell, I'm involved with a project that takes that approach, so...agreed :) But realistically vendors mostly won't do this and customers mostly won't be able to run their own back end. And there are often dependent services needed (weather data for example).
- lutorm 7y agoWell, even if everyone doesn't want to run their own back end, if it's at least possible to do so the chance of someone offering to run that service for a small fee is infinitely greater than if not.
- lutorm 7y agoI just bought an OpenEVSE electric car charger and this is what it does. They run a service for it, but if you prefer you can change the url and run the service yourself.
- redbeard0x0a 7y agoI think the most important hire for this startup would be a brilliant marketer. It would be an uphill battle because a vendor isn't going to want your service if their customers don't even know to ask about it. It would be 99% educating people about this service so they can look for your logo on the box when they buy their next smart doorbell.
- dboreham 7y agoRight. Not having an anchor customer is what's prevented me developing the concept. I think it would be best done by starting as a service outsourcing provider then adding the insurance component.
- the8472 7y agoYou don't need yet another company to solve the problem of failing companies. You need lan-local protocols so that users can control devices within their network directly without going through the cloud.
- michaelt 7y agoThat would solve "It stopped working when the vendor went out of business" but it wouldn't solve "It stopped getting security updates when the vendor went out of business"
- the8472 7y agoCode escrow doesn't guarantee maintenance either, that would be yet another committment for the company and might increase their operating costs over time as the accumulate more and more zombie products to maintain, potentially leading to failure too.
- michaelt 7y agoIsn't maintenance what IoTZombieCo would be contractually obligated to do, though? Here in the UK new homes often have a 10 year warranty from a third-party insurer, who gets to dictate construction methods to the builder. So the idea of products coming with third-party warranties isn't unprecedented.
- inamesh 7y agoCan't control via Alexa or Google home without going to the cloud.
- mondoshawan 7y agoThis idea isn't new. Companies in the B2B and industrial space typically contract out to other companies like what you describe to provide 10+ year support plans for products. The trick is that for a consumer market, the margins are typically much harder to work with -- especially with startups. In fact, there's a zombieco that took over running Vector's upstream servers when Anki died, so definitely not new.
- dboreham 7y agoYes, I've worked in that space which is where I got the idea from.
- darkerside 7y agoCompletely vulnerable to systemic risk. As soon as a wave of companies go out of business, your revenue disappears and your costs skyrocket.
- mdorazio 7y agoYou're forgetting that consumer products companies want customers to buy new products, not keep using old ones indefinitely. It's in their financial interest to deliberately EOL older products with no recourse for customers so long as the average customer doesn't wise up enough to shy away from the brand entirely. This is really digital planned obsolescence. A better company would be one funded by donations that reverse engineers protocols for these things and provides an open server to keep them alive, similar to what the Pebble community did.
- deleted 7y ago[deleted]
- guptaneil 7y agoI agree with the pain point to be solved but let me phrase this pitch another way: IoTZombieCo: give us x% of your revenue and we’ll acquire you for free when you die. In exchange, you can put our logo on your box as if we’ve already acquired you. Companies don’t shut down for fun. Usually it means the economics didn’t make sense. Having a large portfolio of failed products wouldn’t change the economics for IoTZombieCo. The only long-term solution is products that aren’t cloud addicted. Make everything local-first with some progressive (optional) enhancement with cloud functionality that users pay for to keep it sustainable. Disclaimer: I build local-first IoT products at Hiome (hiome.com)
- dboreham 7y agoRight, the model only works if there remains some rump of deployed devices for which the owner is willing to pay the real cost of continued service.
- TheTruth321 7y agoIoTco T&C: If we go bankrupt, we'll open source the app. Mandatory.