The journey of API integration

Simon Seres

Every modern product needs to ‘work with’ other services - this fact drains development budgets through countless API and SDK integration hours at almost every company.

The original vision was to utilise billions of IoT gadgets to build a decentralised mega-computer through open source nodes. A good bot instead of a bad bot scenario.

Simon, CEO of nymea : “We incorporated a company and started to learn. The early outcome was: There are billions of lean linux-systems working in IoT products - but those generic systems are restricted to their actual application as a printer or a heating pump. What a waste. None of the hardware producers were interested in Botnets - nevertheless they honoured the idea of machines talking to other machines.

But, after a couple of economic and technical iterations, we ended up writing software gateways and middlewares.

The need of integrated software gateways became more obvious. Customers wanted to attach their IoT product to all of that Microsoft Azures, or Amazons, and the demand exploded: IFTTT, Conrad Connect, Alexa, Google Home, Apple Home Kit, Zapier, Siemens Mindsphere, IBM Bluemix and hundreds of IoT clouds and products. And because nobody likes vendor lock-in , it should be easy to reattach the IoT product anytime . It should be as easy as changing from Netflix to Amazon Prime (this is no ad!).

We learned: A modern product should be able to seamlessly attach to any product or service. For many reasons.

Waiting for the best idea in the world to come true, we made the second best idea a blessing for many product managers: The best API integration stack for Linux devices. And its not a RAM-killer since it is based on Qt.”

Watch Simon reporting some of his key learnings in an entertaining format.

track icon Ercole
duration icon 60 min
language icon English
level icon Beginner