Just wanted to know if anyone purchased the commercial license for the PRISM library (https://prismlibrary.com/#pricing) and is using it in their MAUI project?
Just wanted to know the feedback, and should we also go for it or should we use the inbuilt navigation? or prefer some other library (open source)
Hello there,
An amateur here. I started building a mobile app that will me on my daily job. Nothing fancy just a simple database that will help me track down few things.
I studied ASP. NET Core MVC 2 years ago in a night school but nothing big. I decided to go for MAUI-Blazor hybrid instead of learning React Native or Flutter from zero after many encouraging posts here. I know C#, html, css, razor pages and Bootstrap so I thought that would be the safest option.
But I started to notice the app doesn't look like a mobile app. Definitely due to Bootstrap. I want another option for styling but with the least friction possible. I don't want to learn new thing else I would have learned xaml from the beginning.
Thank you
Hey everyone,
I’m currently building out a MAUI app, and I hit the absolute wall that we all dread: Localization. Manually creating .resx files, paying for API translation limits, or paying professional services is not fun. So, I built an internal tool to just do it for me using local AI, and I'm wondering if this is something the wider .NET/MAUI community would find valuable if I polished it up.
Here is what my internal tool does right now:
.resx files: You feed it your base English AppResources.resx..resx files (French, German, Spanish, etc.) with the exact, proper .NET naming conventions.gemma-3-12b-it or gemma-2-9b). No cloud API costs. No data sent to third parties.The Question: Enterprise translation management systems charge insane monthly subscriptions or per-project fees. I’m thinking about taking my internal tool, wrapping it in a polished UI (drag-and-drop, visual editors), and adding support for Custom Dictionaries (e.g., if you have a medical app and need to force the AI to use specific pharmaceutical edge-case words).
If I sold this as a "pay-once, own-it-forever" ultimate developer utility, is this something you would actually use?
What features would it need to have for you to instantly buy it? I'd love to know if I should dedicate time to releasing this for the community!
.NET MAUI officially supports Android, iOS, macOS, and Windows but not Linux desktop. I wanted to ship MAUI apps to Linux without rewriting the UI layer, so I built the platform backend myself.
It’s called OpenMaui. The short version of what’s in it:
• 47+ controls wired up… Button, Label, Entry, CollectionView, CarouselView, RefreshView, SwipeView, NavigationPage, Shell, MenuBar, and the rest of the usual suspects
• SkiaSharp rendering, hardware-accelerated, with native X11 and Wayland support
• HiDPI scaling for GNOME / KDE / X11
• 12+ platform services: clipboard, file picker, notifications (libnotify), global hotkeys, drag & drop (XDND), system tray, secure storage
• AT-SPI2 accessibility so ORCA and other screen readers actually work
• IBus/XIM for international input methods
• Standard MAUI XAML, data binding and MVVM behave the way you’d expect
• dotnet templates for both code-first and XAML-first projects
Install is just:
add package OpenMaui.Controls.Linux
I’m a solo dev on this, so I’d genuinely like to hear where it breaks for you, especially on Wayland and on less common distros.
Happy to answer questions about the handler architecture or the SkiaSharp rendering pipeline if anyone wants to know how it fits together under the hood.
For the last 1.5 years, my friend and I have been building an iOS cocktail app using .NET MAUI.
The app is called Craft & Serve: Cocktails and currently contains 250+ cocktail recipes with features like:
From the technical side:
The interesting part for me is that before this project I had basically no real iOS development experience.
I mainly come from the traditional .NET ecosystem, so MAUI gave me an opportunity to build and ship an actual iOS app while still using C#, Visual Studio, and a familiar stack.
Being able to develop most of the app on Windows in Visual Studio still feels kind of amazing to me.
Things I liked:
Things that were difficult:
Since this is my first serious mobile app, I honestly still can’t always tell where the boundary is between: “this is a MAUI limitation” and “this is just me lacking native iOS experience.”
But overall, I think MAUI absolutely made this project possible for me. Without it, I probably would never have attempted native iOS development at all.
Curious to hear from other developers who shipped real MAUI apps:
If anyone is interested, I can also share more details/screenshots from the app or specific MAUI issues we hit during development.
App Store:
https://apps.apple.com/us/app/craft-serve-cocktails/id6749594395
Hi everyone,
About a year ago I went through the Xamarin → .NET MAUI migration on a real production app. I started with Microsoft's Upgrade Assistant expecting it to do most of the heavy lifting and it really disappointed.
Some things converted fine, but in some areas it really seemed to struggle, especially when it came to our custom renderers and third party NuGet packages. It took me a ton of hours to finish polishing it up and getting it ready for release. Many hours digging through Stack Overflow threads and Github issues.
I've been working on something to try to fix that problem, specifically, it's a web tool that focuses on the parts of the migration that the Upgrade Assistant doesn't handle very well. It's still in development, but to give a broad overview:
- You upload your `csproj file(s)
- It scans every NuGet dependency and tells you: Compatible / Needs Replacement / Now Built Into MAUI / Abandoned
- For each incompatible package, it suggests the MAUI alternative with context on *why* and links to the replacement
- It flags custom renderer patterns and gives you guidance on converting them to handlers
- You get a structured migration report you can actually work from (or hand to a client)
The point of this is not to replace the Upgrade Assistant, it's just to handle a lot of the research-heavy part so you spend less time down Github rabbit holes and more time actually migrating.
As I mentioned, this is still in development. I wanted to share the idea here first and get honest feedback from people who've actually been through this, before I go further.
Some things I'm unsure about:
- Is NuGet compatibility the biggest pain point, or is there something else that cost you more time?
- Is there a specific part of the migration you wish you'd had better tooling for?
Happy to answer any questions or just commiserate about renderer migrations. 🙂
Thanks!
Hello Everyone!
i am planning to learn MAUI and do not know a lot about it. just googled some days.
any idea about it to help learn it better?
#
The calendar for MAUI UI July 2026 is now up and spaces have already started filling up quickly! We've got 10 slots filled already. You can see the calendar here: https://goforgoldman.com/posts/mauiuijuly-26
If you're not familiar, it was a tradition started for Xamarin and this will be the 5th year running it for .NET MAUI. Every day throughout July, someone from the community shares a blog post or video showing off something they've built or learned with .NET MAUI. Past contributions have included replicating the UI of a popular app, cool special effects and tricks, tutorials, personal learning experiences...there's no limit other than it has to be UI related and has to be in .NET MAUI.
Previous years' contributions have been amazing and it's been wonderful to see what people have produced. If you're looking to contribute something to the .NET MAUI community, I'd encourage you to get involved - whether you've done this every year or whether you're completely new to .NET MAUI, everyone has a perspective to share!
Comment on the post at the link or reply here if you're interested and I'll add you to the list.
Hey guys
currently I am implementing screen that needs to be able to render 10000+ list items in a tab layout.
Can you recommend me what (ideally official) components will work for this scenario?
component for “buttery smooth” scrolling list with up to 10 000 items (they all contain images)
component for tab layout in MAUI.
Additionally: what’s in your opinion best way to render such a huge dataset on the screen ? I am considering using pagination & loading data using infinite scroll.
Thanks!
I’m building Pulse, a small .NET test runner for conformance tests that run inside a real app host.
For Blazor WebAssembly, the goal is to test behavior that dotnet test can’t honestly prove: real IJSRuntime, imported JS modules, browser storage, host HttpClient, DI, and runtime services while the app is actually running in the browser.
The pattern:
*.TestSupportdotnet testexample:
public abstract class TokenStorageSpec
{
protected abstract ITokenStorage Storage { get; }
protected async Task RoundTrips(CancellationToken ct)
{
await Storage.StoreAsync("auth", "abc", ct);
if (await Storage.RetrieveAsync("auth", ct) != "abc")
throw new InvalidOperationException("Token did not round-trip.");
}
}
public sealed class BrowserStorageSuite(ITokenStorage storage) : TokenStorageSpec
{
protected override ITokenStorage Storage => storage;
[PulseCase(TimeoutMs = 5000)]
public Task LocalStorage_round_trips(CancellationToken ct) => RoundTrips(ct);
}
So the fake-backed test proves the rule in dotnet test, and Pulse proves the same rule through the real browser/runtime boundary.
Pulse is intentionally small: one NuGet package, no Blazor-specific package, no Test Explorer integration, no UI framework, and it returns a structured TestRunReport.
It’s preview-stage. I’m still figuring out the right direction before calling it stable. The focus is conformance testing for app/runtime boundaries, not replacing unit tests or UI automation.
Specs/rules: https://github.com/Circuids/Pulse/blob/master/docs/conformance-specs-and-rules.md
GitHub: https://github.com/Circuids/Pulse
NuGet:
Circuids.Pulse
Feedback welcome, especially from people building Blazor apps with JS interop, browser storage, host wiring, or runtime behavior that is awkward to verify in normal tests.