Accelerometer -> Big acceleration -> software(is acceleration >threshold: toggle airbag) is a much easier and reliabel process than:
Accelerometer -> Big acceleration -> software(is there an internet connection? is the subscription verified? is acceleration > threshold: toggle airbag)
I’m not defending the subscription model, but that check is very obviously not done during the crash, but during startup, when a couple of seconds delay is not fatal. And if it fails I assume the entire thing just turns off completely.
So you stop for gas in the middle of fucking nowhere, the vest doesn’t get an internet conenction for veryfying your subscription and you are fucked, even as a paying customer.
It still boils down to a complex and much easier failing system, that could deny you critical safety features. I mean this also adds an entirely new dimension of hackability. Someone could hack into the server for the subcription verification and deliberately mess it up, or depending how poorly it is coded, could even access the vests of customers during their ride and disable them.
The system to trigger the airbag should never ever have a remote connection of any sort.
So you could turn it off by accident, or it runs out of battery, or you stay the night somewhere on a longer road trip and it fails to reactivate in the morning because lack of internet connection. The issue still stands that there is another layer of failure that can also deny the product to paying customers for infrastructure problems that are out of their control.
Accelerometer -> Big acceleration -> software(is acceleration >threshold: toggle airbag) is a much easier and reliabel process than:
Accelerometer -> Big acceleration -> software(is there an internet connection? is the subscription verified? is acceleration > threshold: toggle airbag)
Yes. Which is why the latter is not happening.
I’m not defending the subscription model, but that check is very obviously not done during the crash, but during startup, when a couple of seconds delay is not fatal. And if it fails I assume the entire thing just turns off completely.
So you stop for gas in the middle of fucking nowhere, the vest doesn’t get an internet conenction for veryfying your subscription and you are fucked, even as a paying customer.
It still boils down to a complex and much easier failing system, that could deny you critical safety features. I mean this also adds an entirely new dimension of hackability. Someone could hack into the server for the subcription verification and deliberately mess it up, or depending how poorly it is coded, could even access the vests of customers during their ride and disable them.
The system to trigger the airbag should never ever have a remote connection of any sort.
Once it’s activated, it won’t turn off for any reason, except if you turn it off or it runs out of battery.
So you could turn it off by accident, or it runs out of battery, or you stay the night somewhere on a longer road trip and it fails to reactivate in the morning because lack of internet connection. The issue still stands that there is another layer of failure that can also deny the product to paying customers for infrastructure problems that are out of their control.