Screens App

Screens Runtime

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.

screens

Run in Screens

Start, stop, inspect logs, and view manifest panels in the Screens runtime.

Where this appears in RIA Hub

Screens list, app runtime, and Studio.

What you need next

Runtime access and a packaged app manifest.

Open guide

Screens shows packaged apps, app cards, status actions, runtime controls, manifest component grids, logs, start and stop lifecycle, and error states.

Screens surfaces

apps Screens list Review app cards, status, and available actions.control App runtime Start, stop, inspect status banners, and follow logs.view Manifest panels Display component grids and app panels produced by packaging.edit Screens Studio Edit layouts, add components, resolve conflicts, and save drafts.

control

App runtime

Runtime controls mirror manifest status and stream errors back to the user.

Stopped Stopped Starting Queued Running Running Error Error

Logs and Troubleshooting

Screens checks

Open all Collapse all

Runtime does not start

Check app manifest validity, target profile, device settings, and model artifact paths.

Logs show missing props

Open Studio or the packaging page and fill required component properties.

Draft conflict appears

Review autosave and conflict state before overwriting another editor change.

Panel is absent

Confirm the manifest component grid includes the panel and the packaged app uses the expected runtime profile.

Studio

Use Screens Studio when you need to edit layouts, add components, resolve conflicts, save drafts, or navigate missing properties. Studio should refine a valid packaged app, not replace the packaging validation flow.

Next steps

• Collect more data — Run a new Campaign Control session to extend your training set, then retrain and repackage.
• Review the full path — Return to End-to-End Onboarding for a summary of the complete workflow.