You need lan-local protocols so that users can control devices within their network directly without going through the cloud.
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.
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.
Such a business might have a chance at the point when the cross over from not caring to caring occur.
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.
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)
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.
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.
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.
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.