Problem is our in house dev team built the original app and they're the first to admit they're out of their depth with the IoT side of things. Bluetooth protocols, sensor data syncing, cloud connectivity, it's a completely different beast from building a regular mobile app. We tried hiring for it but finding engineers who understand both hardware communication and clean mobile UX is brutal.

Recommended Answers

All 2 Replies

I've yet to find everyone is good, great at everything.

But you confuse me with the Bluetooth. I rarely had to deal with the Bluetooth protocol. I DID HAVE TO DEAL WITH the protocol demanded by the DEVICE but not the Bluetooth stack.

More -> Sometimes a client wanted to add support for a DEVICE. I had no problem with that request once they delivered the documentation on the device's protocol.

And the hardware comms was as Darth Vader said "All too easy" once we had Bluetooth. Before that it was RS232, 485 or other and well, that's hardware comms for you.

FIN: Clean mobile UX ? Pfft. Get your product working by any means first. You can polish the UX to what the client wants later.

Problem is our in house dev team built the original app and they're the first to admit they're out of their depth with the IoT side of things

It seems like you have a badly designed app to begin with.

U/X and IoT should be orthogonal. Neither needs to know much (if anything) about the other.

https://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller

The controller causes the UI to display an input box for say a device address, but the UI doesn't have a clue what that's for.
The controller tells the IoT "use this device address", but the IoT doesn't have a clue where that came from.

commented: Thanks for this. The majority of my mobile work was on PalmOS. UX? Well, it had that! +0
Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.