Skip to content

Theme Studio

Brian Jr edited this page Nov 17, 2026 · 1 revision

Theme Studio

The companion's Themes section has a Theme Studio: a full-screen editor where users build their own overlay looks on the device, with a live preview of the real overlay. It needs no code, so point people (and agents) there before adding a new built-in Look. Built-in Looks are for designs that should ship with the app; personal and shared looks belong in Theme Studio and theme repos.

What users can do

  • Mix and match: start from any built-in Look and swap any part (cards, tiles, gauges, sliders, nav, backdrop, headers) from the others.
  • Build from scratch: every part has a parametric Custom style (fill, opacity, border, shadow, glow; gauge shape and colors; nav indicator), plus shapes, pinned colors, label text, effects, gauge fit and their own TTF/OTF fonts.
  • Share: export looks as .tcplooks.json packs to /sdcard/TCP Themes/themes/ (fonts go to /sdcard/TCP Themes/fonts/), or follow a GitHub theme repo made from the tcp-themes template and get its updates.

The user-facing tour is in the README.

How it's stored

A user-made look is a CustomLook (ui/theme/CustomLook.kt): overrides on top of a base Look, where anything left unset comes from the base. It's selected with overlay_look = "custom:<id>" and turned into a normal TccLookSpec by toSpec(), so the overlay and companion render it like any built-in Look.

Keep in mind when you change the Look system

  • Keep CUSTOM wired. Every style enum has a CUSTOM value backed by ui/components/looks/CustomRenderers.kt, with its settings in CustomRenderParams. New renderer interface methods need a Custom implementation too.
  • Expose new options to users. A new trait or spec field that users should control needs a matching CustomLook field, a line in toSpec(), JSON in CustomLookJson, and a Theme Studio control.
  • Keep the pack format in sync. Looks are shared as .tcplooks.json packs (ui/theme/LookPack.kt) through /sdcard/TCP Themes/{themes,fonts} (system/ThemeFolder.kt) and GitHub theme repos (system/ThemeSources.kt). The repo template lives in theme-template/, and its README documents the pack format. When you add a field that packs should carry, update that README too. The ThemePackTest example-pack test keeps the template's sample pack valid.
  • Don't branch on spec.look == ... for visuals. A custom look keeps its base Look's id, so checks like that leak the base look's behavior into every custom look built on it. (This already broke custom card shapes on the Auto base once.)

Back: Home

Clone this wiki locally