XAML.io v0.8 — Quotes
All quotes attributable to Giovanni Albani, CEO of Userware, unless noted.
Embargoed until Monday, July 6, 2026.

--- Headline quote ---
"WPF isn't going anywhere on the desktop. But a lot of these apps now need to live
on the web too. That means reachable from any device, centrally updated, and running
inside the browser's security sandbox instead of with full access to each user's
machine, with the accessibility and auditability the desktop never gave them. What's
always made that painful is that it meant a rewrite, and that's exactly what we remove.
We keep your original C# and XAML and make the framework support what your app already
does, so you avoid regressions and keep a codebase your team still understands."

--- On migration being a real project (Darshin Vyas, VP of Sales, Userware) ---
"For a serious application, the honest answer is that the migration is a project, and
that's exactly what we do. It starts with a free compatibility analysis and a fixed-cost
quote. We deliver in milestones you can compile and test, and your team can keep working
the whole time. We've done this for more than thirteen years, on over ten million lines
of enterprise code."

--- On why move a desktop app to the web at all ---
"Most teams aren't moving these apps to the web for novelty. They're moving them because
the business needs the app on any device, behind central one-click updates, inside the
browser's security sandbox rather than with full access to each PC, with the accessibility
and auditability the Windows desktop never gave them."

--- On the AI-rewrite trend ---
"The instinct today is to let AI rewrite a legacy app. For a working business app, that's
a brand-new app you have to re-test and re-trust. We'd rather keep your code and change
where it runs."

--- On the value of existing code ---
"A working WPF app is an asset, not a liability. We help companies bring it to the web and
keep it, instead of throwing it away in a rewrite."

--- On what has changed ---
"For years, the only way to get a WPF app onto the web was to rewrite it in something else.
That's the assumption we're ending."

--- Short pull-quote ---
"The web shouldn't cost you a rewrite: keep your WPF code, and change where it runs."
