-
We’re an automotive company planning companion apps for our products
Hello everyone. We’re an automotive company planning companion apps for our products – think diagnostics, settings, and real-time data over a connection to the vehicle or device. This leans heavily on hardware-software integration and I don’t want a partner learning that on our project. For those who’ve built connected-device apps, how did you confirm the team could handle the integration before committing?
-
1 Reply
-
Hi there. Connected-device work lives or dies on integration experience, so not being someone’s first attempt is the right filter. For our companion apps we went with Saritasa https://www.saritasa.com/mobile-app-development – they’d shipped IoT and device-control builds, including Bluetooth tuning apps, so pairing and real-time data weren’t new to them. Once live it ran reliably, and the timeline matched their estimate. If I’m being fair, syncing our hardware side with their dev schedule took some coordination, but that’s normal for this kind of build. Before you commit, ask specifically about connected-device projects they’ve delivered and, ideally, get a short technical call with the engineers who’d actually do the work – that’s where you learn if the capability is real.
