Dartvel build targets: every platform and its status

dartvel build web
dartvel build android
dartvel build    # every target this machine can build
dartvel build linux --profile development

dartvel doctor
dartvel doctor --target tizen
dartvel build webos --auto-install

Tools Dartvel can fetch unattended install under ~/.dartvel/toolchains. It asks first, and installs without asking in CI.

Inside a project, doctor also checks the directories you configured as pagesDir, backendDir and modelsDir. A project that does not use one gets a [-] line, which is information and needs no fix. [!] is kept for something you have to fix.

[+] lib/pages exists
[-] lib/backend/functions not present (no backend functions)
[-] lib/models not present (no models)

Status: dartvel build webos skips: LG's CLI cannot resolve a Dartvel project. A package assembled in CI runs in a Wayland window under ARM emulation. Not run on a TV

A release build of android or fireos is signed with your own key. Without one the build stops before it starts and says how to set one up. It is never signed with the debug key.

# pubspec.yaml
dartvel:
  android:
    signing:
      keyProperties: ../secrets/key.properties   # kept out of the repository
    internet: true          # the default
    allowBackup: false      # the default
    cleartextHosts: [printer.local]   # plain HTTP only to these

keytool -genkeypair -v -keystore upload.jks -keyalg RSA -keysize 4096 -validity 10000 -alias upload
dartvel build android

The properties file holds storeFile, storePassword, keyAlias and keyPassword. storeFile is relative to the file.

In CI, set DARTVEL_ANDROID_KEYSTORE, DARTVEL_ANDROID_KEYSTORE_PASSWORD and DARTVEL_ANDROID_KEY_ALIAS instead.

Backup is off, including copying to a new phone. With allowBackup: true, the app's databases, its sign-in and its offline data still stay on the device.

Plain HTTP is refused except to the hosts you list. Debug builds can also reach your computer from the emulator.

Release builds keep the Java Dartvel calls by name, so shrinking the app does not break the camera or payments.

--arch picks arm, arm64 or x64 for embedded builds. It defaults to arm64, and to this machine's own for sony-elinux.

These names are accepted. Today they build the same bundle as sony-elinux, with no disk image.

Some targets are not officially supported by Flutter. They come with every Dartvel Cloud plan instead of the free install: Apple Vision Pro, Meta Quest, Chrome and Firefox extensions, VS Code extensions, Telegram Mini Apps, apps that run in a terminal, Fuchsia, and microcontrollers with no Linux such as the ESP32-S3, which need the app built entirely from Dartvel primitives. The runtimes behind them (the Telegram host, the XR runtime behind DV.Window, the terminal surface and the browser-extension runtime) come with the same plans, as the dartvel_runtimes_pro package that plugs into extension points in the free framework. Every free target runs without it.

dartvel build visionos --cloud   # build it on Dartvel Cloud
dartvel targets add pro          # or add the package and build here
dartvel targets                  # what this install can build

Without a plan, dartvel build visionos says which plan includes it and stops. Nothing is built or sent.

The package adds build steps only. Nothing from it, and no licence key, ends up in your app.

Dartvel 0.11.5 and earlier built these targets in the open, and those releases stay MIT licensed.

The way a paid target plugs in is public. Any package can add a build target the same way: see the CLI README.

Every TV, embedded, extension and terminal target runs on an embedder somebody else wrote. Dartvel keeps a fork of each so it can pin, patch and track it against the Flutter version Dartvel ships. Each fork keeps upstream's licence and docs untouched below a banner that says what changed.

What the fork adds: Tracks upstream's pin of Flutter 3.44.4. One patch: it stages the Flutter engine and assets into a native TPK, which Tizen SDK CLI 10.x left out.

What the fork adds: Records the pin at Flutter 3.29.3, the newest engine Sony publishes. dartvel build sony-elinux assembles its bundle from Sony's embedder artifacts.

What the fork adds: Records the pin at Flutter 3.38.10. Its Dart 3.10.9 is below Dartvel's floor, so dartvel build webos skips; CI assembles a package from LG's engine instead.

What the fork adds: Adds a Bazel rule and a script that package any Flutter app, and a build-only bootstrap. Blocked today: the Flutter it bundles is too old to resolve a Dartvel project.

What the fork adds: Points the generated extension at the file tsc writes. dartvel build vscode runs upstream's own scaffold and build steps.

What the fork adds: Re-pins to Flutter 3.44.5 and adds dartvel-cli-flt, which bundles an app so it can leave the machine. Upstream is a research project that runs apps in development.

What the fork adds: Targets Dart 3.12 and Flutter 3.44 and keeps the package name, so a project swaps the dependency and its imports resolve unchanged. Upstream's 2,918 tests run unchanged in CI. DVBox and DVText do not use mix.

Thank you to the maintainers of these projects at Samsung, Sony, LG, the Fuchsia team, FlutterTV, Bitwild, and to SlowGen and Jia Hao. Dartvel's TV, embedded and terminal targets exist because they did the hard part first.

GETTING STARTED

APP

DATA

BACKEND

OPERATIONS

SHIPPING

REFERENCE

Build targets

Build with one command

Check tools before you build

Every target and its status

Android release builds

TVs and embedded devices use vendor embedders

Paid targets

Upstream embedders and credits

Also built on