learn-dotnet-maui: a curated index of .NET MAUI learning resources

A link directory, organised by the format you want to learn in

The learn-dotnet-maui repository describes itself as a repository filled with resources available to start learning or deepen your knowledge about .NET MAUI, and the key design decision is that the content is divided by type of content, so that video, blogs, sample code and the rest are separated, and you can find the content in the form you prefer.

That framing is the repository's whole contribution. Anyone learning a framework faces the same problem: the official documentation is thorough and is not how most people want to learn, the blog posts are scattered, the sample repositories are buried in search results, and the video courses cost time you have to spend. Collecting them in one place with the format as the primary axis saves an afternoon of searching.

The categories are the folders you see at the top level of the tree: Blogs, Books, Code, Services, Social Media, Videos and Other. Blogs covers the community blog sites, Books covers e-books written about .NET MAUI, Code covers notable project or sample repositories that can be used for reference, Services covers services you can use with a MAUI app such as analytics, crash reporting and distribution, Social Media collects the influencers related to MAUI, and Other holds what does not fit the rest, such as newsletters and podcasts.

The primary language of the repository is listed as unknown, which is the honest label for a folder of Markdown link lists.

The official Microsoft sources are kept separate from the community list

The repository lists four official links in a separate section, and the separation is deliberate rather than cosmetic.

The .NET MAUI GitHub repository at github.com/dotnet/maui is where the project is actively developed. The Microsoft Docs entry points at the official documentation, the Learn Path is an interactive course on Microsoft Learn with hands-on examples, and Learn Live is a set of 7 live streamed episodes for building a first MAUI app with James Montemagno and Matthew Soucoup.

Putting these first, and keeping them out of the community folders, tells a reader which sources are canonical. The community resources are a supplement to the official documentation, not a replacement for it, and the repository's own structure makes that hierarchy visible before you click anything.

The Learn Live series is worth calling out because it addresses a real gap. MAUI has a reputation for shifting under you, because it is the successor to Xamarin Forms, which is why the topic tags list both xamarin and xamarin-forms. A series with named presenters who are building in public is a different kind of artefact from a documentation page, and for a framework in that state of transition, watching the API being used is a reasonable way to keep up.

Working through the list: the official links first, then a folder

There is no install step and no command to copy for a repository of links, and the readme directs readers to the official documentation site at dot.net/maui for the framework itself. What a reader can copy verbatim is the set of official entry points the project lists:

* [.NET MAUI GitHub repository](https://github.com/dotnet/maui): the .NET MAUI GitHub repository where the project is actively developed.

A sensible first pass is to open the Microsoft Learn path from that list, because it is the only resource here described as interactive and it comes with hands-on examples. From there, pick one format folder rather than reading across all of them. The Videos folder for a visual route, Books for a systematic one, and Code when you want to read an application rather than a chapter.

The Code folder is the one to spend the most time in, because the sample repositories it points at are the only entries here that show a complete application rather than a fragment. The Services folder is the one to skim, since analytics, crash reporting and distribution are choices you make later, once the app works.

If you want to see the destination before you start, the built-with-maui repository linked from the tip gives you a list of applications to read in the other direction, from a shipped product back to the framework decisions it made.

The companion repository for real-world apps, and what it tells you

There is a tip in the readme pointing at a separate repository, built-with-maui, for anyone wondering what real-world apps are built with .NET MAUI.

That companion project changes how the learning list should be read. A curated list of tutorials and blog posts tells you how people teach the framework, but it does not tell you whether anyone ships with it. A list of real applications answers the second question, and it is the more useful one when you are deciding whether to invest a quarter in learning a framework.

Both repositories come from the same author, and both are MIT licensed. The learning resources repository is not archived, and the last push was on 2026-08-06. There are no GitHub releases, which is consistent with what the repository actually is: a set of text files that are edited and committed, not a versioned artefact that needs a release trail.

One disclaimer in the readme is worth repeating because it is easy to miss in a directory full of links: this repo and its resources are in no way affiliated with, or endorsed by, Microsoft. Given that the content is mostly links to Microsoft's own documentation and to community sites, someone could easily read the official links as an endorsement of the list. It is not one.

Contributing is a pull request, and there is no curation policy

The contribution model is stated in one line: if you know about a website or resource you do not see on here yet, feel free to open a PR. There is a PRs Welcome badge and an invitation to do so.

That openness is the right default for a list like this, and it also means the list carries no filtering criteria beyond the judgment of whoever submitted the link. The readme does not describe a policy for what qualifies, whether a resource is checked before being added, or whether entries are pruned when they go stale. The only stated structure is the folder taxonomy, and the only stated editorial rule is the type of content.

The practical consequence for a reader is that the quality signal comes from the folders and the submission history rather than from a stated policy. A Books folder with three entries in it is more useful than an Other folder with a hundred links, because the taxonomy is doing the work. The Social Media and Other folders, where the taxonomy necessarily has to stretch, are the ones to approach with more skepticism about signal.

The repository also carries a .github directory, a .gitattributes and a .gitignore, and an assets folder holding the decorative header image, which the readme credits to a specific free photo source, so the attribution practice in the readme is consistent with the file contents rather than bolted on.

What the list cannot tell you, and when it is the wrong tool

Two limitations are worth naming before anyone points a whole quarter of learning at this repository.

The first is that links rot. A directory of external URLs, some of them to personal blogs and YouTube channels, is a set of claims about the state of the world at the moment they were added. The repository gives no indication of when each entry was last verified, and the readme says nothing about a review cycle. There is no changelog either, and no releases to diff. For a framework that ships on a schedule, some fraction of a two-year-old list is going to describe an API that has since changed, and the list itself cannot tell you which fraction.

The second is that a link list is not a curriculum. It has no ordering, no difficulty progression, and no exercises. If you want to be a MAUI developer, this repository tells you the shape of the available resources and where to find them, and then you have to make the plan yourself, including the part that matters most, which is deciding which order to do it in and when to stop reading and start building.

So it is the wrong tool for a team onboarding a developer who needs a guided path with a mentor, and the wrong tool for anyone who wants a sample application to read end to end. The Code folder points at sample repositories that exist precisely to be read, and that is where the actual learning is. As a map of the ecosystem, though, it is exactly the thing that is otherwise scattered across a dozen tabs, and for a framework that is still finding its shape, having one maintained index of where the writing and the code live is worth the effort.

Editorial conclusion

learn-dotnet-maui fits a developer who is starting .NET MAUI and wants a map of where the community writes, records and shares code, and it does not fit a team looking for a tutorial series, a sample application or a maintained framework. Before treating it as a curriculum, open each linked category yourself and check that the entries still resolve and still match the current SDK, because the repository is an index of links and it does not restate what is in them.

Frequently asked questions

Official sources

1. Issues
2. jfversluis/learn-dotnet-maui on GitHub
3. License: MIT
4. Project website
5. README