Put your content on every screen with a single code

TEVIX is an app for Smart TVs, phones and computers that becomes your company's app. You don't need to publish anything in the app stores: your audience installs TEVIX, enters your code, and from then on the device always opens straight into your content, with your name, your color and your logo.

In 3 steps

Choose your source type

The "source" is where TEVIX fetches your content from. There are three types. Start with the simplest one for your case; you can switch later without changing your code.

Website or web player

Enter the full URL. The device opens that page full screen inside TEVIX. It works for any website, but to look good on TV the site needs to support arrow-key and OK navigation (visible focus on buttons). If it already works in the TV's browser, it will work here.

Compatible format (start.json)

If you already have a start.json published for another TV application, register its URL (for example https://yoursite.com/app/start.json). TEVIX understands:

• parameter with menu:, content: and redirect:; the {PREFIX} and {SERVER} placeholders are filled with the protocol and host of your start.json.
• Menu (headline, menu[] with label, icon, data as a URL or object, execute, focus).
• Content in pages[].items[] with layout on the 12×6 grid (or 16×8 with compress), as well as template + items with {context:...} and action: "video:data".
• Item types default, separate, teaser, button, space; fields title, titleHeader, titleFooter, label, image, icon, action, execute, focus.
• Actions video:, audio:, link:, link:window:, content:, info:, reload:, back: and multiple actions [a|b].

Not yet supported in this format: plugins (video:plugin:, audio:plugin:), panel:, request:interaction: and extended properties. These items show a notice instead of breaking.

TEVIX format

This is the most complete format, and a simple one too: a main file (tevix.json) with your identity and menu, plus one file per page. Details below.

tevix.json: identity and menu

{
  "tevix": "1.0",
  "app": {
    "name": "Portal Cidade",
    "tagline": "News and Radio 98.7",
    "short": "PC",
    "color": "#E8452C",
    "logo": "logo.png"
  },
  "menu": [
    { "id": "inicio",   "label": "Home",   "icon": "home",  "content": "inicio.json" },
    { "id": "aovivo",   "label": "Live",   "icon": "live",  "content": "aovivo.json" },
    { "id": "noticias", "label": "News",   "icon": "news",  "content": "noticias.json" },
    { "id": "radio",    "label": "Radio",  "icon": "radio", "content": "radio.json" }
  ],
  "player": {
    "type": "audio",
    "title": "Radio Cidade 98.7 FM",
    "subtitle": "Live",
    "url": "https://stream.suaradio.com.br/live.mp3"
  }
}

Pages and blocks

Each menu item points to a page file. A page has a title and a list of blocks, from top to bottom.

{
  "title": "Home",
  "meta": "Updated 4 min ago",
  "blocks": [
    { "type": "hero", "items": [ "1 large featured item + up to 2 on the side" ] },
    { "type": "row",  "title": "Latest videos", "items": [ "horizontal carousel" ] },
    { "type": "grid", "title": "News",          "items": [ "grid of cards" ] },
    { "type": "list", "title": "Most read",     "items": [ "numbered text-only list" ] }
  ]
}

Items

{
  "k": "Sports",
  "title": "Cidade FC wins and takes the lead",
  "desc": "A goal in the 88th minute secured the win.",
  "time": "1 h ago",
  "image": "https://seusite.com/img/futebol.jpg",
  "action": "text:materia/1235.json"
}

Actions

URLs can be relative to the file they appear in (materia/1235.json, ../videos/x.mp4). An item without an action is informational only.

Plugins: dynamic content from your server

Static JSON files cover most apps. When the content needs real-time logic (a schedule that changes, a player with login, live progress, a per-user catalog), use a TEVIX plugin: an HTML page of yours that runs hidden inside the app and talks to it. The app asks the plugin for content, the plugin answers with the same page JSON you already know and, whenever you want, updates items on screen, opens a video, shows a panel or reacts to what the user does.

1. The plugin page

Create an HTML file (e.g. https://seusite.com/tevix/plugin.html) that loads the library and registers a handler. The page has no interface: it only answers the app.

<!DOCTYPE html>
<html><head><meta charset="utf-8">
<script src="https://tevix.app/js/tevix-plugin.js"></script>
</head><body><script>
TevixPlugin.setupHandler({
  init: function (info) {
    // info.app {name,color,logo}, info.code, info.lang ("pt"|"en"|"es"), info.device.id, info.tevix
  },
  ready: function () {
    // connection ready: you can start timers here (e.g. update items every second)
  },
  handleRequest: function (id, data, reply) {
    // the app asks for content. "init" is the default request when the plugin page opens.
    if (id === "init") reply({
      headline: "On air",
      pages: [{ items: [
        { id: "agora", layout: "0,0,8,2", titleHeader: "Now", title: "Morning News", progress: 0.4, action: "video:plugin:aovivo" },
        { layout: "8,0,4,2", type: "button", icon: "list", label: "Schedule", action: "content:plugin:grade" }
      ]}]
    });
    else if (id === "aovivo") reply({ url: "https://cdn.seusite.com/live.m3u8", title: "Live" });
    else if (id === "grade") reply({ headline: "Schedule", pages: [ /* ... */ ] });
    else reply({ error: "unknown request: " + id });
  },
  handleData: function (data) {
    // came from a "plugin:commit:SOMETHING" action (string)
  },
  handleEvent: function (name, data) {
    // "player:play", "player:time" {position,duration}, "player:ended", "player:closed", "content:shown", "focus" {id}, "back", "visibility"
  }
});
</script></body></html>

reply() accepts a page JSON (pages/template+items or blocks), an { "action": "video:..." } object to just run an action, or { "error": "message" }. It can also return a Promise. If the plugin does not answer within 20 seconds, the app shows an error with a Try again button.

2. Connecting the plugin to the app

In tevix.json, a menu item can point to the plugin instead of a page file:

{
  "app": { "name": "City TV", "color": "#E8452C" },
  "menu": [
    { "label": "Live", "icon": "live", "plugin": "https://seusite.com/tevix/plugin.html" },
    { "label": "News", "icon": "news", "content": "noticias.json" }
  ]
}

If the whole app is the plugin, use "plugin": "URL" directly at the root of tevix.json (no menu): the app opens without a sidebar. By default the app requests the init content; change it with "request": "other-id". Inside any page, static or coming from the plugin, use the actions in the table below. The plugin stays loaded while the app is open, even when switching pages; loading a plugin from another URL unloads the previous one.

3. What the plugin can do in the app

All through the TevixPlugin library:

4. Events the app sends

They arrive in handleEvent(name, data):

5. Extra page and item properties

Articles (text)

{
  "k": "City",
  "title": "City Hall announces new bus line",
  "subtitle": "Service starts on Monday with 12 vehicles.",
  "date": "November 2, 2026",
  "author": "Newsroom",
  "image": "https://seusite.com/img/onibus.jpg",
  "body": [
    "First paragraph.",
    "Second paragraph."
  ]
}

Each entry in body becomes a paragraph. Plain text, no HTML. The reading view uses large type, comfortable from 3 meters away from the TV.

Persistent radio

With the player field in tevix.json, the app shows an always-visible radio bar. Listeners browse the news while they listen. Any item with audio: also plays in that bar. Use a direct stream (.mp3 or .aac), not a player page.

Menu icons

home live news video radio play movie tv music settings info link web star search list. Material Design icon names (play-circle-outline, live-tv, ondemand-video…) are converted automatically; unknown names become a dot.

Complete example to copy

The "Portal Cidade" demo app is published and can serve as a template. Download the files, replace the text, images and URLs, and publish them on your server:

• tevix.json (identity, menu and radio)
• inicio.json (hero, carousel and list), noticias.json (grid), radio.json (audio and content:)
• materia/1234.json (article)

To see it in the app: open TEVIX and enter 8CR-EEC.

Hosting and CORS

The JSON files live on your server, on any hosting that serves static files. The device fetches them directly from there, so two things are mandatory:

1. Enable CORS: the server must respond with the Access-Control-Allow-Origin: * header on the JSON files (and on images, if you wish).
2. HTTPS whenever possible. Free certificates (Let's Encrypt) do the job.

location ~* \.json$ {
    add_header Access-Control-Allow-Origin * always;
    add_header Cache-Control "public, max-age=300";
}

<FilesMatch "\.json$">
    Header set Access-Control-Allow-Origin "*"
    Header set Cache-Control "public, max-age=300"
</FilesMatch>

Generate the files automatically

You don't need to write JSON by hand. Anything that produces a text file will do:

• WordPress site / RSS: a script (PHP, Python, Node) reads the RSS feed and writes inicio.json and noticias.json every 5 minutes. Headline → title, summary → desc, featured image → image, article link → generate a materia/ID.json with the text.
• Radio: a fixed radio.json with the stream and the schedule; change the player's subtitle to the current show.
• Videos: the YouTube API or your CDN lists the latest videos; use video: with the direct MP4/HLS. YouTube pages do not play inside the app; the media file is required.

Test your app

1. Open TEVIX in the browser (or on the TV) and enter your code. In the partner area there is a Test my app now button that signs in with your code automatically.
2. Navigate with the keyboard arrows (or the remote) and OK/Enter. Back: Backspace or Esc.
3. Changed a JSON file? Go to Settings → Clear cache and reload inside the app.
4. The "Could not load this page" error shows the URL and the reason (404, CORS, invalid JSON). Validate your JSON with an online validator before publishing.
5. In Settings → Check code now the app queries the TEVIX server immediately (useful right after renewing your plan).

Tips for looking good on TV

• 16:9, lightweight images (JPG up to 150 KB). No small text inside the image.
• Short titles. On TV, text is read from 3 meters away.
• Up to 8 menu items. Start with what your audience uses most (Live, Home).
• For live streams, use HLS (.m3u8) with 2 or 3 quality levels. Progressive MP4 is fine for short videos.
• If you use the Website type, make sure the site has visible focus and works with Tab/arrow keys; without a mouse, the user only has the remote.

Plans, trial and expiration

To subscribe or renew, use the contact shown in the partner area. The code always stays the same: your audience doesn't need to enter anything again.

Partner area

At /parceiro you sign in with your code and the password you chose at sign-up. There you can:

• See your plan status, its validity and how many devices used the app in the last 7 days.
• Change the content URL, name, color and logo. Devices update the next time they open.
• Copy ready-made instructions to share with your audience.
• Test the app with one click and change your password.

Frequently asked questions