DEVELOPMENT / CLI

Dowe Dev

Compile the current project, start the targets you choose, and keep development artifacts inside the disposable .dowe directory.

Open Deploy docs

ONE DEVELOPMENT ENTRYPOINT

Start the project from its root

Run Dowe from the directory that contains main.dowe. In a terminal, dowe dev opens the target selector; explicit flags make the same workflow deterministic for scripts and CI.

dowe
dowe dev
dowe dev --target server --target web
dowe dev --target desktop
dowe dev --target android
dowe dev --target ios

INTERACTIVE

Choose targets once

The checkbox menu filters targets from main.dowe and the current host, then remembers the confirmed selection in .dowe/dev/target-selection.json.

AUTOMATION

Use explicit flags

Each --target is validated before compilation. Explicit runs do not read or write the interactive preference file.

HOST FILTERING

Keep unavailable targets out

Server and web run on supported desktop hosts. iOS is available only on macOS, while mobile and desktop launchers require their native toolchains.

TARGET PIPELINE

One source model, several targets

The shared Dowe compiler reads the project model once and prepares the selected target pipelines. A fullstack project commonly starts the server and web targets together.

SERVER + WEB

Fast fullstack feedback

The server target starts the Dowe-owned backend. The web target serves generated HTML, CSS, JavaScript, route chunks, fonts, and development reload support.

DESKTOP + MOBILE

Native previews from the same views

Desktop reuses the generated web/static output and the platform window system. Android and iOS use their native hosts while preserving the shared Dowe view model.

DISPOSABLE DEVELOPMENT OUTPUT

Inspect generated support without owning it

Dowe writes generated development output below .dowe, including target manifests, route data, fonts, icon copies, and type-checking support. Keep project source in main.dowe, theme.dowe, views, and server; do not edit generated files.

dowe
.dowe/
  dev/
  apps/
  fonts/
  icons/
  types/
  tsconfig.json

Dowe does not require Node.js, node_modules, Tailwind, or a JavaScript application runtime to compile source or run the Dowe-owned development server.

WATCH AND RELOAD

Keep the session open while source changes

The development session watches project inputs, runs the shared rebuild pipeline, and reports successful or failed rebuilds. Web changes reload the browser; server changes restart the backend when the new build succeeds.

Source of truth

Edit Dowe Source Format and configuration at the project root. Generated artifacts remain disposable and reproducible.

Recoverable rebuilds

A failed rebuild reports diagnostics and keeps the development session available for the next correction.

Read Agent docs