Phase 3 — Unplanned and Additional

Phase 3 has no committed scope. It was originally reserved for a single question: does DataFlex need to look at native UI controls again? That option is still open — no decision has been made — but the market now largely builds half-web applications on Electron, and FlexTron is the DataFlex equivalent. Porting FlexTron looks like the stronger short-term bet, which is why native controls stay TBD rather than planned.

Beyond that, Phase 3 absorbs whatever is not directly involved in Phase 1 or Phase 2. If the Phase 2 development-environment question resolves in favour of VS Code, Studio remote development moves here as an additional item rather than disappearing.

Statuses mean exactly what they mean on the roadmap overview: ✓ released and usable · ◐ released, with the limitation named in the cell · ✗ still to be implemented · N/A not applicable to that platform · TBD not yet decided.

Components can ship between phases

A phase describes a full-fledged release, not a release train. TechStack's interop system, combined with the package manager introduced in DataFlex 26.0, lets components ship on their own schedule: FlexTron, the database drivers provided out of the box, and the Web UI server and client capabilities are all packages. Over time, more and more components will be released independently of one another. So an item documented under a later phase can become available earlier — FlexTron on Windows belongs to Phase 1 and FlexTron on the other platforms to Phase 2, but a cross-platform FlexTron package may well appear in between.

Candidates

Everything here is either undecided or waiting for a phase to claim it.

Feature	WebAssembly	Windows	macOS	Linux	Unix
Native UI controls	TBD	TBD	TBD	TBD	TBD
Studio remote development	TBD	TBD	TBD	TBD	TBD
SOAP web services	✗	✗	✗	✗	✗

Studio remote development also appears on Phase 2 — Cross-Platform Deployments: it lands there if the Studio route wins, and here if VS Code does.