Tagged
5 posts
I wanted MAUI in a browser without Blazor: real DOM elements, positioned by MAUI's own layout engine. So I built a backend for it. Then I pointed the Shiny Controls gallery at it, 68 pages of unchanged XAML, and nearly all of it just worked. Here is what does, what doesn't yet (MediaElement, SkiaSharp views) and how to try it.
Four Office editors, a free-form notebook, ribbons on everything, Find across all of them, presenting mode for decks, and a camera you call instead of a screen you build. All of it in the box, on .NET MAUI and Blazor, no WebViews.
A seekable keyframe engine for .NET MAUI with CSS @keyframes semantics in XAML, 42 motion icons compiled from one spec into a drawn scene on MAUI and real CSS keyframes on Blazor, and a ShinyButton that finally makes press-wait-see-if-it-worked a one-liner.
Sixty-odd controls, one token contract, two renderers, zero WebViews. Shiny Controls hits 1.0 for .NET MAUI and Blazor — and there is a live playground you can click through before you install anything.
Shiny Controls v1.0 ships with IFeedbackService — a single injectable service that every interactive control calls. Implement it once for haptic, TTS, sound effects, analytics, or any combination.
