Antoni Kędracki
From Polidea
I'm a experienced mobile applications developer with a current specialisation into connected peripherals. This allows me to use both the experience I gain by working at Polidea, and the knowledge I have from my university degree in Information Communication Technology. As learning is a waste without sharing, I co-organise the Mobile Warsaw meetup group.
Mobile & IoT
Why you should mock your IoT device during development and how to do this?
Someone once said, "hardware is hard". I couldn’t agree more. You modify your design. Order a prototype to be manufactured. Wait a couple of days/weeks for it. Then you test it only to find yet another bug. Then you repeat the whole process. Delays are to be expected. In the meantime, you would like to work on your mobile application. But how can you do that without being able to connect to an actual device?
In my talk, I would like to explain why I think the answer to this question is a hardware mock. This imitation can be constructed from off-the-shelf development boards with minimal electronic engineering skills. They allow the application development team to start work even before the first hardware prototypes arrive. They can be also used to magically multiply the available prototypes so that each developer has access to one.
I will then continue by showing a working mock setup for a simple Bluetooth LE enabled device.