An App is more than a visual.

Choose the right role

Apps can provide Content, Interactive, Control, Information, Processing, Transition, Output or Utility/Data capabilities. One package may expose several role-specific endpoints.

Native output belongs behind ViXL Bridge or a native runtime. Information consoles subscribe to logical Show data.

Package with exact identity

Declare an App ID and explicit App version. Keep schema and API versions separate. Include the required manifests, entrypoints and assets, then validate the package with the matching SDK tooling.

Published packages are immutable. Changes need a new App version. Installation verifies package and manifest hashes; saved Scenes retain their pins.

Respect the Show contract

Layers have stable identity. Presets describe target compositions; Cues recall them. Reconcile with KEEP, UPDATE, REPLACE, CLEAR and IGNORE.

Preload and warm heavy content before reporting READY. Transition Apps receive FROM and TO frames with deterministic progress. Media must be verified, staged and local at playback time.

Work against the right SDK

The current catalog includes legacy .vxl packages and v2 .vixlapp packages. Use the SDK and validator matching the package format; these are not interchangeable wrappers.

Validate manifests and controls, preparation failures, retries, disposal and deterministic playback. Test your exact package against the release runtime before requesting a listing.

Explore Type Studio

Type Studio 0.5.0 provides an editing surface for Type 0.4.0. It provides a dedicated editing workspace alongside the Viewer test drive.

Release review

Prepare package hashes, supported roles, compatibility requirements, real screenshots and test evidence. Submit them through your existing ViXL development conversation.

A self-service developer publishing portal is not operational. There is no automated store submission or payout flow on this release.