Roadmap

Project Roadmap

Synchronized with ROADMAP.md in the main repo (the source of truth). This page lists what is ahead — what the product already does is documented on the product pages.

Web track

• Forms & validation engine (DataAnnotations-driven).
• Accessibility polish pass — focus trap, keyboard nav, aria details collected as fences across components.
• Global state + performance budgets.
• Real-time server push ([ServerEvent] over SignalR) — Server Actions are request/response today.
• Typed programmatic Navigator API for client-side navigation (the router itself is complete — link-driven).
• Statement-level source-map density — C# stack mapping is member-level today.

Native track (Photon)

• Image decode/upload — the remaining Texture consumer (Image renders its placeholder surface today).
• iOS and Android accessibility bridges (UIAccessibility / AccessibilityNodeInfo) — the semantics tree they consume is already target-neutral; macOS ships its bridge.

Component track

• ListView variable item extents (incremental measurement) — v1 is fixed-extent vertical.
• Spreadsheet: 2D scroll (wide sheets), formula engine, per-cell formatting, merges, frozen panes — all outside v1 scope.
• Inline marked-text rendering in code surfaces during IME composition.

Track I — Editor intelligence (CodeEditor)

The framework ships a real code editor — document model, selection, history, highlighting, bracket matching, find, squiggles — and it currently cannot help you write. The missing half is intelligence, and the piece that makes it possible is proven: Roslyn answers semantic completions over the same compilation the page builds (context. offers Theme; Col offers Column, because the using static surface is part of that compilation).

• I1 — the completion model in Primitives, beside CodeEditorController: items, selection, the span a commit replaces, open/filter/move/accept/dismiss. Write-once, testable headless.
• I2 — keys and the list in Components: the list is placed at the caret from the metrics the editor already computes (ContentTop, LineHeight, ContentLeft, ColumnWidth), the way the find bar already floats over the code.
• I3 — signature help: the parameter panel on (, on I1's plumbing and I2's placement.

The real problem is latency, not completions: fetch on a trigger (. or Ctrl+Space), filter locally while typing continues, cancel stale requests. Live diagnostics — squiggles as you type — are the same shape.

Track E — the "eQuantic UI" VS Code extension

A first-party visual editor on the SDK itself — live screen preview (the REAL web realizer in a webview), click-to-select in the viewer (stable layout paths + the V3 source maps eqc already emits), a property panel that edits the C# source through Roslyn rewrites, up to full visual editing. Milestones E1 (live preview) → E4 (full editing).

Standing directives

• Zero third-party dependencies wherever the platform provides the capability (system frameworks, embedded toolchains — the Bun/slangc model).
• Fail loudly: anything the SDK cannot faithfully realize is a build error, never silent divergence.
• Everything pinned: conformance differentially, styles by byte-identical cross-pins, pixels by goldens, hydration by class identity (e2e).