Build your product

Use SenHub Web or SenCLI to turn product intent into one canonical, buildable device definition. Start with the hardware facts declared by an official Board, add the Components your product needs, bind compatible Drivers, and compile the Application that runs on SenCore.

Recommended path

1. Understand the shared platform model and the identities a project owns.
2. Select a supported board instead of inferring capabilities from a board name.
3. Configure Components and modules with compatible drivers and connections.
4. Add UI and Logic in Application Studio when the product needs an on-device experience.
5. Trigger a firmware build through SenHub Web or the corresponding SenCLI project build workflow only after the project configuration validates.
6. Continue to Deliver to devices with the produced artifact and a planned operation.

What remains stable

Board, Catalog, SenCore release, Application, and build artifact are separate identities. A successful build records the exact facts it consumed; changing a Catalog selection or Application creates a new result rather than silently changing an existing artifact.

The Components guide explains the public configuration model. Available modules, drivers, boards, and peripherals must be read from the active SenHub or SenCLI project context; Docs does not publish backend definition inventories.