Skip to content

What people see

  • The consent sheet. When someone types your address, Kino shows "Instalar <name>", your version and author, the description, the list of hosts under "Se va a conectar con:" (left out when hosts is empty), and the warning "Plugin no verificado: solo instálalo si confías en quien lo hizo." with "Instalar" and "Cancelar". If your manifest has a password setting it adds "Este plugin usa tu usuario y contraseña"; a url setting adds "Se conectará a los servidores que escribas en su configuración". Declaring download adds "Puede descargar videos para verlos sin conexión", drm adds "Reproduce video protegido (DRM)", channels adds "Agrega canales en vivo a la pestaña En vivo", secrets adds "Usa datos sellados por su autor", the subtitles capability adds "Agrega subtítulos a tus películas y series", each insecureHttp host adds, in red, "Conexión sin cifrar con <host>", liveStreamHosts: "any" adds, in red, "Puede reproducir canales desde cualquier servidor que indique su lista", and streamHosts: "any" adds, in red, "Puede reproducir video desde cualquier servidor que indique". From apiVersion 6, migrate adds "Revisar lo que tienes guardado (biblioteca, historial, favoritos) para pasarlo a este plugin", telemetry: true adds "Comparte registros de errores con Kino para corregir fallas" and telemetry: "verbose" adds "Comparte registros detallados de reproducción y errores con Kino para corregir fallas"; "browser": true adds, in red, "Puede abrir páginas web ocultas para encontrar el video" and "browser": "pages", in red, "Puede abrir páginas web ocultas para mostrar contenido y encontrar el video" (Hidden browser). From apiVersion 7, tracking adds, in red, "Le contará a <your hosts> qué ves y cuándo lo terminas" (Telling a tracker) and segments adds "Agrega el botón para saltar la intro y los créditos" (Where the intro and credits are). On an update, what is new carries a "nuevo" chip. Nothing of yours runs before they accept.
  • A long host list folds. With more than 3 hosts the sheet says "Se va a conectar con N servidores:", lists the first 3 (on an update, the new ones first) and "y N más (M nuevos)", with a "Ver todos" / "Ver menos" toggle. The permission lines and the "Plugin no verificado" warning sit above the list and never fold; "Cancelar" and "Instalar" stay pinned below it while the body scrolls. A short list still reads better: declare what you use, not every mirror you ever saw.
  • Host dialogs. A kino.fetch to an undeclared host during resolve/episodes, and an undeclared host of the video the player opens or meets mid-playback, ask the person ("Rechazar" / "Permitir"; the focus starts on "Rechazar"). For a movie's or episode's video, subtitles or audio the dialog also offers "Permitir video de cualquier servidor" (the broad video permission); once chosen, the plugin's details say "Puede reproducir video desde cualquier servidor" next to "Quitar permiso de video amplio". A plugin with remembered refusals also shows "Olvidar rechazos de host".
  • While resolve runs the player shows "Resolviendo el video de <name>…", and after 5 s "… buscando enlaces (N s)".
  • When a stream can't play, the player says why in Spanish, never the player's own English: for example "Este aparato no puede reproducir este formato de video (4K/HEVC)", "El servidor del video respondió con un error" or "No se pudo reproducir este video".
  • Configurar. A plugin with settings has a "Configurar" button in Ajustes ▸ Plugins and, from Kino 0.9.50, its own tab in Ajustes with the same form (The settings form). Until every required setting has a value its status is "Falta configurar" and nothing of it runs.
  • Ver más. A Home row with a ref ends in a "Ver más" card, and a search page with a next shows "Ver más resultados de <name>": both open a grid that asks you for the next page as the person scrolls.
  • Search, Home and the library. Your results appear in search under your plugin's name (with your color), next to the app's own sources; your home rows appear on Home after the app's own; your titles play in Kino's player and appear in "Continuar viendo" and the library. Titles of a plugin that declares download can be saved for offline viewing (Downloads); Plugin titles can be sent to a TV (Chromecast and DLNA, see Sending to the TV below). A live item's card says "EN VIVO" and plays on tap, with no info page; a channel never enters "Continuar viendo" or the library (Live channels). A plugin found through the kino-plugin topic carries the label "De la comunidad" on its card. In search, a live channel whose name has nothing to do with what was typed is left out (the rule); movies and series always stay.
  • Status of each plugin in Ajustes > Plugins: "Activo", "Desactivado", "Falta configurar", "No responde — actívalo para volver a intentar" (three timeouts in a row; the person can re-enable it), "Actualización disponible — requiere tu aprobación", and "Archivos dañados, reinstálalo" (the installed file no longer matches what was installed).
  • Disable and uninstall. A disabled plugin disappears from search and Home; its titles stay in the library and say "Activa el plugin <name> para ver esto". Uninstalling deletes the plugin's files, its storage and its cached Home rows immediately, but keeps the person's library titles and progress: opening one says "Esto venía del plugin <name>, que ya no está instalado", and installing the plugin again restores them. That is one more reason to keep id and ref handling stable. Titles already downloaded keep playing offline and can be removed from Descargas. From Kino 0.9.87 each card in Instalados has its own uninstall button (built-in and required plugins have none).

  • Signed plugins. A signed plugin (Signed plugins) shows the line "Firmado por su autor" on the consent sheet, a "Firmado" pill on catalog and community cards ("Activo · Firmado" on an installed one), and "Clave del autor: ABCD-EF01-2345-6789" in its details (phone: Gestionar; TV: the installed plugin's actions). Kino 0.9.45 and later.

Sending to the TV (Chromecast and DLNA)

Plugin titles can be sent to a TV from the player. Nothing in the manifest turns it on: Kino decides per stream from what your resolve returns (url, mime, headers, drm):

Your stream What Kino does
mp4/webm (or another progressive file) with no headers, on a host your plugin may use The TV fetches the URL itself; the phone moves no bytes. If the TV fails it, it is relayed through the phone.
HLS (.m3u8) Through the phone (a Chromecast needs CORS on it): playlists are rewritten so every segment and key goes through the phone.
Any file with headers (Referer, cookies, tokens in headers) Through the phone: it fetches with your headers and the TV only sees a local address.
A request-signed stream (Kino 0.9.50) Through the phone, which calls sign() for every playlist and segment the TV asks for.
DRM (Widevine or ClearKey), DASH, progressive MPEG-TS, or a format nothing tells apart Not sent: the person reads "Este título no se puede enviar a la TV" (protected ones: "Este título está protegido y no se puede enviar a la TV").

What helps authors: return a real mime (video/mp4, application/vnd.apple.mpegurl) or a URL that ends in the right extension; Kino probes the first bytes of a stream nothing describes (a 1 KB ranged read, 2 s) but that costs a request. Prefer links that need no headers (the lightest route); every host involved must be one your plugin may reach (declared, typed, or covered by an "any" permission), over https. While casting, the phone itself stays silent.

From Kino 0.9.54, an apiVersion 8 music or podcast track goes to a Chromecast as music, with its title, artist, album and cover, and to a DLNA TV as an audio item; an 18+ track sends only the app's name.

External resolver apps (Kino 0.9.66)

When a plugin answers external instead of a url (External resolver apps):

  • The first time, a dialog asks: "" quiere usar "" para resolver contenido de tipo "". / Esta aplicación no es de Kino y actúa por su cuenta. ("Permitir" / "No permitir"). With several apps for the protocol, "Elige qué aplicación usar"; the pick is remembered.
  • While the app works: "Abriendo con """ with its live progress (its own short text, or "Buscando...") and a "Cancelar" button.
  • When it fails: "No se pudo resolver este contenido (): ."; with no app installed, "Este contenido necesita una aplicación externa que no tienes instalada." (or, when the plugin names one, a sheet that offers to download it from GitHub); after a "no", "No autorizaste resolver este contenido con ...". A later playback error the app explained reads "La aplicación que ofrece este video dijo: ...".
  • Their decisions live in Ajustes, in the "Fuentes externas" section, where each can be revoked. Such a title can only be played, never downloaded.
  • Sending it to a TV goes through the phone like any plugin title; it was tried on a real Chromecast (and DLNA on an LG webOS TV, with an HLS answer) (Casting a resolver's title).

Sync providers (Kino 0.9.74)

When a plugin declares syncProvider (Sync providers):

  • The consent sheet says, in red, "Sincronizará tus datos a través de su servicio: el plugin y su servicio podrán leerlos" ("Will sync your data through its service: the plugin and its service can read it"). An update that adds the capability waits for approval.
  • Ajustes de todos los perfiles ▸ Sincronización ▸ Proveedor lists "Red local" and every installed provider, each with a switch; only one is on at a time, or none. Turning one on asks "¿Sincronizar con <name>?" ("La sincronización por red local se apaga mientras uses <name>"; "Si <name> ya guarda datos de otro aparato, se combinan con los de este. Nunca se borra nada de ningún lado.") with "Combinar con este aparato".
  • The provider's row shows "Sincronizado hace 3 min", "Esperando la primera sincronización", "Falló la última sincronización: <reason>", "Falta el token: escríbelo en Configurar" or "El token no coincide o los datos guardados no son de Kino", the plugin's own syncStatus line, and the buttons Configurar ("Set up"), Sincronizar ahora, Restablecer sincronización, Enviar configuración ("Send settings") and Recibir configuración ("Receive settings"); on a device that still lacks the settings, "Recibir configuración" leads and "Configurar" turns quiet.
  • Receiving on a second device: a QR, an address and a 6-digit code for 3 minutes (and, when the Cloudflare quick tunnel opens, the words for "Otra red"), then "Recibido para <plugin>: ¿aplicar?" with the labels of the settings it got, never their values, and "Aplicar".

Kino 0.9.88

  • "Continuar viendo" opens the title page. A "Continuar viendo" card opens the title's page (a series on the episode to go on with) instead of the player; its play button starts it.
  • The title page gets the video ready. While the person reads the page of one of your titles, Kino may already resolve it (resolveAhead) or let your plugin warm up (prepare), so the video starts sooner. The person sees nothing of it, and nothing changes if they leave the page.
  • "Abrir <name>". After an install, the confirmation's main button reads "Abrir <name>" when it opens your plugin's own screen; a plugin that only adds a screen with a menu entry gets that button too.

Screens and apiVersion 14 (Kino 0.9.74)

Available with Kino 0.9.74

Available from Kino 0.9.74. An older Kino refuses these plugins with «Este plugin necesita una versión más nueva de Kino»; to keep reaching people on an older version use enhancements (see Screens without raising your apiVersion).

  • Screens. A plugin with a screen gets an entry on the TV sidebar (the first three plugin screens directly, the others under «Más pantallas») and a chip on the phone's Inicio strip, or a button at the top of its settings page; the screen opens with Kino's title bar (the plugin's name and a close button).
  • New red lines. library, playerPanelTab, playerControl, room, schedule and ai each show their red line on the consent sheet and are asked at install and on the update that adds them; shared shows a plain line. The person can switch each one off in the plugin's tab in Ajustes (Rooms, the library and player control, Background jobs, shared results and AI).
  • The player slot. A plugin with a fixed player slot element shows «Mostrará algo suyo de forma permanente en el reproductor mientras ves un video» in red, asked on each device; its switch is «Dejar que muestre algo en el reproductor». On the TV its elements sit in the top-right corner of the player.
  • Updates. An update that adds a red consent line or a new host shows it first, open, under «Nuevo en esta actualización».
  • Tabs in the player panel. A plugin with playerPanelTab adds a tab to the player panel of any title; the person can hide it ("Mostrar en el reproductor") or reorder it (Ajustes, "Paneles del reproductor"). The player panel.
  • Exporting a plugin. Plugins ▸ Instalados ▸ Gestionar ▸ "Exportar plugin" shares a .kinoplugin file that installs on another phone as a local plugin. Exporting and importing a plugin file.

Kino 0.9.77 (apiVersion 15)

Available with Kino 0.9.77

An older Kino refuses these plugins with «Este plugin necesita una versión más nueva de Kino».

  • The Home bell. A plugin with notifications leaves short notices: the bell shows a badge with the unread ones and the plugin updates waiting for approval; tapping a notice goes to the plugin's screen and marks it read. Each device keeps its own.
  • New consent lines. identity shows, in red, «Podrá saber tu usuario de Telegram y enviarlo a sus servicios»; notifications, «Podrá mostrarte avisos en la campanita»; a store (pluginStore), «Agrega plugins de sus servidores a tu tienda» and, if it is live, also in red «Lo que busques en la tienda llegará a sus servidores». The person can switch identity and notifications off in the plugin's tab in Ajustes.
  • The plugin store. Plugins shows one store built from the active stores (Kino Plugins ships with the app): the tabs «De Kino» (From Kino: Kino Plugins' default list), «De la comunidad» (Community: everything else, from every store, with the «Populares»/«Recientes» sort) and «Instalados» (Installed), a store filter and, on every card, «de <store>». A reload icon syncs the stores and ends with a toast, «Se actualizaron N plugins» or «Tus plugins están al día». Searching, filtering and paging are local; Kino applies its blocklist and the 18+ code to everything stores list, and keeps one plugin per id across stores. A plugin a store stops listing stays installed and Instalados says «Ya no está en ninguna tienda». Plugin stores.

Kino 0.9.78 (apiVersion 16 and 17)

Available from Kino 0.9.78

kino.coins and kino.sync.setActive arrive with Kino 0.9.78; kino.library.stats and "perProfile" are apiVersion 17, in Kino 0.9.81. An older version refuses those plugins with «Este plugin necesita una versión más nueva de Kino».

  • Kino coins. coins shows, in red, «Podrá ver tu saldo de kinos y regalar tus kinos». It has no switch of its own: the person revokes it by disabling or removing the plugin, and if they switch Kinos off in Kino's Ajustes the plugin must show nothing of coins (kino.coins).
  • The library line grew. It now reads «Podrá leer lo que has visto y guardado en Kino, cuánto lo ves y a qué hora, y enviarlo a sus servicios», because with apiVersion 17 the plugin can read a month's aggregates (kino.library.stats). An update that raises a plugin already holding library to apiVersion 17 asks the person again.
  • Switching sync provider from the plugin. A provider may offer its own button; Kino always asks its own question with the plugin's name (kino.sync.setActive).
  • Per-profile jobs. A perProfile job has, in the plugin's tab in Ajustes, the usual job row (off by default, covering every profile) and, for each profile, «Incluir este perfil», on by default (Background jobs).

Kino 0.9.81 (apiVersion 20): plugins that use each other

Available from Kino 0.9.81

The plugin protocol is apiVersion 20, which arrives with Kino 0.9.81.

  • One plain line per door on the install sheet of a plugin that uses another one's doors: «Usa datos de TMDB (Movie records from TMDB)», the provider's name and the door's summary (the repository, «Usa datos de kinotvapp/kino-plugin-tmdb», while the provider is not installed). Not red, no switch, no approval of its own; on an update that adds a door the line is marked new. There is never a question per call.
  • An install button inside the plugin. While the provider is missing, the consumer shows its own screen with a button; the button opens Kino's normal install sheet for the provider, with the provider's own consent lines, and nothing is installed until the person taps Instalar. If it is already installed Kino says «Ese plugin ya está instalado».
  • Removing the provider leaves the consumer installed; it simply shows its install screen again.
  • A plugin that only provides (no capability, no host) says on its card that it does not connect to the internet, and does not show up as a source in search or Home.
  • A screen-only consumer (only screen, "hosts": []) says on its card that it does not connect to the internet only when it has no settings at all; its install sheet still shows the «Usa datos de …» line of each door it uses.

Kino 0.9.81 (apiVersion 18): app themes

Available from Kino 0.9.81

App themes are apiVersion 18, which arrives with Kino 0.9.81. An older Kino refuses a plugin that declares appThemes with «Este plugin necesita una versión más nueva de Kino».

  • Ajustes ▸ Apariencia. Lists Kino's own theme and every theme of the installed plugins, each with the plugin it comes from. The person opens a preview (cards, a dialog, the player's controls), then turns it on; one theme is active at a time, per profile, and the choice syncs between their devices. «Personalizar» changes only what the theme's author allows.
  • No consent line. A theme is data: no network, no code, no capability. It can never restyle what Kino asks the person to decide: Ajustes ▸ Apariencia itself, the purchase and experience questions, the gate and the splash keep Kino's own look.
  • A theme can cost kinos. In the list the row says «Gran Tesoro · 50 kinos», on the preview the button reads «Comprar por 50 kinos» and, above it, «Tienes N kinos.» (the person's balance). Pressing it opens Kino's own sheet with the price and the balance; «Comprar por N kinos» is enabled only when the balance covers it («Te faltan N kinos…» otherwise). It is bought once per account and works on every device; a failed purchase charges nothing. The same sheet appears when the plugin's own screen asks to turn the theme on. Free themes show none of this (App themes).
  • The experience. A theme may suggest the light or the full experience of the whole app; Kino asks the person first («Experiencia para “…”», «Dejar la actual» / «Usar la ligera» or «Usar la completa»), and a plugin's screen may ask the same with go.setExperience (App themes).
  • The logo. A theme may draw its own logo in the side menu, the TV rail and the header.
  • Where the author is paid. Ajustes ▸ App ▸ «Tu cuenta de kinos» shows the person's account (first and last 8 characters) and copies all 64 on a tap: the payTo of a theme's price.
  • A gift. Kino announces «Te regalamos 100 kinos» in the Home bell, once, as its own notice (not a plugin's).

Kino 0.9.74 (apiVersion 13)

With the apiVersion 13 capabilities (What's new):

  • No new consent line: socket, byteSource, storageLarge, catalog, qrScan and imageSource add nothing to the consent sheet (a socket reaches only the hosts the sheet already lists).
  • A byte stream plays like any video, and casts to a Chromecast or a DLNA TV from the phone over the home network. When your read fails the person reads your error, or "El plugin no entregó los datos del video" for a wrong answer. Its titles show the download button, but such a video never downloads.
  • The QR scanner: the camera full screen with "<plugin name> quiere leer un código QR", your title, "Apunta la cámara al código QR" and a close button; a code that is too long reads "Este código no es válido para <plugin>". Without the camera permission Kino asks for it, and explains why with Retry and Cancel if the person refuses.
  • A qr setting is a QR code on the plugin's settings form, redrawn every refreshMs; with no text it reads "Sin información".
  • Images from the plugin appear card by card as they come on screen; a picture that fails, or a title saved with one on another device, shows the usual placeholder. The person never sees an error for a picture.

From Kino 0.9.54

With nothing new in your manifest, except where said:

  • Kino in Spanish or English. The person picks the app's language in Ajustes ▸ App ▸ Idioma ("Automático" follows the device: Spanish on a Spanish device, English on any other). Kino's own texts follow it, the consent sheet and the messages Kino words for your plugin's failures included. What your plugin returns (titles, row names, settings labels, a userMessage) is shown as you wrote it: read kino.lang, now "es-CO" or "en-US", to word it in the person's language.
  • Catalog-only plugins. With "catalogOnly": true the consent sheet adds "Solo catálogo: no reproduce videos", the title page's button reads "Buscar dónde verlo", and the plugin is never offered as a source of a title.
  • Music and podcasts (apiVersion 8, the contract): square covers in rows of their own, album and podcast pages with "Reproducir" and "Aleatorio", an audio player, a "Seguir escuchando" row for podcasts on Home, audio downloads and audio cast.
  • The title page is the same whatever order its sources answer. TMDB comes first for the synopsis, year, genres, score and runtime; your item and the new details export come before AniList and meta plugins for the synopsis and art.
  • A lighter copy after repeated stalls. When playback keeps stopping to load, the player can say the connection is slow and, once, move by itself to a clearly lighter copy among your alternatives when their labels name the resolution.
  • Finding plugins. "De la comunidad" lists 100 plugins a page, sorted by "Populares" or "Recientes", with "Cargar más" and "Buscar en GitHub" (Publishing).
  • CloudStream plugins. People can add a CloudStream repository and install its plugins through a separate complement app (CloudStream plugins).

From Kino 0.9.50

With nothing new in your manifest, except where said:

  • Play on the TV from the phone. With two paired devices, "Reproducir en el TV" works for a title of any plugin: the TV opens it with its own copy of the plugin. If the TV can't, the phone says why: "Instala el plugin <name> en el TV para verlo allí", "Activa …", "Configura …", "Actualiza …", "Reinstala …", "En el TV hay otro plugin con ese nombre; instala el mismo desde su repositorio", "Desbloquea el contenido 18+ en el TV para verlo allí" or, for a TV on an older Kino, "Actualiza Kino en el TV para verlo allí". So keep your id and your refs the same on every device.
  • New chapters of the series the person follows. Kino checks now and then (at most every 6 hours) the saved series of any usable plugin that declares episodes, calling your episodes(ref) with the saved ref, and adds the missing chapters. A failure leaves that series alone and moves on to the next. Keep your series refs stable.
  • "Para ti". A recommendation that comes from a plugin's catalog is saved by its ref: a movie as a movie, a series with its first season (calling episodes).
  • 18+ content. adult: true entries of an apiVersion 6 plugin show only with the 18+ code unlocked (18+ content).
  • Channels on Home. An apiVersion 6 plugin can put channels in its Home rows (Channels in your Home rows).
  • A section of its own in the TV sidebar or the phone's Inicio strip, and a group in Categorías, for a plugin that declares section or exports categories (Section, categories and colors).
  • Search inside a "Ver más" page. Every "Ver más" page has "Buscar en esta categoría" (scopedSearch).
  • Your own tab in Ajustes. A plugin with settings gets a tab named after it, with its form, status lines and buttons, painted in its theme colors (The settings form).
  • The Servidor menu. When a Stream has two or more copies, the player's "Audio y subtítulos" menu starts with a Servidor section listing them by label ("Opción 2", "Opción 3"… without one); the person switches and keeps watching from the same spot (Labelled and lazy copies).
  • Your own sentence on an error. A valid userMessage shows as "Mensaje de <name>: …" instead of Kino's line (Your own sentence).
  • Subtitles from your plugin. A plugin that exports subtitles is listed, under its name, in the player's "Buscar subtítulos en línea" for any title Kino knows by IMDb or TMDB id (Subtitles for any title).
  • Info pages filled by your plugin. A meta plugin fills what TMDB and AniList left empty on any title's info page (Describing other titles).
  • Hidden pages. A "browser" plugin's page is never on screen: the player shows its usual loading state while it runs (Hidden browser).
  • Updates. A badge on Ajustes ▸ Plugins counts the updates waiting for approval, and a failed call of a plugin with a pending update says so (Updates).
  • Community plugins. The section carries the note "Plugins de la comunidad — Kino no los revisa ni responde por su contenido.", and an installed plugin taken down from the index says "Retirado del índice de la comunidad." (Claims and plugin takedowns).

Plugins on the person's other devices

Kino keeps a person's plugins in step between their own devices (for example phone and TV): an install, a switch on or off, an uninstall, an approval or a saved setting on one device is sent to the others, and passwords travel encrypted end to end. Nothing in your plugin changes. What the other device does: it installs your plugin again from the same address, silently when what it fetches asks for nothing more than the person approved on the first one; if an update adds something (a host, a capability), it waits in "Plugins de tus otros aparatos" for the person to approve it there. So keep your repository public and your address stable.