Apps SDK

Updated: 10/25/2026

On this page

Build an app 2 pages

From template to releaseThe whole path of a new app: create it from the template with pnpm app:new , write the widget, config, texts, and images, check it with pnpm app:check , test it, and take it through the pull request into the catalog up to the release in Stable.
An app in the new standardConvert an app to templates with size, formats, fit report, surfaces, and the declarative form, using the weather app as an example, plus fit check, store images, old configs, host contract, and the order of the next apps.

What is an app, and how does it get onto a display?From the manifest through release, channels, and installation to the signed bundle on the device: the lifecycle of an app in one picture.
The manifestEvery field of the app manifest with whether it is required, its format, and its effect, from id and version to legal, unlocks, and connects.
Widget, configuration, and previewdefineWidget with configSchema and noResolver, formats (useWidgetFormat), preview variants with size for catalog and thumbnails, and preview states, with the clock example.
Configure widgetsRead the widget catalog: configSchema as JSON Schema, required fields, examples, and a ready-made widget instance for each built-in building block.

Backend: resolvers, fetchers, and jobsThe three decorators @WidgetResolver, @Fetcher, and @JobHandler, their rules, and the capabilities that an app’s backend obtains through tokens.
Data access, permissions, and termsdataAccess (reads, external, retention), permissions for team and operator, unlocks and connects, the legal block: what an app discloses before installation.

Signing and the path into the catalogWhat belongs to a release, sha256 and Ed25519 signature, the policy on the device, channels canary → beta → stable, and who creates releases today.
The example appsAll 26 bundled apps with profile and special feature, and the three references clock (widget only), weather (fetcher), pharmacies-on-duty (resources and job).