E004

Share Your MAUI Controls with NuGet

· 1:50

Discover the open-source .NET MAUI Controls Library and how NuGet, versioning, documentation, and reusable components simplify application development.

Share Your MAUI Controls with NuGet cover

PRESS PLAY. FIND AN IDEA.

Listen to the episode

Show Notes

Why write the same UI component over and over again?

Reusable controls can improve consistency, maintainability, and productivity across multiple .NET MAUI projects.

In this episode of the TSJDEV Apps Podcast, Thomas Sebastian Jensen introduces his open-source .NET MAUI Controls Library and explains why distributing reusable components through NuGet can simplify application development.

In this episode

  • Why reusable controls matter.
  • Introducing HyperlinkLabel, InitialsControl, RatingControl, and StaticChipControl.
  • Sharing custom controls through NuGet.
  • The importance of versioning, documentation, and clean component design.

Coming next

Building cross-platform desktop applications with Avalonia UI.

TSJDEV Apps Podcast - Short Episodes. Big Developer Ideas.

Full Transcript

You’ve built a useful UI control. It works perfectly. But now you need it in three different applications.

Do you copy the code three times?

Welcome to the TSJDEV Apps Podcast! Short Episodes. Big Developer Ideas.

I’m Thomas Sebastian Jensen, and today we’re talking about reusable controls and NuGet packages.

When developing .NET MAUI applications, you often encounter the same requirements.

Maybe you need a label that opens a website, an avatar displaying someone’s initials, or a simple star-rating component.

Of course, you could implement these controls separately in every project.

But that’s not particularly maintainable.

That’s why I created my own .NET MAUI Controls Library.

It includes several reusable components, such as HyperlinkLabel, InitialsControl, RatingControl, and StaticChipControl.

Instead of copying source files between applications, the controls are distributed through NuGet.

This means developers can install the package, register the library in their MAUI application, and start using the components directly in XAML.

But publishing a package introduces responsibilities.

You need meaningful version numbers, clear documentation, and a stable public API.

A reusable component should also work well with established patterns such as MVVM.

And whenever you improve a control, you can distribute that improvement through a new package version.

The real benefit isn’t just saving a few lines of code.

It’s creating a consistent, maintainable foundation for multiple applications.

So here’s my advice: if you’ve implemented the same component more than once, consider turning it into a reusable library.

But reusable components are only part of cross-platform development.

What if we want an entire desktop application running on Windows, macOS, and Linux?

Next time, we’ll explore Avalonia UI.

Stay curious, keep experimenting, and keep building!

Links & Resources