# Software for application and low-power processors

To design and manage client applications, it’s necessary to understand the organization of APIs in the code and the relationships, functions, and operations of the source code directory files.

## Application processor directory structure

The QSH-exposed APIs are called QSH client APIs for application
development. The following information shows the QSH client API
tree structure and the location of each software component.

The source code for QSH client APIs is in the `<workspace>/build-qcom-wayland/workspace/sources/sensinghub/sensing-hub`
directory. Here, `<workspace>` specifies your working directory.

├───/sources/sensinghub/sensing-hub
    │
    ├───apis                          - APIs
    │   └───proto                     - Proto API
    │       └───google
    │           └───protobuf
    │
    ├───common                        - Common header file
    │   └───inc
    │
    ├───examples
    │   └───SessionClient             - Sample 1 source file
    │
    └───session                       - Client APIs source and header files
        └───1.0
            ├───inc
            └───src
    Copy to clipboard

Note

To view and customize the source code, see the [Qualcomm Linux Yocto Guide](https://docs.qualcomm.com/bundle/publicresource/topics/80-70030-27).

The sensing-hub source is available in the `<workspace>/build-qcom-wayland/workspace/sources/sensinghub/sensing-hub/` directory.

## Low-power processor directory structure

The QSH software stack consists of the framework, API, sensor driver,
and algorithm components. For more information, see
[Software](https://docs.qualcomm.com/bundle/resource/topics/80-70030-7A/software.html).

Last Published: Jun 15, 2026

[Previous Topic
Qualcomm sensing hub APIs](https://docs.qualcomm.com/bundle/publicresource/80-70030-7/topics/qsh_api_reference.md) [Next Topic
Platform](https://docs.qualcomm.com/bundle/publicresource/80-70030-7/topics/platform.md)