- Configuring an ESP8266 for Battery PowerPosted 1 day ago
- Creating a Telegram Bot for ESP32Posted 2 days ago
- Mini Course on BlynkPosted 3 days ago
- Creating a Unique Electronic Musical Instrument: The Sound WallPosted 5 days ago
- Building a Laser MicroscopePosted 5 days ago
- Grand Piano Keys with ArduinoPosted 1 week ago
- Wireless Power TransferPosted 1 week ago
- Robot Punchers with ArduinoPosted 1 week ago
- A minimal 3D-printed scalePosted 2 weeks ago
- Expanding the pins of a microcontrollerPosted 2 weeks 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.