Form depth

Forms should disclose complexity gradually. Start with clear field labels and helper text, group fields by task, and reserve advanced settings for users who need direct control.

Field depth

Project name

Used for the output directory.

Tensor arena

Enter a value between 64 and 512 KB.

Manifest label

System-managed value.

Deployment profile

Group related fields and reveal specialist settings only when needed.

Model

Deployment engine

Target board

Output directory

Relative to the project root.

Advanced memory settings

What gets written

ResetSave profile

Schema-driven configuration

Configuration-heavy tools can use a shared schema to drive their form controls, validation, and serialized output. This keeps a CLI, a web UI, and a CI job on the same configuration contract without forcing every page to hand-author its own field layout. The same schema can serialize to JSON or YAML; the example below uses JSON here so the generated payload stays easy to inspect.

Schema-driven configuration

Render a consistent form from one typed object schema, then pass the resulting JSON to a CLI, API, or CI job.

JSON schema

Model artifact *

LiteRT/TFLite file to compile or profile.

Deployment engine *

Runtime selected for this configuration.

Target board *

Hardware target used by the build or profiling run.

Arena budget (KB)

Optional memory constraint for an early design check.

Include per-layer measurements

Retain detailed operator measurements in the result bundle.

Generated configuration

3 required fields

{
  "model": "speech_enhancement.tflite",
  "engine": "heliaAOT",
  "target": "Apollo510 EVB",
  "arena_kb": 192,
  "include_per_layer": true
}

Depth principles

• Keep labels persistent; use placeholders only as examples.
• Place validation beside the field that needs attention.
• Separate task sections with spacing or quiet rules instead of nested cards.
• Reveal advanced settings without clearing existing form state.