IoT is hard! You have a huge mix of disciplines coming together!
It's also hard because of awesome devices like iPhone and Android phones. They create expectations about cost and capability.
These things are supercomputers... and are also produced in the tens of millions of devices per model.
At that scale, price per unit is extremely low, and the upfront development cost, the 'Non-Recurring Engineering' (NRE) cost, can end up being amortised across a huge number of devices making it insignificant to the end user cost.
When we at Element develop IoT devices, we want to get the quickest wins we possibly can! We want to decrease time & cost and ship a working product fast.
Key words above... working product!!! The user expects big things from any IoT device, due to the expectations set by the supercomputers in our pockets. A good old engineering conundrum!
Our native app team leader Ravinder here is emulating some of the worst-case scenarios for the newly developed ShockWiz Android app we built for SRAM.
The app has been rebuilt in the newest Android toolchain using Kotlin, Jetpack Compose, Coroutines... the works.
We utilised our Cranio Element Sync Bluetooth library as part of the app to do the asynchronous Bluetooth interactions with IoT devices, here specifically ShockWiz.
Emulating the worst-case user experience is an absolute must these days!
A good amount of effort is spent in abusing the products we develop, so the end user gets what they expect.