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
- Now Finish touch — One finger works like a mouse today; touch screens and tablets need the gestures that go with them.
- Now A smoother picture on monitors with an odd refresh rate — Frames should arrive evenly on every display, not only on one that runs at 60 Hz.
Next
- Next More performance for live data and large selections — Fast-moving values and selections over many rows should stay as cheap as scrolling.
- Next Accessibility across all hosts — Screen readers work on all three hosts; the remaining gaps on Avalonia should close, so that every host offers the same.
Later
- Later More charts — More chart types and options, drawn by the same engine as the grid.
- Later More export and print options — CSV, XLSX, PDF and printing exist; more control over what goes onto paper and into files.
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 packageto 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
- Built The WinForms host as a NuGet package — A WinForms team adds one package and tries ArionUI in its own form, without building anything from source.
- Built DataTable and DataView as live sources, columns generated from the table — Most old forms hold their data in a DataTable; the grid sees its inserts, deletes and edits and types its columns from the schema.
- Built BindingSource support, with its position kept in step with the grid's current row — Forms built in the designer navigate through a BindingSource; text boxes and navigators bound to it keep working next to the grid.
- Built Validation from the DataTable, IDataErrorInfo and INotifyDataErrorInfo as a ready edit policy — Rules an application already has refuse or mark a wrong value in the grid, without a second validation layer.
- Built View-model binding for board controls — board.Bind(viewModel, x => x.Property): a PropertyChanged on any thread repaints only what changed, on the UI thread.
- Built A theme from the system colours and the form's font, and one that follows Windows — An ArionUI island in an old window looks like it belongs there, high-contrast schemes included.
- Built Lists of objects as a WinForms DataSource: BindingList<T> and List<T>, directly or through a BindingSource — Forms that bind business objects instead of a DataTable swap the grid the same way; a BindingList reports its changes by itself.
- Built A WinForms sample: one form with a DataTable, from before to after in three steps — A migration path is believable when you can open every step and compare.
How the kit fits into a migration: Modernise a WinForms or WPF app. All of it is Core.
Controls, board and styling
- Built Tab control — Almost every business form groups its fields on tabs.
- Built Radio buttons and option groups — An exclusive choice with arrow keys and the right screen-reader role, not faked with check boxes.
- Built A combo box: a value with type-ahead, or free text with suggestions — A form field needs a value it holds and a list you can type into.
- Built Multi-line text box — Notes, comments and addresses do not fit on one line.
- Built Numeric up-down and date picker — The editors the grid has in its cells, now as form fields, with formats and masks from the culture.
- Built Menu bar, toolbar and context menus on controls — A window needs a menu bar at its top edge, with F10 and access keys, and a context menu on any control.
- Built Image control — Logos, photos and icons, decoded once instead of on every frame.
- Built Tooltips on controls — A button with only an icon needs a tooltip to explain itself.
- Built A validation state on controls: an error text and an Invalid state for style sheets — A form shows which field is wrong and why, in the theme's colours, and a screen reader hears it.
- Built Draggable splitters between board tracks — Users resize the regions of a working window; a double-click gives a track its size back, Ctrl+Z takes a drag back.
- Built Moving tiles with the mouse, and saving the board layout — A dashboard users arrange themselves looks the same at the next start.
- Built Docking tiles beside another tile or at the board's edge — Users build their own working window by dragging a panel where they want it, with a preview of the area it gets, Esc to cancel and Ctrl+Z to take it back.
- Built Split areas with tab groups, as in an IDE — A board divided like Visual Studio's windows: panels share an area as tabs, switched with Ctrl+Tab, and a saved layout (Pro) keeps the tree.
- Built Charts in tiles that stay cheap under load — A hover over a chart draws a stamp instead of repainting the chart, and a scroll draws only the newly shown strip, with dozens of live charts on one board.
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.
- 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.
- Floating panels — Tiles dock inside their board and window; a panel torn out into a window of its own is not built.
- 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.
- 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.
Get release news
One e-mail per new version, nothing else, never passed on. Every e-mail has a link that unsubscribes you.