The Plugchoice SDK is in beta. Until version 1.0, a minor version may change the SDK or the SDK API. Pin the SDK version in your app and the
Plugchoice-Version header on your server.What your users can do
Add a charger
Connect a new charger to Plugchoice and to your app.
Change its Wi-Fi
Move a charger to another Wi-Fi network, for example after a new router.
Set it up
Tell Plugchoice how the charger is wired, such as its maximum current.
Reconnect it
Bring a charger back online when it lost its connection to Plugchoice.
What you build
Three small pieces, and Link does the rest:1
An endpoint on your server
It asks Plugchoice for a client secret: a short-lived pass that says who your user is and which chargers they may touch.
2
A button in your app
It opens Link. The SDK gets the client secret from your endpoint when it needs one.
3
A check when Link closes
Your app hears how it went, and your server confirms it with Plugchoice.
Why Link
- Many brands, one button. Volt Time, Zaptec, Alfen, Peblar, and any other OCPP charger. Plugchoice keeps Link up to date, so new brands and fixes reach your users without an update of your app.
- What only a phone can do. Link joins a charger’s own Wi-Fi, finds it on the home network and talks to it over Bluetooth, behind the phone’s usual permission prompts.
- Your look. Your name, logo and colour, in light and dark, in seven languages.
Platforms
The SDK is open source: github.com/plugchoice/mobile-sdk.
Get access
Email support@plugchoice.com for test credentials. Test mode works with real chargers; see Test and live.Next
How Link works
The few ideas behind the SDK, in plain words.
Get started
Add a charger from your app, end to end.
Installation
Add the SDK to your iOS, Android or React Native app.
Supported chargers
What Link can do for each brand.