App themes
Choose App theme in the Calculator App editor. Each choice shows its palette and density. Use Tab to reach the picker, arrow keys to move between themes, and Home/End to select the first/last choice. The selected radio and its outline identify the choice without relying on color.
The existing Run preview changes immediately. Changing a theme keeps your inputs, selected files, scenarios, case, active pages and last results. It does not run a calculation, call AI or charge credits. Save the draft, or use Save as to keep a new copy. The usual unsaved-changes warning includes the theme. Opening another app restores that app's saved theme; execution-history restoration restores the theme recorded with that run.
Eight stable choices
| Theme ID | Name | Palette | Density | Character |
|---|---|---|---|---|
deccf | DECCF | Light green | Standard (default) | Rounded surfaces, light shadows and a gentle spring response |
nordic-light | Nordic light | Cool blue/gray | Standard | Crisp corners, flat cards and restrained motion |
warm-light | Warm light | Warm neutral | Standard | Soft curves, diffuse shadows and slower, softer motion |
mono-light | Mono light | Grayscale | Standard | Nearly square corners, stronger outlines and solid selection states |
graphite-dark | Graphite dark | Dark graphite | Standard | Layered surfaces, deeper shadows and softly lit active choices |
deccf-compact | DECCF compact | Light green | Compact | Tighter rounding, subtle shadows and quicker feedback |
nordic-compact | Nordic compact | Cool blue/gray | Compact | Small corners and flat surfaces for a precise, compact workspace |
deccf-ultra-compact | DECCF ultra compact | Light green | Ultra compact | Minimal rounding and shadows, with short, restrained transitions |
Labels may be translated; IDs remain stable. The chosen palette takes precedence over the device's light/dark preference. All themes use Myriad Pro, loaded automatically, with a system font fallback if it is unavailable. Navigation uses its light condensed variant; input values keep the regular family.
| Density token | Standard | Compact | Ultra compact |
|---|---|---|---|
| Single-line desktop control minimum | 48 px | 36 px | 28 px |
| Panel padding | 10 px | 10 px | 10 px |
| Field gap | 8 px | 8 px | 8 px |
| Base table cell vertical padding | 4 px | 4 px | 4 px |
| Button vertical padding | 12 px | 7 px | 3 px |
Labels, multiline inputs and zoom may increase a control's height. Touch controls retain at least 44 px interactive targets where needed; editable mobile fields use 16 px text to avoid automatic browser zoom. Tables keep local horizontal scrolling and an edge shadow when more columns remain offscreen. Focus remains visible in every palette. Diagrams include labels, legends and values, rather than conveying meaning by color alone.
Themes change shape, depth and interaction feel as well as color. Fields with units share one focus frame around the complete control. Input and results menus use the same selection styling. Reduced-motion preferences disable transitions and bounce effects in every theme.
What changes
The theme covers the app's inputs, run settings, scenarios, cases, reports, charts and app-owned dialogs/dropdowns. Each app has its own open Shadow Root with the same shared component styles in Run preview, normal run view, a separate app window and an embedded app. Portal navigation, account pages, Marketplace, code editors and the theme picker keep the portal appearance. Two apps can use different themes without affecting each other.
An installed app uses its installed version's theme. A saved case with a version snapshot keeps that snapshot's theme. Changing the owner's current draft does not restyle a previously published version. Publish and install a newer version to adopt that version's theme. Embedded elements read their pinned app version; there is no separate host theme override method.
App metadata and integrations
Theme is optional app metadata, outside the model and its calculation inputs:
{"ui":{"theme":"deccf-compact"}}The contract is content.ui?: { theme: AppThemeId }. The object accepts exactly one supported theme ID. A new write with null, an array, a missing/non-string/unknown theme, extra CSS, scripts or URLs is rejected. Apps without ui use deccf; they need no migration. An unknown externally stored theme displays a warning and falls back to DECCF without rewriting the record. Choose a valid theme before saving such an app.
MCP's deccf_create_model and deccf_update_model accept optional ui: { theme: "deccf-compact" }. Omit ui in a partial update to preserve the saved choice. deccf_get_model returns it when present. The same metadata survives an own-model transfer through deccf_prepare_save, module-backed transfers, and Save as. Theme never changes package selection, calculation inputs or numerical results.
For an authenticated portal integration, use the existing library save contract and current revision. This example reads the app, keeps its complete content and saves just a theme change:
const appId = "your-app-id";
const endpoint = `/api/library/models/${encodeURIComponent(appId)}`;
const current = await (await fetch(endpoint)).json();
const response = await fetch(endpoint, {
method: "PUT",
headers: { "Content-Type": "application/json" },
body: JSON.stringify({
name: current.name,
revision: current.revision,
versionId: current.versionId,
content: { ...current.content, ui: { theme: "deccf-compact" } }
})
});
if (!response.ok) throw new Error((await response.json()).error);The server still checks the signed-in owner and revision. Omitted ui on an existing library update preserves it. Import/export should retain content.ui as app metadata; never put it into request.input or model JavaScript. A saved theme does not authorize CSS imports or executable resources. See Embedded Calculator Apps for the separate, limited host CSS variable and part contract.