Plugins for Movian are written in ECMAScript.

*Starting from v4.9.401 Movian uses Duktape engine (http://duktape.org).

This document assumes the reader has some ECMAScript knowledge background. There are plenty of books and sites on learning the language itself so this guide is concentrated on the engine features.

Movian plugins do not interact directly to the user via the user interface (similar to a web browser) but rather respond to browse and search requests and populate the internal data model with information that is then presented to the user via Movian's user interface(s).

Structure of a plugin

Each plugin resides in a directory of it's own. This directory must contain a file plugin.json which contains information about the plugin. For more information about this file, please see the section named plugin.json below.

Apart for the plugin.json file there are no further restrictions of what the files are named in the plugin directory or if files are placed in sub-directories, etc


Is a JSON (http://www.json.org/) encoded text file containing information about the plugin. Example from the Headweb plugin:

  "type": "ecmascript",
  "apiversion": 1,
  "id": "headweb",
  "file": "headweb.js",
  "showtimeVersion": "4.1.22",
  "version": "1.5.3",
  "author": "Andreas Öman",
  "title": "Headweb",
  "icon": "headweb_square.png",
  "synopsis": "Headweb online video",
  "category": "video",
  "description": "<p>Headweb is a Swedish online video store.<p>For more information, visit <a href=\"http://www.headweb.com\">http://www.headweb.com</a>",

Description of fields and requirement of their presence:


Type of plugin, as described by the following list.

  • ecmascript - loads the plugin using Duktape.
  • views - used for user interface (screen keyboard plugin)

apiversion (OPTIONAL)

Only applicable if type is ecmascript, ie. when running using the Duktape engine. This controls the API exposed by Movian to the plugin.

  • 1 - The version 1 API is the default and is compatible with the API which was exposed through the old SpiderMonkey engine.
  • 2 - The version 2 API is a new API which more resembles modern ECMAScript using modules and CommonJS interfaces. Please try to use this.

The version 1 API is emulated using the version 2 API using a wrapper. The emulation code can be found here https://github.com/andoma/showtime/blob/master/resources/ecmascript/legacy/api-v1.js


Unique identifier for a plugin. The IDs are assigned by the Movian project. Any ID starting with the string "test" is reserved for development and can be used by plugin developers until a final ID has been assigned. The assigned IDs will be ASCII lowercase. To get an ID please mail


Name of the plugin executable/script. Usually it's a good idea to give the file a name resembling the plugin ID.


Short title of the Plugin. If omitted the 'id' field will be used instead which might look a bit bad due to lowercasing, etc

showtimeVersion (RECOMMENDED)

Minimum version required of Movian for this plugin to work. If the current version of Movian is less than this version the user won't be able to install the plugin but will be notified about what version of Movian is required. The same goes if a plugin is updated and the new version requires a newer version of Movian. Then the user will be refused to upgrade the plugin. If this field is omitted Movian will assume the plugin works on all versions of Movian.


Version of the plugin. If this does not match the current installed version of a user's plugin the user will be presented with the possibility to upgrade the plugin. If the field is omitted Movian will set the version to "Unknown"

category (RECOMMENDED)

Category of the plugin. If the field is omitted Movian will set the category to "Unknown". Following categories are known:
"tv" - online TV
"video" - streaming video
"music" - streaming music
"glwview" - UI extentions
"subtitles" - subtitles
"glwosk" - on screen keyboard

synopsis (RECOMMENDED)

A short one line summary of the plugin or the service it accesses

author (OPTIONAL)

Plugin developer. Any UTF-8 characters are valid.

homepage (RECOMMENDED)

An URI with the location of the plugin homepage


Path to plugin icon. The path is relative to the plugin root directory. If no icon is available Movian will use a placeholder image instead.

description (OPTIONAL)

Long RichText formatted (some HTML features are supported) description of the plugin.