IoT Device Development Gone Wrong and How to Fix It

Here you can re-watch the webinar.

Connected device development catastrophes can happen – we’ve seen our fair share of them! Why do they happen, and how can your products avoid doing the same? What are some buzzwords that you’ve been hearing, but don’t know truly how to apply the technology?

Ioterra invited professionals to discuss the best practices of developing the hardware and software aspects of a product. One of the panelists was our CEO, Alexey Shabalovskiy. He was asked about EMBIQ experience with building IoT devices. 

- Danny DeLaveaga: So, Alexey, when companies are creating or using connected products, what kind of things should they be thinking about in the beginning in terms of certifications or should they be thinking about that? How should they go about selecting a development, for a product development initiative?

- Alexey Shabalovskiy: Sure, in first place, I would say it’s very much important to find a partner or somebody who is experienced in the field to which you’re going to build application for, like when you’re trying to set up some set of sensors in some specific environment. It’s worth to find a company which is already experienced with that kind of sensor or that field of knowledge. Speaking about certificates, well, certificates are important while you already have chosen your technology which you are going to use in your solution, but mainly at the first, the initial stage of your product, at concept stage or feasibility study. It is very much important to not choose a particular technology or particular use case for that technology, but rather to look at your business need, your functional needs and then to fit technology to functional needs.

- Alexey Shabalovskiy: So, at that moment you probably wouldn’t need any certificates yet. At the implementation stage, of course, and that depends on technology which you have chosen. For example, if you chose that your BLE device or IoT device has to be connected with Apple device, Apple headset, and Android headset, you would probably look for a company which has MFi certification and can support you with some extension of API or SDK. But before you decide how you’re going to use your product, well rather look for experience than certificates.

- Danny DeLaveaga: Okay, great, so look for a company that has built something similar to what you’re trying to build.

- Alexey Shabalovskiy:Right, right, but if you find, if you’ll find a company which built exactly similar thing which you’re going to build, think twice if you want to build it.

- Danny DeLaveaga: Oh yeah, yeah. Alright, well, so, we’ve got some questions from the audience that I’d like to shoot at you and I think I’ll do this one to you Ron and then go to Hugo, but we would love to hear a couple of stories where things went wrong in a project and how they were fixed. So does anyone have any stories that they can tell around things that go wrong? I know Hugo you brushed into some mobile application and some Bluetooth issues, but yeah, let’s go ahead and start with you Ron.

Read the transcription from the webinar on Ioterra’s site.