Package an Application

Application Composer Workflow

workflow

Capture to Screens

The tested RIA Hub path from upload or synthesis through curation, training, packaging, and a running Screens app.

1. Capture or synthesize Start from a local recording, uploaded RF sample, or synthetic signal problem.
2. Curate and label Select source files, slice useful intervals, and attach labels or qualifiers.
3. Inspect readiness Review balance, metadata, empty states, and recommendations before training.
4. Train model Choose a repository, runner, dataset, template, and mode to launch a workflow run.
5. Package app Connect model artifacts into an application pipeline and validate target runtime settings.
6. Run in Screens Start, stop, inspect logs, and view manifest panels in the Screens runtime.

package

Package app

Connect model artifacts into an application pipeline and validate target runtime settings.

Where this appears in RIA Hub

Engine Builder and Application Composer.

What you need next

A valid manifest with model path, inference block, and sink or device settings.

Open guide

Application Composer turns trained artifacts into an app pipeline. Blocks and edges describe source, transform, inference, and sink behavior; target profile selection controls runtime packaging; commit and build actions persist the result.

Packaging surfaces

target Engine Builder Choose backend and runtime targets for the packaged artifact.pipeline Application Composer Connect source, inference, transform, and sink blocks on the canvas.runtime Screens target Package for the Screens runtime profile when the app should run in the Screens UI.checks Validation Fix missing model paths, invalid block order, and sink or device gaps.

pipeline

Application Composer

Composer validates edges, block compatibility, and required properties.

Manifest Ready valid blocks Build Queued runner required

Packaging Checklist

Validation failures to resolve

Open all Collapse all

Model artifact missing

Select a trained artifact and confirm the model path can be resolved by the packager.

Invalid inference block

Ensure the inference block receives the model path and compatible input data.

Missing sink or device

Select the output sink, device, or Screens runtime settings required by the target profile.

Block order is invalid

Fix edges so the graph follows source, preprocessing, inference, postprocessing, and sink order.

Next steps

• Run in Screens — Screens App covers launching, monitoring, and troubleshooting the packaged application at runtime.