Skip to content

Avalonia UI Migration

mleem97 edited this page May 10, 2026 · 2 revisions

Avalonia UI Migration

This document tracks the migration from MAUI to Avalonia UI, which is now Complete.

Status: Complete

The project has successfully transitioned to Avalonia UI 11.2.

Key Achievements

  • Cross-Platform Parity: Full support for Windows and Linux.
  • Performance: Reduced startup time and memory footprint via .NET 9.
  • Design System: Fully implemented the "Terminal Core" design system.
  • New project: GregCore Modmanager.Avalonia
  • Custom chrome window (SystemDecorations=None, extended client area)
  • Terminal Core themed shell and compact upload-focused layout
  • Status row with Steam/GregAPI/Login text conventions

Goals

  • Build a production-ready Avalonia desktop client.
  • Preserve existing workflow behavior.
  • Improve UX density and scaling.

Next Steps

  1. Extract shared service interfaces from MAUI-specific code.
  2. Wire real session/Steam state into Avalonia view models.
  3. Port primary workflows:
    • Project browser
    • Mod upload editor
    • Workshop browser
  4. Add accessibility and keyboard navigation QA pass.

UX Scaling Rules

  • Use compact type sizes for metadata (10-12px).
  • Avoid oversized cards and empty whitespace.
  • Keep controls aligned to a strict grid.
  • Use high contrast in dark mode only.

Clone this wiki locally