Originally Posted by
Weston@HPTuners
There is no plan at this time. It's unfortunately not a simple matter of us choosing which devices we allow the app to connect with, but rather us having to develop custom support for each specific device. As you might imagine, it quickly becomes impractical to try to support everything that's on the market when nearly everything requires one-off development work, and typically we'd need to obtain and test each device as well.
Classic Bluetooth on Android has enabled us to simply support certain widely used standards, and then everything that properly conforms to it works easily, but that was never possible on iOS due to Apple's Bluetooth restrictions. Bluetooth 4/5 (aka BLE) is not restricted, but it also has some drawbacks, the biggest of which is that it does not have simple serial communications... there is a way to do it, but we need to know the specific UUID's and/or device names for everything ahead of time, and not all of them function in quite the same way either.
So, if the necessary technical info on the Kiwi 4 is published, and it only requires a minor change to our existing Kiwi 3 or other BLE device support, then I'd be happy to add it. I think it's mutually beneficial for all involved. But so far I've not seen PLX openly publish any developer technical info on the Kiwi 4, and I can't justify signing any NDAs for the sake of supporting someone else's product. The Kiwi 3 was much the same situation, except that it was the first viable BLE option for iOS users, so it was worth the time investment to figure it out on my own... Turns out the BT chip manufacturer openly published the info I needed there.
When hardware manufacturers openly publish the technical information that's needed to support their products, they're far more likely to get support from us, just like with most any app developer. But even still, it takes our time and resources, so we do have to prioritize.