Open-source presentation layer for production .NET MAUI apps
Build production MAUI screens without a framework tax.
UraniumUI fills the UI gaps plain MAUI leaves to every team: Material inputs, generated forms, validation mapping, data grids, tree views, tab views, dialogs, bottom sheets, backdrops, icons, blur effects, and app-ready presentation patterns without forcing a new architecture or coding style.
XAML, ContentPage, bindings, handlers, resources, and platform APIs stay available.
Forms, validation, dialogs, layouts, data views, page attachments, and stateful content.
Material controls, resources, icons, color tokens, overlays, blurs, and light/dark surfaces.
No black box
No Framework Tax.
UraniumUI is not a second framework on top of MAUI. It is a MAUI-native presentation layer that adds the screen pieces MAUI does not provide out of the box while leaving your app architecture alone.
Plain MAUI In, Better UI Out
Build with familiar XAML, ContentPage screens, bindings, styles, resources, handlers, dependency injection, and MVVM.
Use Your Architecture
No required base ViewModels, proprietary navigation model, custom application layer, or generated project structure.
Adopt Incrementally
Start with one control, add Material inputs, use DataGrid or TreeView, wire dialogs, or bring in AutoFormView where dynamic forms make sense.
Escape Hatches Stay Open
Drop down to MAUI APIs, handlers, platform code, resources, styles, or your own controls whenever a screen needs it.
Why UraniumUI
Stop rebuilding the same production UI foundation in every MAUI app.
Forms From Models
Generate editable forms from your models, map types to custom editors, localize display names, control layout, and reuse the same form infrastructure inside dialogs.
Validation Infrastructure
Use InputKit validations, DataAnnotations, async validators, and generated-field validation path mapping without hand-wiring every input.
Material Controls
Ship with text fields, editor fields, picker fields, autocomplete, buttons, chips, checkboxes, radio buttons, containers, dividers, and elevation.
Data and Navigation
Build data-heavy screens with DataGrid, auto columns, Paginator, TreeView, TabView, Select, Dropdown, CalendarView, templates, and selection APIs.
Dialogs and Surfaces
Use IDialogService, default modal pages, Mopups, CommunityToolkit, prompts, confirmations, progress dialogs, form dialogs, BottomSheet, and Backdrop.
Page Infrastructure
Build reusable presentation shells with UraniumContentPage, page attachments, stateful views, dynamic content, layouts, dropdowns, and expanders.
Theming, Icons, and Effects
Use color resources, style resources, cascading styling, custom themes, Material Symbols, Font Awesome, Fluent icons, and blur effects.
Templates and Web Components
Start from app templates, add UraniumContentPage item templates, and render syntax-highlighted code with WebView-backed CodeView.
One practical example
When the job is a form, one model can drive the UI.
Forms are one of UraniumUI's productivity wins: generate editors, display names, layouts, and validation messages from the same model. When the defaults are not enough, replace editor mappings or drop down to normal MAUI views.
Install what you need
Composable packages for app-level presentation.
Quick start
Create a new UraniumUI app.
Use the templates to start with UraniumUI, Material resources, icon options, dialog options, and optional blur support.
dotnet new install UraniumUI.Templates
dotnet new uraniumui-app -n MyMauiAppBuild MAUI screens from a stronger presentation layer.
Start with the guide, inspect the API, or join the community if you are evaluating UraniumUI for a production app or team codebase.