App themes (apiVersion 18)¶
Available from Kino 0.9.81
appThemes, go.useTheme, go.setExperience and activeTheme arrive with "apiVersion": 18, which
contract.json ties to Kino 0.9.81. Every older Kino refuses an
apiVersion 18 manifest with «Este plugin necesita una versión más nueva de Kino», and appThemes is not offered
through enhancements. Below apiVersion 18 the field is ignored.
A plugin may offer whole-app looks: colours, a background, corner radii, type sizes, shadows, motion, player control sizes and its own logo, and from apiVersion 26 painted surfaces, a background picture, a font and TV layouts, for every screen of Kino on the phone and the TV. A theme is data in the manifest: no code runs, no network is used, no capability is needed. The person picks one theme in Ajustes ▸ Apariencia (or with a button on your own screen), may adjust what you allow, and the choice is per profile and syncs between their devices.
This is not the apiVersion 6 theme field, which only colours your section, Ajustes tab and
player accent. Both may live in the same manifest.
A theme-only plugin¶
{
"id": "theme-neon",
"name": "Neón",
"version": "1.0.0",
"apiVersion": 18,
"entry": "plugin.js",
"description": "Un tema oscuro con acentos neón",
"hosts": [],
"categories": ["themes"],
"appThemes": [
{
"id": "neon",
"name": { "es": "Neón", "en": "Neon" },
"colors": { "accent": "#00E5FF", "onAccent": "#000000", "background": "#0A0A14", "surface": "#14142A", "surfaceHigh": "#1E1E3A", "railPanel": "#101026" },
"background": { "type": "gradient", "colors": ["#0A0A14", "#1A0A2E"], "angle": 180 },
"shape": { "cardRadius": 14, "channelRadius": 14, "buttonRadius": 24, "chipRadius": 20, "dialogRadius": 20, "inputRadius": 12 },
"typography": { "scale": 1.1, "titleScale": 1.05, "bodyScale": 1.0 },
"tv": { "typography": { "scale": 1.0 } },
"adjustable": {
"colors.accent": { "swatches": ["#00E5FF", "#7C4DFF", "#FFB300"] },
"shape.cardRadius": { "min": 0, "max": 20 },
"typography.scale": { "min": 1.0, "max": 1.3 },
"background": true
}
}
]
}
plugin.js can be empty (export {};): Kino loads it and calls nothing. Rules for such a plugin:
- No capabilities. A plugin whose only content is
appThemesmay leavecapabilitiesout (or add onlyscreen, for a presentation page: see Turning a theme on from your screen). "hosts": []is allowed from apiVersion 18 in a plugin that only shipsappThemes: it reaches nothing, and its card says it doesn't connect to the internet."categories": ["themes"]lists it under Temas in Kino's plugin store.themesis one of the nine marketplace values (movies,series,anime,live,radio,subtitles,utilities,themes,adult).- It plays nothing, so it does not open the way past Kino's first source picker.
- No consent line: activating a theme is the person's consent, and a theme grants nothing (no network, no code, no data).
- Any other plugin (a catalog, a live TV plugin) may also carry
appThemesbeside its capabilities.
The fields of a theme¶
appThemes is a list of 1 to 8 themes. Each one:
| Field | Rule |
|---|---|
id |
Required. ^[a-z0-9][a-z0-9-]{1,39}$, unique in the plugin. Never change it once published: the person's choice and adjustments hang off it. |
name |
Required. { "es", "en" } (one may be missing: it takes the other) or one string for both; at most 40 characters. |
colors, shape, typography, elevation, motion, player |
The token groups below. Every token is optional: what you leave out stays Kino's. |
background |
{ "type": "solid", "colors": [one] } or { "type": "gradient", "colors": [2 to 8], "angle": whole degrees } (default angle 180). image (apiVersion 26): { "asset", "fit", "dim" }, see a picture behind the app (an older Kino refuses it). |
tv, phone |
The same groups and background, overriding the theme on that form only. |
adjustable |
What the person may change in Ajustes ▸ Apariencia ▸ Personalizar (at most 48 tokens): true, { "swatches": ["#RRGGBB", …] } (colours only) or { "min", "max" } (numbers only). |
pluginColors |
"respect" (default) or "override": what happens to other plugins' own apiVersion 6 theme colours. |
price |
Optional { "kinos": 1 to 1000, "payTo": "<64 lowercase hex>" }. No price is a free theme. See Priced themes. |
experience |
Optional "light" or "full": the whole-app experience the theme looks best with. See The experience. |
logo |
Optional { "wordmark"?, "mark"?, "decor"? } (at least one), vector only. See Your own logo. |
A format error refuses the whole manifest: an unknown field or token, a wrong type (a number where a colour goes), a bad
id, two themes with the same id, more than 8 themes, a name over 40 characters, a malformed price, experience or
logo. A value out of its range does not refuse anything: Kino drops that one token with a warning and keeps its own
value, so the theme still works. node sdk/validate.mjs . prints those warnings for the phone and the TV.
Tokens and ranges¶
The 47 tokens, with the ranges contract.json (manifest.appThemes) enforces:
| Group | Token | Type and range | Kino's own value |
|---|---|---|---|
colors |
accent |
#RRGGBB |
#E50914 |
colors |
onAccent (text and icons on the accent) |
#RRGGBB |
#FFFFFF |
colors |
background |
#RRGGBB (or the background field) |
#0E0E0E |
colors |
surface (cards, panels) |
#RRGGBB |
#181818 |
colors |
surfaceHigh (raised panels) |
#RRGGBB |
#242424 |
colors |
textPrimary, textSecondary |
#RRGGBB |
#F5F5F5, #B3B3B3 |
colors |
focus, onFocus (the TV focus treatment) |
#RRGGBB |
#FFFFFF, #000000 |
colors |
outline, railPanel, placeholderTop, placeholderBottom, success, warning, error, favorite, scrim |
#RRGGBB |
Kino's |
colors |
border (the colour of borders, see Borders) |
#RRGGBB |
none: outline is used without it |
shape |
cardRadius, channelRadius, buttonRadius, chipRadius, dialogRadius, inputRadius |
number, 0 to 32 | Kino's |
shape |
dialogBorder, menuBorder, headerBorder, cardBorder, panelBorder (width in dp, see Borders) |
number, 0 to 4 | 0: Kino draws no borders |
shape |
heroRadius, railItemRadius (apiVersion 26: corners of the framed hero and the floating rail, see Painted surfaces) |
number, 0 to 32 and 0 to 24 | 16 and Kino's |
typography |
scale, titleScale, bodyScale |
number, 0.85 to 1.3 | 1 |
elevation |
cardShadow, dialogShadow |
number, 0 to 1 | Kino's |
elevation |
heroScrim |
number, 0.3 to 1 | Kino's |
motion |
focusZoom |
number, 1 to 1.15 | Kino's |
motion |
crossfadeMs |
number, 0 to 800 | Kino's |
motion |
heroDrift |
"on" or "off" |
Kino's |
player |
buttonScale |
number, 0.8 to 1.4 | 1 |
player |
playButtonScale |
number, 0.8 to 1.6 | 1 |
player |
seekBarScale |
number, 0.8 to 2 | 1 |
player |
labelScale |
number, 0.85 to 1.3 | 1 |
player |
buttonShape |
"circle", "rounded" or "square" |
Kino's |
The token is named by its path: colors.accent, shape.cardRadius, player.buttonShape (that is how adjustable names
them). typography.scale multiplies the system font scale (the combination is capped). On the phone a player button may
look smaller, but its touch target never goes below 48 dp; on the TV the focused button keeps Kino's focus treatment, only
recoloured with focus and onFocus.
How Kino resolves a theme¶
Lowest to highest priority, per token:
- Kino's own value.
- The theme, then its
tvorphoneblock. - The person's adjustments, only on tokens in
adjustable, clamped to itsmin/max(or one of itsswatches) and to the ranges above. - The device. With reduced effects (Ajustes ▸ Experiencia visual) the
motiontokens do nothing; whether TV cards are rounded at all stays the person's "Esquinas redondeadas" switch (off by default on TV for performance; Apariencia offers to turn it on when a theme uses a radius). A theme never decides what a device can draw.
The legibility guardrails¶
The same thresholds as the apiVersion 6 theme (minTextContrast 4.5, minUiContrast 3), read on the effective
colours (Kino's where your theme changed only one side). A pair that fails falls back to Kino's values on the side your theme
set, with a warning:
| Pair | Needs | When it fails |
|---|---|---|
| The background (every gradient stop) | dark (relative luminance at most 0.05) or light, when the theme brings its own textPrimary and textSecondary that read on the background and on surface (Kino 0.9.82; a light background used to be refused always) |
Kino's background (and its accent if needed) |
accent on the background |
3:1 | Kino's accent and onAccent, as a pair |
onAccent on accent |
4.5:1 | Kino's accent and onAccent, as a pair |
| Kino's accent on your background | 3:1 | Kino's background |
textPrimary and textSecondary on the background and surface |
4.5:1 | Kino's text colours |
textPrimary on surfaceHigh |
4.5:1 | Kino's surfaceHigh (then the text colours) |
Text on your surface |
4.5:1 | Kino's surface |
focus on the background; onFocus on focus |
3:1; 4.5:1 | Kino's focus and onFocus |
Unlike the apiVersion 6 theme, appThemes has no "not close to Kino's red" rule. The person's own adjustments go through
the same checks: Apariencia refuses a colour that would not read, in Kino's words.
What a theme never restyles¶
Kino draws in its own look, whatever theme is active: Ajustes ▸ Apariencia itself, its preview, the purchase and experience
questions, the plugin install and update consent sheets, the 18+ code and setting locks, the go.url sheet, the lock screen,
and every other screen that asks the person for a decision. Kino's own logo stays on the splash, the gate and those decision
screens. QR codes stay black on white, and what is drawn over video or artwork keeps its colours.
pluginColors¶
Other plugins may have their own apiVersion 6 theme colours. With "respect" (the default) their pages and their player
accent keep them; with "override" the active theme's colours win everywhere. The person always has the last word: Apariencia
shows a Colores de los plugins switch for every theme, whatever you declared.
Priced themes (price)¶
A theme may cost kinos, Kino's free coin (the person earns them by watching: 1 every 10 minutes, at most 20 a UTC day).
"price": { "kinos": 50, "payTo": "0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef" }
kinosis a whole number from 1 to 1000;payTois your coins account: 64 lowercase hexadecimal characters. Both are required together; anything else refuses the manifest.- Before a priced theme turns on (from Apariencia, from your plugin's manage sheet or from your own
go.useTheme), Kino shows its own purchase sheet: «Comprar «name»», «Cuesta N kinos.», the person's balance («Tienes N kinos.»), and Comprar por N kinos, enabled only when the balance covers it («Te faltan N kinos para comprarlo.» otherwise). A failed purchase charges nothing. Apariencia shows the price on the list and on the preview button, and the balance next to priced themes. - The kinos go to
payTo. One purchase per theme and account, valid on every device of the person. - Your plugin never sees the purchase, the balance or the coins session: you need no
coinscapability to sell a theme. Declarecoins(apiVersion 16, a red consent line) only if your own screen wants to show the balance withkino.coins.balance(); when it rejects withdisabled, show nothing about kinos. - The price and the account are in your public manifest: they are what Kino charges and pays, not a lock on your files.
- Your account. A coins account is the same 64-hex identifier Kino Social calls the author's
user_key: the coins service derives it from the person's Telegram identity with a secret, and never stores the Telegram id. It is the id of the person who signed in to Kino with Telegram, sopayTomust be the account of the person who is paid. From Kino 0.9.81 you read and copy it in Ajustes ▸ App ▸ Tu cuenta de kinos (it needs the Kinos switch on and your Telegram sign-in): tap the row to copy the whole 64 characters. - Your own theme. The service refuses a purchase whose buyer and
payToare the same account (self_purchase): nothing is charged. To test the purchase flow, use a second account, or the kit's mocks and a debug build. - Refunds. There are none: a purchase is final, the kinos are already in the author's balance, and the service has no refund operation. What a person never pays is a failed purchase: it charges nothing, and buying the same theme twice charges once.
The experience (experience, go.setExperience)¶
Kino has two whole-app presets in Ajustes ▸ Experiencia visual: light (no shadows, no effects, square corners) and full (every effect on, rounded corners).
- A theme that looks best with one says so with
"experience": "light"or"full". When the person turns the theme on, Kino asks («Este tema se ve mejor con la experiencia completa. ¿La usamos también?», with «Usar la completa» and «Dejar la actual»). Nothing changes without their yes, and nothing is asked when the app already has it. - Your own screen may ask too:
go: { setExperience: "light" | "full" }, only from the person's own press or submit on your screen (neveropen, a timer, a change, a load-more, anonClose, a panel or a notice). Kino asks first, naming your plugin («Tu plugin» pide la experiencia completa. ¿La usamos?). Any other value drops thego, logged.
Your own logo (logo)¶
A theme may draw its own logo in place of Kino's in the phone's side menu and header and in the TV's rail. Vector only (no image file, no network):
"logo": {
"wordmark": { "size": [120, 30], "paths": [{ "d": "M0 0 L26 15 L0 30 Z", "fill": "accent" },
{ "d": "M40 4 H52 V26 H40 Z", "fill": "textPrimary" }] },
"mark": { "size": [30, 30], "paths": [{ "d": "M15 0 L30 15 L15 30 L0 15 Z", "fill": "accent" }] }
}
- At least one of
wordmark(the long logo: phone menu and header, the TV's open rail) andmark(the square one: the TV's collapsed rail). What you leave out stays Kino's. sizeis[width, height], whole numbers from 1 to 1000, at most 8 times wider than tall (or the reverse).- 1 to 8
paths, eachdup to 2,000 characters of SVG path data (M L H V C S Q T A Z, numbers, spaces, commas, signs);fillisaccent,onAccent,textPrimary,textSecondary(they follow the theme and the person's adjustments) or a fixed#RRGGBB. decor(Kino 0.9.82) does not replace Kino's logo: it is drawn over it, in the wordmark and in the mark, in the space of the "o". It is{ "paths": [...] }(1 to 8, the same format). Its centre is the origin (0, 0), y grows downwards, and the ring's outer radius is 100. A hat on the "o" sits at y < -100, something covering the whole "o" is a disc of radius 100, and the dot of the "i" is near (-353, -132). Use it to play with Kino's own logo (Luffy's straw hat, the arc reactor as the "o").- Kino keeps its own logo on the splash, the gate and every screen that asks for a decision.
Borders (colors.border, shape.*Border)¶
Available from Kino 0.9.82
No new apiVersion: an older Kino ignores these tokens and draws no borders.
Kino has no borders. A theme may ask for them, as a width in dp (0 to 4; 0 or absent = none) per kind of element, plus a colour:
| Token | Frames |
|---|---|
shape.dialogBorder |
dialogs and bottom sheets |
shape.menuBorder |
dropdown menus |
shape.headerBorder |
headers: a line along their lower edge |
shape.cardBorder |
cards |
shape.panelBorder |
panels |
The colour is colors.border; when the theme gives none, outline is used. A border follows the element's corners (dialogRadius, cardRadius…). A theme that asks for no borders looks exactly as before.
"colors": { "border": "#8624A0" },
"shape": { "dialogBorder": 2, "cardBorder": 1, "headerBorder": 1 }
Painted surfaces, layouts and files (apiVersion 26)¶
Next Kino release, not published yet
Everything in this section arrives with "apiVersion": 26 (Kino 0.9.87, provisional: the number moves if the release does).
A theme that uses them must declare "apiVersion": 26: a Kino that does not know 26 then refuses the whole manifest ("Este
plugin necesita una versión más nueva de Kino") instead of misreading it. Do not put these keys in a theme that declares a
lower apiVersion: Kino 0.9.87 skips them there, but an older Kino refuses a theme with an unknown field. With none of these
keys a theme looks exactly as before, on every Kino.
Level 1 colours, shapes and sizes. Level 2 lets a theme paint: a gradient or glossy fill, a gradient outline and a soft glow on the elements Kino draws, a background picture, its own font, and two TV layouts (a framed hero and a floating rail). It is still data: no code runs, no network is used at runtime, and the pictures and fonts ship in your plugin's own repository.
surfaces: fill, stroke and glow per element¶
surfaces is an object whose keys are the elements below; each value is { "fill"?, "stroke"?, "glow"? }. An element you do not
list keeps Kino's own look.
| Element | Where it paints |
|---|---|
button |
the primary filled button (a dialog's confirm, the hero's "Continuar viendo") |
buttonGhost |
the secondary button next to it (Cancel, "…") |
navItem, navActive |
the top menu's pills and the rail's items, inactive and active (the focused or chosen one) |
rail |
the rail's panel: its fill and outline |
iconButton |
the round corner buttons (profile, bell, reload) and the plugins button |
card, cardFocus |
a poster or wide card at rest and focused: stroke and glow (the fill is the picture, so a card has none) |
focus |
the focus ring of everything else focusable: a stroke and a glow, never a fill |
hero |
the framed hero's card (stroke and glow; its corners are shape.heroRadius) |
progress |
the filled part of a continue-watching progress bar |
The three value types:
| Value | Shape | Range |
|---|---|---|
fill |
{ "type": "solid", "color": "#RRGGBB" } or { "type": "gradient", "colors": ["#RRGGBB", …], "angle": degrees } (angle default 180) |
2 to 8 colours; a gradient outside that is dropped with a warning |
stroke |
{ "width": dp, "color": "#RRGGBB" } or { "width": dp, "gradient": { "type": "gradient", … } } (exactly one of the two) |
width 0 to 4 |
glow |
{ "color": "#RRGGBB", "radius": dp, "alpha": 0 to 1 }, a blurred halo behind the element |
radius 0 to 24 |
"surfaces": {
"button": { "fill": { "type": "gradient", "colors": ["#D9232F", "#A8060F"], "angle": 180 }, "stroke": { "width": 1, "color": "#FF7B83" } },
"navActive": { "fill": { "type": "solid", "color": "#2A0D12" }, "stroke": { "width": 1.5, "color": "#E50914" }, "glow": { "color": "#E50914", "radius": 10, "alpha": 0.55 } },
"cardFocus": { "stroke": { "width": 2, "color": "#F2E8EA" }, "glow": { "color": "#E50914", "radius": 14, "alpha": 0.45 } },
"card": { "glow": { "color": "#E50914", "radius": 10, "alpha": 0.22 } }
}
A theme's tv and phone blocks may carry their own surfaces; the block wins over the theme on that form only. The phone paints
button, buttonGhost, iconButton, card and progress; the rail, the top menu and the framed hero exist on the TV only.
style.gloss: a glossy look from one number¶
"style": { "gloss": 0 to 1 }. An element with no explicit fill gets a lighter-top to darker-bottom gradient derived from its
base colour (the accent for button and navActive, surfaceHigh for iconButton and buttonGhost), and button, navActive and
cardFocus get a glow derived from the accent. Anything you write explicitly wins over the derived value. 0 or absent = Kino's flat
look. A value outside 0 to 1 is clamped with a warning.
layout: a framed hero and a floating rail (TV)¶
"layout": { "hero": "fullBleed" | "framed", "rail": "strip" | "floating" }, both optional; tv and phone blocks may carry it.
"hero": "framed"draws the Home's hero as an inset rounded card (withsurfaces.hero) instead of a picture bleeding to the screen's edges. Its corners areshape.heroRadius(0 to 32, default 16)."rail": "floating"keeps the TV's left rail as a rounded panel at all times (withsurfaces.rail), closed or open, with equal air on both sides; its items takeshape.railItemRadius(0 to 24).- TV only. The phone ignores both keys and keeps its own layout. An unknown word refuses the manifest; the device's switches below turn each layout off.
assets and background.image: a picture behind the app¶
A theme lists the files it ships in assets, each { "id", "path", "sha256", "bytes" }: id ^[a-z0-9][a-z0-9-]{1,39}$, path a
relative path inside your plugin's repository, sha256 64 hexadecimal characters, bytes the exact size. At most 16 files.
"assets": [ { "id": "background", "path": "assets/background.webp", "sha256": "0ed54aa7…", "bytes": 8276 } ],
"background": { "image": { "asset": "background", "fit": "cover", "dim": 0.35 } }
background.imageis{ "asset": id, "fit": "cover" | "top", "dim": 0.3 to 1 }:coverfills the page and is centred,topanchors it to the top edge, anddimis how much black goes over it.colors.backgroundstays required as the fallback (while the picture loads, when it fails, and for the contrast checks). Atvorphoneblock may name a different picture.- Kino fetches each asset at install from the same address your manifest came from (never from a new host), checks the size and the sha256, and keeps the files with the plugin: an update replaces them, removing the plugin removes them. A picture is at most 2,000,000 bytes and 3,840 x 2,160 pixels, a font at most 1,000,000, all the files together 6,000,000.
- A file that is missing, fails its hash, is over a cap or cannot be decoded is left out, with a note in the log: the plugin and the rest of the theme still install, and the page shows the fallback colour (or Kino's font). It never refuses the install.
- The text contrast is checked against the fallback colour darkened by
dim; the picture itself is trusted beyond that, so test it in Kino. Pictures are decoded once, at the window's size, off the main thread.
An asset can be installed from a repository address (GitHub, a manifest URL); a plugin imported from a .kinoplugin file or
packaged by hand does not carry its theme files yet.
typography.fontFamily: your own font¶
"typography": { "fontFamily": { "regular": "<asset id>", "bold": "<asset id>" } }: bold is optional, and both name entries of
assets (a TTF or OTF file of at most 1,000,000 bytes). Every text Kino draws with its own scale takes the family, and the scales
(scale, titleScale, bodyScale) keep working on top. A font that is missing or that Android cannot read leaves Kino's font.
The two new shape tokens¶
shape.heroRadius (0 to 32) and shape.railItemRadius (0 to 24) join the table in Tokens and ranges. Below apiVersion 26
they are skipped without a word.
Guardrails for what you paint¶
Every rule drops that value with a warning (node sdk/validate.mjs . prints it, and so does Kino's log); it never refuses the
manifest, so a theme with one bad number stays usable:
- Text must stay readable on a fill. The text colour Kino puts on a fill (
onAccentonbuttonandnavActive, the page's text elsewhere) must keep 4.5 : 1 against every stop of a gradient. A fill that fails is dropped: "surfaces.navActive.fill: the text on it isn't readable on every stop (at least 4.5:1); dropped". - Focus is never invisible. A
focusorcardFocusstroke too close to the page colour is dropped and Kino keeps its own ring.focushas a stroke and a glow, never a fill (afillthere is dropped with a warning). - Colour count, angle, width, radius, alpha and
dimare held to the ranges above (clamped or dropped, with a warning). - With
background.image,dimis at least 0.3.
The person's switches¶
The device always wins over a theme. In Ajustes ▸ Experiencia visual ▸ Personalizar uno por uno (also reachable from the Rendimiento tile of the plugins panel on the TV) the person can turn each of seven effects off on its own, keeping your colours, shapes and type: glows, gradient fills, gradient outlines, the background picture, the framed hero, the floating rail and the theme font. They are per device. On a weak TV, "all effects off" turns all seven off. So design every effect as an addition: a theme with the seven off must still look right.
A complete example¶
kinotvapp/kino-plugin-theme-crimson is a small, unsigned theme using every
key of this section: gloss and gradient buttons, a dark pill with a red ring for the active menu, a soft glow on the cards, a
framed hero, a floating rail and a background picture. Install it from Plugins ▸ Agregar with kinotvapp/kino-plugin-theme-crimson.
Turning a theme on from your screen (go.useTheme, activeTheme)¶
The person activates a theme in Ajustes ▸ Apariencia (Tema de Kino is always the first option; a preview shows a Home
row, a dialog and the player controls before Usar este tema), from your plugin's manage sheet («Ver temas», «Activar tema
de …»), or from a button on your own screen (the screen capability, apiVersion 14+, which a theme plugin
may declare to present its theme):
export async function screen({ activeTheme }) {
const on = activeTheme === "neon";
return { type: "ElevatedButton", labelText: on ? "Desactivar" : "Activar", labelTextEn: on ? "Turn off" : "Turn on",
onPressed: { go: { useTheme: { theme: on ? null : "neon" } } } };
}
export async function screenEvent() { return null; }
screenandscreenEventreceiveactiveTheme: the id of your theme active now, elsenull. Kino callsscreenagain after any change (one made in Apariencia too), so one button can flip.go: { useTheme: { theme } }:themeis one of yourappThemesids (it does what Apariencia's button does: the same per-profile choice, the same sync, the person's adjustments kept) ornull(back to Kino's theme, only while one of yours is active: you can never reset another plugin's).- Only from the person's own press or submit on your screen: dropped, logged, from
open, a timer, a change, a load-more, a pop-up'sonClose, a panel or a notice, and below apiVersion 18. Refused, logged, with nothing changed, when Apariencia does not list that theme as yours (another plugin's id, your plugin off in this profile, 18+ while locked). - A priced theme the person has not bought opens Kino's purchase sheet first; a theme with
experienceasks about it. - Kino shows its own toast, «Tema aplicado» or «Volviste al tema de Kino», and repaints the whole app, your screen included.
- A presentation screen that needs no menu icon can open from your settings page only:
"screen": { "label": "Neón", "opensFrom": ["settings"], "settingsButton": { "label": "Ver presentación", "labelEn": "See presentation" } }.
The person's side¶
- One theme is active at a time, per profile; the choice and the adjustments sync between the person's linked devices, both ways.
- Personalizar lists only what you marked
adjustable(swatches and a written#RRGGBBfor colours: swatches are what work with a remote; a stepper for numbers), plus «Volver a los valores del tema». - Disabling or removing your plugin returns to Kino's theme; the choice is kept and comes back on reinstall. An update
re-resolves the theme, and adjustments to tokens no longer
adjustableare dropped. - Any failure resolving a theme gives Kino's own look, never a crash.
Test it with the kit¶
node sdk/validate.mjs . # format, plus each theme's warnings on phone and TV
node sdk/run.mjs --context '{"activeTheme":"neon"}' . screen # your presentation screen with your theme on
node sdk/run.mjs . screenEvent activate --trigger tap # what Kino does with go.useTheme / go.setExperience
validate.mjs prints lines such as appThemes neon (tv): shape.cardRadius: 40.0 is outside 0.0..32.0; Kino's is used and
appThemes neon (phone): background: is too light (the background must be dark for now); Kino's is used: the app's own
warnings, word for word. screen prints the tree with any malformed go dropped, and screenEvent says when a go.useTheme in an answer would be dropped (not a tap, not one of your ids, null with
none of yours active). The kit draws no colours: look at the theme in Kino (Ajustes ▸ Apariencia ▸ the preview).
Checklist¶
- [ ]
"apiVersion": 18and the person knows it needs Kino 0.9.81 or later. - [ ]
node sdk/validate.mjs .passes and prints no warning you did not expect, for phone and TV. - [ ] Every theme
idis final;namehasesanden. - [ ] The background is dark, or light with your own readable text, and every pair in the guardrails reads.
- [ ]
adjustableoffers swatches (not only free colours) so a TV remote can use it. - [ ] A
pricehas your realpayTo; you did not addcoinsjust to sell. - [ ] A screen that turns the theme on reads
activeThemeand usesgo.useThemeonly from a tap. - [ ] Level 2 keys (
surfaces,style,layout,assets,background.image,typography.fontFamily) only in a theme that declares"apiVersion": 26; every asset'ssha256andbytesmatch the file, and the picture is at most 2 MB. - [ ] The theme looks right with the seven effects off (Ajustes ▸ Experiencia visual): colours and shapes carry it, effects only add.
- [ ]
"categories": ["themes"], and"hosts": []when the plugin only ships themes.