Roadmap

What ArionUI works on now, what comes next and what comes later, then what it does today and what is not planned. An order, not dates; one sentence each on why it matters.

Version 0.1.0-preview.2, an early preview. The plan below is ordered: the points under Now are in progress, Next follows, Later after that. Feedback on the preview can change the order.

Now

Next

Later

Built

Grid and views Core

  • Table, card board and tree views over the same data, switchable at run time — one engine instead of three controls.
  • Sorting, filter row, value filters, search, editing, undo and redo — what a data grid is expected to do, without per-row controls.
  • Live and server-side sources — keyed feeds, bounded logs, paged and virtual sources keep large and moving data cheap.
  • Screen readers on all three hosts — tested with Narrator and NVDA, because internal software has users who need them.
  • Shaped and bidirectional text in cells — CJK, Arabic, Indic scripts and emoji render correctly.

Board & Styling Preview

  • Board with tracks, auto-fit, spans, breakpoints, scroll or fit, nesting and feeds — the layout grid for whole windows.
  • Style sheets with selectors, a cascade, theme tokens, transitions and Explain — web-style theming that the compiler checks.
  • Drawn controls for business forms — buttons, text boxes, tabs, radio groups, combo boxes, numeric and date fields, menus, toolbars, images, tooltips and a validation state.
  • Any view as a tile — a full grid, chart or 3D scene on a dashboard, not a picture of one.
  • ArionControlSurface on Avalonia, WPF and WinForms — drawn controls in an existing window, one panel at a time.

Pro modules Pro

  • Grouping and pivot — the questions a table alone cannot answer.
  • Charts and 3D charts on the GPU — the same data as a picture, in the same engine and selection.
  • Timeline and planning matrix — resources over time, plans as ordinary columns.
  • Conditional formatting, layout persistence, export — rules users edit, layouts that come back, CSV, XLSX and PDF.

Hosts and rendering Core

  • One Skia renderer behind Avalonia, WPF and WinForms — the hosts draw the same frame instead of three parallel implementations.
  • GPU by default, CPU fallback — machines without a usable GPU still get a working grid that repaints only the newly scrolled strip.
  • Avalonia, WPF and WinForms as NuGet packages — one dotnet add package to try it.

Recently built

The points of the plan of 4 October 2026, built since, and what followed them before the first preview. Each is described on its documentation page.

The modernisation kit

How the kit fits into a migration: Modernise a WinForms or WPF app. All of it is Core.

Controls, board and styling

In the documentation: Controls, Board, Styling. Controls, splitters, moving and docking tiles and split areas are Core; saving a board layout uses the Pro package ArionUI.Layout, and charts in tiles are Pro modules.

Not on the roadmap yet

Limits that stay, stated so nobody plans around them by mistake.

The current answer is always the repository, with its README and open issues: github.com/ArionUI/ArionUI. If something here matters to you, open an issue — it helps decide what comes first.

Get release news

One e-mail per new version, nothing else, never passed on. Every e-mail has a link that unsubscribes you.

Interested in (optional)

We first send a confirmation link. Every e-mail has an unsubscribe link. Privacy