Frequently Asked Questions
Why would a developer want to use this platform?
Communication protocols differ between car manufacturers; a third-party interested in working with multiple car manufacturers would have to create an integration with each car manufacturer separately. App development would quickly become complicated or impossible; and manufacturers do not have the time or resources to cooperate with individual developers.
HIGH MOBILITY offers applications access to real vehicle data from an ever-growing list of carmakers with a single integration and a unified Auto API.
To ease development, we created vehicle emulators and a way to simulate a car driving so applications can be tested without having a physical connected car present.
Anyone can sign up to HIGH MOBILITY at no cost and start using the emulators and simulator to experiment with the APIs and begin developing applications.
When you create an application and an emulated vehicle, you get API keys which can be used to read data about the emulated vehicle, like fuel level, tire pressure, or location.
We have SDKs and sample applications for iOS, Android, and Node.js to help you get started.
What's the emulator?
To aid developers who need to work with connected cars while testing and fine-tuning their applications, we created a vehicle emulator. The emulator allows developers to see—in the browser and in real time—precisely how a car would react to commands from their applications. At the same time, the sidebar shows—and can control—every aspect of the car’s environment and its state. The Auto API can be used to read these parameters and change them where applicable. Any communication with or change in state of the car is shown in the console log in the bottom frame of the emulator workspace.
The emulator must be running in order for the emulated car to receive and respond to commands. When it is running, the vehicle’s states—and those of its environment—can be observed and changed in two different ways: through the control panel in the sidebar, and through the API.
The vehicle states persist when the emulator is not running and are saved on HIGH MOBILITY’s servers. When an emulator is restarted, the vehicle and its environment will look exactly as it did when the emulator was closed. The states change only if the sidebar is used to change them, if the Auto APIs are used to write to the vehicle, or if they are changed during a pre-programmed simulation.