Skip to content

Status and roadmap

Tessel is at version 0.23. It’s young: the core of the language and its UI toolkit work, and they’re enough to write real apps (the Tessel IDE is one), but plenty is missing, and details of the language may still change. This page is an honest list of where things stand.

Tessel is developed with the help of an AI coding assistant, which is why its first releases came so quickly. The dates on What’s new are the real ones.

  • The language: structs and enums (with methods), functions and closures, lists and dictionaries, optionals, if, for and match, and value semantics with copy-on-write. Programs made of several files.
  • The compiler: type checking with clear error messages, and native code through LLVM. Built apps are single executables that need nothing else installed.
  • Platforms: macOS (11 and later), Windows and Linux (x86-64 and ARM64; Tessel itself on glibc 2.34 and later, the apps it builds from 2.28). All three are built and tested before every release, and each builds apps for the others (--windows on a Mac, --linux anywhere). Apps can also be built for Android (11 and later), which is newer and has so far been tried only on an emulator; there an app can read the phone’s location, satellites and compass. There’s no iOS support yet.
  • UI: windows, HiDPI screens, state and bind, stacks, Scroll, Text (selectable, or cut short), Button, TextField, SearchField, Link, Toggle, Picker (segments or radio buttons), TabView, grids, scrolling either or both ways (and from code), split views, a rich text editor, tables with cells edited in place, views turned and scaled, a dropdown picker, sound and video, web pages, notifications, a tray icon, full screen, files dragged out of the app, CodeEditor with syntax colors, Table and Tree, Divider, over 100 built-in icons, SVG, PNG and JPEG pictures, text written in Markdown, keyboard shortcuts, hover and pressed states, and the layout and styling modifiers. Every control works from the keyboard, and screen readers are told what’s in a window. Drawing of your own in a Canvas (shapes, paths, text and pictures), the mouse in full with .onPointer (every button, moves, the wheel, pinches), keys with .onKey, tooltips, pointers, files dropped on the window, and drawings saved as pictures. Solid shapes in three dimensions in a Scene3D, with a camera and lights, drawn by the graphics card. Ribbons of tabs and groups of commands. Context menus, popovers, the menu bar (the system’s on macOS, drawn in the window elsewhere), more than one window, files opened with the app from Finder, and asking before the app closes.
  • Looks: light and dark appearance that follows the system, colors of your own, and animation of views that move, resize, appear or disappear, with springs.
  • Text editing: selecting with the mouse and keyboard, word and line movement, copy, cut, paste, undo and redo, Tab between fields, and input methods (Chinese, Japanese, Korean, accents with dead keys).
  • Background work: timers (after and every), HTTP requests, downloads and WebSockets, TCP and UDP sockets and an HTTP server (sockets), running other programs, and heavy computations on another thread (background), all with completion blocks that run on the UI thread. They work in programs with only fn main too.
  • Language: structs, enums with values, interfaces, generics, closures, functions that take any number of values, optionals, errors with Result and try, tuples and sets, for and while loops with break and continue, and programs split over any number of files, with modules (import, public, private) for code shared between programs.
  • Standard library: files and folders, JSON and binary encoding of your own types, Data for raw bytes (with the numbers that binary files hold, and compression), dates and times with time zones and calendar arithmetic, random numbers, the clipboard, reading standard input and writing to standard error, and many methods for strings, numbers and lists.
  • Tools: the tessel command, tests written next to the code (tessel test), libraries to publish and use (tessel add, tessel publish), a REPL (tessel repl), hot reload (tessel run --hot, and “Reload on save” in the IDE), the Tessel IDE (with this documentation built in, a Design panel for building a window by pointing at it, and a preview for Markdown files), a VS Code extension, a language server for other editors, a debugger in the IDE, VS Code and the terminal, app bundles on macOS, and a headless mode for testing apps and taking screenshots.
  • Debugging: the debugger stops at lines, steps and shows variables, but can’t change a value, work out an expression, or stop on a condition, and doesn’t reach apps on Android.
  • Accessibility: apps tell screen readers what’s in their windows on macOS, Windows and Linux, but text can’t be read or edited piece by piece through one, menus drawn in the window aren’t described, and it hasn’t been tried with Narrator on Windows. Not on Android yet.
  • Packaging: tessel build --bundle makes a .app on macOS and an installer (Name Setup.exe) for Windows, with your icon.png as their icon, but apps aren’t code signed, and there are no disk images (.dmg) for macOS.
  • Editor support: the language server doesn’t format code, and the Tessel IDE itself doesn’t have go-to-definition or rename yet (VS Code and other editors do, through the language server).
  • Installation: packages exist for Apple silicon Macs and 64-bit Windows only (no Intel Macs yet). The macOS package is signed and notarized; the Windows one isn’t signed yet, so Windows SmartScreen may warn about a downloaded tessel.exe.

These are the next areas of work. None of them has a date.

AreaPlans
App polishFuller accessibility: reading and editing text through a screen reader, and Android.
Standard libraryFilling gaps as apps need them.
PackagingCode signing and installers.
DebuggingChanging values and conditions on breakpoints in the debugger.

Tessel’s goals and the reasons for its design are on Tessel’s design.