Curated tool

Avalonia

Draft entry. Basic layout pass before the full writeup.

Why I needed it

I needed a desktop stack that works on Fedora and still lets me ship to Windows without splitting the codebase.

Setup notes

Current use is tied to Rivet Core development and local Linux workflow.

Mental model

Build one practical desktop app flow, then package per target platform.

Friction points

WebView and embed behavior differences still show up depending on host/runtime.

What worked

Fast enough development loop with a clear path to cross-platform desktop output.

What did not

Platform-specific edges still need handling when app behavior expects tighter native integration.

README assumptions

This entry will be expanded with packaging notes and real tradeoffs in the next pass.