libaktualizr-why-use.adoc

Integrate libaktualizr into your solution

Note	We recommend that you view this article in our documentation portal. Not all of our articles render correctly in GitHub.

The OTA Connect client (aktualizr) is designed to be run as a standalone component on an embedded system and can manage the entire software update process. However, most automotive production use cases will have requirements that go beyond what the standalone client can provide. For example, some in-vehicle interfaces are proprietary and under NDA, so their implementation must be kept separate from aktualizr.

Why use libaktualizr?

You can integrate the OTA update functionality yourself and minimize the involvement of external consultants. For this purpose, you can use libaktualizr to build your own OTA update solution.

Typical scenarios for making your own client could be:

• You want to integrate OTA Connect functionality with a third-party HMI

• You want to integrate OTA Connect with a third-party interface that installs software on Secondary ECUs

• You want to constrain network traffic and software updates to specific vehicle states

• You want to provide motorists or service staff with progress indicators for specific software updates.

To get started, have a look at our demo app in GitHub or read through our guide to getting started with libaktualizr.