Desktop App

The Desktop App or Workbench is the name for the richer local surface beyond the web Playground.

This page is intentionally honest:

1. the direction is already clear
2. there is already substantial strategy and audit evidence around it
3. but the source package for this surface does not currently live in this workspace as a clean active app package alongside the docs site

How To Read This Surface

This surface is positioned as:

1. a richer local workbench
2. more UX-rich than the Playground
3. more appropriate for carrying a longer-lived preference system

If the Playground is the lightweight browser IDE, the Desktop App is the heavier and more personal local workbench.

Boundary With The Playground

The healthy difference to preserve is:

1. the Playground focuses on quick authoring and quick inspection
2. the Desktop App may carry richer state and preferences
3. the Playground does not need to copy the full UX model of the local workbench

Current Status

Based on the repo’s strategy and audit documents:

1. this surface is often referred to as the Flutter workbench
2. its direction and boundary have already been discussed substantially
3. there is audit evidence showing it is not merely an idea
4. but it is not yet present in this active workspace as a clean public app package

So this page is not yet a deep usage guide. It is an official documentation slot so the surface boundary is explicit from now on.

Why This Page Still Matters

Without this page, outside readers may wrongly conclude that:

1. the Playground is the only interactive surface
2. or that every richer workbench concern will simply be piled into the web Playground

That is not the healthy direction.

Documentation Status

Over time, this surface should ideally have documentation that lives closer to its active workbench repo or package.

For now, the website is only standardizing:

1. the role of this surface
2. its boundary relative to the Playground
3. its position in the wider RelGeo product architecture

Continue Reading

1. read Playground for the lightweight browser surface
2. read CLI for terminal automation
3. read Current Capabilities to see how this surface is positioned at the product level