Roadmap

What ArionUI does today, what is decided and coming, and what is not planned — no dates, one sentence each on why it matters.

Version 0.1.0-preview.1. The planned points come from the product plan of 4 October 2026: everything a complete desktop UI and the modernisation of WinForms and WPF apps still need will be built. When a point is built, it moves up into the first list.

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.
About a dozen drawn controls — button, text box, check box, switch, slider, drop-down button, label, panels — enough for simple forms.
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 and WPF as NuGet packages — one dotnet add package to try it.

Planned

The modernisation kit

Planned The WinForms host as a NuGet package — Without it, a WinForms team has to build ArionUI from source before it can try anything.
Planned A DataTable source and columns generated from a DataTable — Most old forms hold their data in a DataTable; today a grid sees a snapshot of it, not its inserts and deletes.
Planned BindingSource support, with its current position kept in step with the grid's current item — Forms built in the designer navigate through a BindingSource; keeping it means keeping the form's logic.
Planned Validation from IDataErrorInfo and INotifyDataErrorInfo as a ready edit policy — Error texts an application already produces should reach the grid without a second validation layer.
Planned A view-model bridge: INotifyPropertyChanged repaints a board on the UI thread — Today a view model tells the board by hand; MVVM code should not need that line.
Planned A theme derived from the system colours and the form's font — An ArionUI island in an old window should look like it belongs there, not like a different application.
Planned A WinForms sample: one form with a DataTable, before and after — A migration path is only believable when you can open both versions and compare them.

How the kit fits into a migration: Modernise a WinForms or WPF app.

Controls and surfaces

Planned Tab control — Almost every business form groups its fields on tabs.
Planned Radio buttons and option groups — An exclusive choice with arrow-key navigation and the right screen-reader role cannot be faked with check boxes.
Planned A combo box as a control: a value, type-ahead, editable — Today a drop-down button opens a menu; a form field needs a value it holds and a list you can type into.
Planned Multi-line text box — Notes, comments and addresses do not fit on one line.
Planned Numeric up-down and date picker as stand-alone controls — The grid already edits numbers, masks and dates in its cells; a form needs the same editors outside a grid.
Planned Menu bar, toolbar and context menus on controls — A menu exists as a pane the application opens itself; a window needs a menu bar at its top edge and context menus on any control.
Planned Draggable splitters, and docking later — Users resize the regions of a working window; today a layout has fixed edges and a centre.
Planned Image control — Logos, photos and icons are part of most screens; today they are drawn by hand in a drawing control.
Planned Tooltips on controls — A button with only an icon needs a tooltip to explain itself.
Planned A validation state on controls: an error text and an Invalid state for style sheets — A form has to show which field is wrong and why, in the theme's colours.
Planned Board layout persistence, and moving tiles with the mouse — A dashboard users arrange themselves should look the same at the next start.

What exists today instead: Controls.

Not on the roadmap yet

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

A native control inside a board tile — A tile shows what the engine draws; hosting a WinForms or WPF control inside one would leave the immediate-mode contract and the parity between the hosts. Old forms sit next to ArionUI, not inside it.
ActiveX for VB6, Delphi or Access — There is no ActiveX wrapper. A .NET host window could be reached from there, but that is a project of its own with an open outcome.
Linux and macOS — Avalonia runs there, but ArionUI is developed and tested on Windows only so far.
A visual designer — Boards, columns and style sheets are written in C#. What the cascade did is inspectable through Explain, but there is no drag-and-drop designer.
Multi-touch gestures — One finger works like a mouse; pinch and swipe are not built.
A mirrored right-to-left layout — Bidirectional text inside a cell works; the grid and the board always lay out left to right.
IME pre-edit — The candidate window sits at the caret, but text being composed is not shown inside the field.

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.