Write components once in C#. On the web they compile to JavaScript at build time, without WebAssembly. In a native app they render through Photon, eQuantic's own GPU engine on Metal and Vulkan.
Write components once in C#. On the web they compile to JavaScript at build time, without WebAssembly. In a native app they render through Photon, eQuantic's own GPU engine on Metal and Vulkan.
On the webJavaScript and atomic CSS, rendered on the server and hydrated in the browser
In a native appPhoton draws the same components on the GPU, through Metal and Vulkan
LIVE PREVIEW
3
WHY IT EXISTS
Three decisions the framework is built on
Written once, in C#One vocabulary of components that every target realises its own way: the DOM and CSS on the web, GPU pixels in a native app. No WebView, no Skia.
Typed styles, no CSS to writeColors, spacing and type are C# values. The web gets deduplicated atomic classes, and a native app paints the same values on the GPU.
Server Actions, type-safeMark a method [ServerAction] and call it from the client. Only marked methods can be reached, and one marked [Authorize] is checked before it runs.
Written once, in C#One vocabulary of components that every target realises its own way: the DOM and CSS on the web, GPU pixels in a native app. No WebView, no Skia.
Typed styles, no CSS to writeColors, spacing and type are C# values. The web gets deduplicated atomic classes, and a native app paints the same values on the GPU.
Server Actions, type-safeMark a method [ServerAction] and call it from the client. Only marked methods can be reached, and one marked [Authorize] is checked before it runs.
Written once, in C#One vocabulary of components that every target realises its own way: the DOM and CSS on the web, GPU pixels in a native app. No WebView, no Skia.
Typed styles, no CSS to writeColors, spacing and type are C# values. The web gets deduplicated atomic classes, and a native app paints the same values on the GPU.
Server Actions, type-safeMark a method [ServerAction] and call it from the client. Only marked methods can be reached, and one marked [Authorize] is checked before it runs.
WHY .NET TEAMS PICK ITOne stack, not twoMost .NET shops end up with a JS stack they barely maintain — one team in C#, another in TypeScript, two CI pipelines, two deploy stories. eQuantic.UI collapses that into the stack you already run.
One language, end-to-endThe model, the endpoint and the button that calls it are all C#, reviewed by the same people, in one repository.
Web and native, one codebaseThe same components open in a browser and in a native window, so the desktop and the phone need no second UI stack.
Tooling you already rundotnet watch reloads the page in place, source maps stop the debugger in the C# you wrote, and the build is the dotnet build your CI already runs.
Owned, not rentedMIT licensed, on NuGet and developed in public — and the site you are reading is built with it.
WHY .NET TEAMS PICK ITOne stack, not twoMost .NET shops end up with a JS stack they barely maintain — one team in C#, another in TypeScript, two CI pipelines, two deploy stories. eQuantic.UI collapses that into the stack you already run.
One language, end-to-endThe model, the endpoint and the button that calls it are all C#, reviewed by the same people, in one repository.
Web and native, one codebaseThe same components open in a browser and in a native window, so the desktop and the phone need no second UI stack.
Tooling you already rundotnet watch reloads the page in place, source maps stop the debugger in the C# you wrote, and the build is the dotnet build your CI already runs.
Owned, not rentedMIT licensed, on NuGet and developed in public — and the site you are reading is built with it.
FROM THE COMMUNITYWhat people are saying about it
“This initiative has a huge potential.”
WC
Willian CésarSoftware Engineer
“This initiative has a huge potential.”
WC
Willian CésarSoftware Engineer
One language, all the way down
The guides, the reference for every component and the quick start live on the framework's own site, and move with every release.