- Terminus FE1.1 USB hub board: the solution to connect four USB devicesPosted 1 week ago
- Understanding the Mechanics of 3D PrintingPosted 2 months ago
- SDS011 the Air Quality SensorPosted 3 months ago
- NIXIE STYLE LED DISPLAYPosted 6 months ago
- TOTEM: learning by experimentingPosted 6 months ago
- Google Assistant Voice Controlled Switch – NodeMCU IOT ProjePosted 7 months ago
- Water Softener Salt Level MonitorPosted 7 months ago
- Sparkly Air SensorPosted 7 months ago
- Ultra sonic distance finder with live statusPosted 7 months ago
- Windows interface to have total control over lampsPosted 7 months ago
How to deal with API clients, the lazy way — from code generation to release management
The Arduino IoT Cloud platform aims to make it very simple for anyone to develop and manage IoT applications and its REST API plays a key role in this search for simplicity. The IoT Cloud API at its core consists of a set of endpoints exposed by a backend service, but this alone is not enough to provide a full-fledge product to your users. What you need on top of your API service are:
- Good documentation explaining how to use the service.
- A number of plug-and-play API clients that can be used to abstract the API from different programming languages.
Both those features are difficult to maintain because they get outdated pretty easily as your API evolves but clients are particularly challenging: they’re written in different programming languages and for each of those you should provide idiomatic code that works and is distributed according to best practices defined by each language’s ecosystem.