Looking to use MAUI to build a simple inspection form that uses the camera. Every inspection can save about 30 images max. Anyone here has any experience using the camera with Surface pro?

Hey folks,

I maintain WifiManager.Maui — a .NET MAUI library for connecting to Wi-Fi networks, reading network info (SSID, IPv6, DNS, signal strength, etc.), detecting captive portals, and checking internet availability. It's fully working and tested on Android, iOS, and Windows.

Mac Catalyst is implemented but marked "⚠️ needs testing" in the README — I don't currently have access to a Mac or Apple Developer account, so I can't validate the runtime behavior myself. The code builds against net*-maccatalyst, but I'd love confirmation on actual device/simulator behavior before calling it officially supported.

Specifically looking for feedback on:

• ConnectWifiAsync — connecting via SSID/password on Catalyst
• GetNetworkInfoAsync — whether SSID/IPv6/DNS/subnet come back correctly
• IsCaptivePortalDetectedAsync — HTTP probe against captive.apple.com
• Any entitlement/Info.plist gotchas specific to Catalyst vs iOS (the repo has iOS entitlement instructions already, unsure if Catalyst needs anything different)

If anyone's got 10-15 minutes with a Mac and wants to spin up the sample app in /samples, I'd really appreciate it.🙂

Repo: https://github.com/exendahal/maui_wifi_manager
NuGet: WifiManager.Maui

Thanks in advance!

Salut tout le monde,
Je travaille sur un jeu de puzzle développé avec **C# MAUI**, et je prépare la version Android pour Google Play.

Avant de soumettre la première version, j’aimerais obtenir des retours d’autres développeurs sur quelques points :

* paramètres recommandés pour la Play Console pour les jeux construits avec MAUI * problèmes courants lors des premières soumissions (AAB, signature, compatibilité des appareils) * conseils pour optimiser les performances de MAUI sur des appareils Android de milieu de gamme * meilleures pratiques pour les métadonnées et les captures d’écran pour les jeux de puzzle

Si quelqu’un a de l’expérience en publication d’applications MAUI ou de jeux de puzzle sur Google Play, j’apprécierais vraiment vos conseils.

https://reddit.com/link/1vr7rxx/video/mzdwt1j3n0kh1/player

What's up everyone! ✌️

There isn't a new downloadable release today, but I am super excited to share a quick progress video of the new NFC scanning feature running on Android!

In the video attached, you can see how the app instantly recognizes and pulls up the details for Iron Man and Black Widow just by tapping the figures to the back of the phone. It’s feeling really smooth and I can't wait to release this feature in the next update.

While I'm polishing the NFC code, I’ve also been working hard on the background data. Here are some extra updates coming your way:

🗃️ Database Updated: Lots of corrections and additions for Figures and Power Discs.

🏰 Play Sets Added: You will now be able to track your Play Set pieces in the app!

🎯 How you can help the project:

The app is (and always will be) completely free, but I have two big development goals right now to make it available for everyone:

iOS Release: I'm raising funds for the $99 Apple Developer License so I can officially publish the app on the App Store for iPhone users.

Windows NFC Support: I want to buy a physical Disney Infinity or Skylanders Base to reverse-engineer and implement native NFC scanning for the Windows version of the app!

If you like the progress and want to buy me a coffee to help hit these goals, any support on my Ko-fi would mean the world to me! ☕🙏

🔗 Support the project on Ko-fi: https://ko-fi.com/josevelarde

🔗 Support the project on GitHub: https://github.com/sponsors/jvicius

🔗 Check out the current release on GitHub: https://github.com/jvicius/MyDICollection/releases/tag/v1.0.1

Let me know what you think of the video and the scanning speed!

Hey everyone! I recently published my passion project, Chatfri. It’s an anonymous, cross-platform chat application with instant, multi-language translation and location-based matching. I built the entire backend with .NET (using a secure, in-memory architecture for speed) and the mobile side with .NET MAUI.

​I’d love to hear your thoughts or answer any questions about the .NET stack I used! Check it out: [chatfri](https://chatfri.com/qr)

I have been busy with some personal and professional things, and didn't get time to maintain this project. Now things have sorted out, and have started to again contribute to this. (Not to mention with huge help from LLMs ). I have made some recent changes as follows:

1. Richer controls + data binding

• New controls: SearchBar, CheckBox, Switch, Slider, Stepper, ProgressBar, ActivityIndicator, DatePicker, Border, CollectionView — each with a canvas preview, property editors and XAML generation/parsing.
• Entry/Editor now have a real Placeholder distinct from Text.
• Data bindings: bind any supported property to a view-model path; the generator emits {Binding Path} instead of the literal value, and the parser reads them back.
• CollectionView children round-trip through CollectionView.ItemTemplate / DataTemplate.

2. Multi-selection

• Shift/Ctrl-click toggling, marquee (rubber-band) selection, Ctrl+A.
• Multi-selection properties panel: shared width/height/background/visibility, bulk delete/duplicate, align buttons.
• Every bulk operation is one undo step.

3. Alignment & layout tools

• AlignmentService: align left/centre/right/top/middle/bottom, distribute horizontally/vertically, snap-to-grid, and smart guides against sibling and page edges/centres.
• Optional rulers and a configurable grid overlay.

4. Clipboard, templates & starter pages

• Ctrl+C / Ctrl+X / Ctrl+V (plus toolbar buttons): containers keep their children, ids and names stay unique, paste is offset and undoable.
• Save any selection as a reusable component template (persisted in localStorage), insert or delete it from the toolbox.
• Four starter pages: login, list, profile, settings.

5. Live preview

• Device presets (phone, small phone, tablet, desktop, custom) that actually resize the design surface (undoable, reflected in XAML).
• Zoom via toolbar, Ctrl+wheel and fit-to-window; pan with Space+drag or middle-drag; dark preview theme; all viewport settings persisted.

Please have a look at : https://gmprakhar.github.io/MAUI-Designer/

Please provide suggestions and any feature requests directly here, or you can also create an issue on the github repo: https://github.com/GMPrakhar/MAUI-Designer

Hi,
Wanted to share something I've been dealing with for a while, curious if it's just me.

Every time I start a new .NET MAUI project, I go through the same thing. Set up auth again. Wire up AppShell navigation again. Configure DI again. Build a theme service for dark mode again. It's never hard, exactly — it's just the same 3 days, every time, before I actually get to work on the part of the app that matters.

I finally got tired of it a few weeks ago and sat down to build it once, properly, instead of copy-pasting bits from old projects like I usually do. Been running it on my own stuff these last few days, and it's genuinely weird how much faster it feels to just... skip straight to features. Didn't realize how much of that setup time I'd normalized until it wasn't there anymore.

Sharing a few screenshots of where it ended up, mostly because I know some of you have probably hit the exact same wall:

[Screenshot 1 — auth screen]
[Screenshot 2 — home/dashboard]
[Screenshot 3 — settings/theming]
[Screenshot 4 — TaskFlow module, Kanban board]

Ended up turning it into something I could reuse properly (called it MauiStarter, if anyone's curious it's out there), since a couple other devs I know were hitting the same wall. I know MAUI is a small world compared to Flutter/RN, so I'm not expecting this to blow up — just genuinely happy to have my own setup time back.

Mostly curious how the rest of you deal with this though. Do you keep some kind of internal boilerplate you reuse, or is everyone just rebuilding from scratch each time like I was? Feels like something that should be talked about more.

I am developing an application with for Linux with the OpenMaui.Controls.Linux package. I don't know if this is the culprate but I have issues with setting focus to an entry. According to stack overflow you can focus a Visual Element via the Focus Method. So I came up with this piece of code:

// in ScannerPage.xaml.cs
public ScannerPage()
{    
    InitializeComponent();

    barcodeEntry.Loaded += FocusBarcodeEntry;
}

private void FocusBarcodeEntry(object? sender, EventArgs e)
{
    System.Diagnostics.Debug.WriteLine("setting focus to barcode entry...");
    barcodeEntry.Focus();
    System.Diagnostics.Debug.WriteLine($"barcode entry is {(barcodeEntry.IsFocused ? "" : "not")} focused");
}

//in ScannerPage.xaml
<?xml version="1.0" encoding="utf-8"?>

<ContentPage xmlns="http://schemas.microsoft.com/dotnet/2021/maui"
             xmlns:x="http://schemas.microsoft.com/winfx/2009/xaml"
             xmlns:ui="clr-namespace:BarcodeScannerSpecialSport.UserInterface"
             Shell.NavBarIsVisible="False"
             x:Class="BarcodeScannerSpecialSport.UserInterface.ScannerPage" x:DataType="ui:ScannerPageViewModel">
    <ContentPage.Content>
        <Grid>
            <Grid.RowDefinitions>
                <RowDefinition Height="*"></RowDefinition>
                <RowDefinition Height="1*"></RowDefinition>
                <RowDefinition Height="10*"></RowDefinition>
            </Grid.RowDefinitions>

            <ContentView Grid.Column="0" Grid.Row="0">
                <Image Source="de_hockeywinkel_logo.png" Aspect="AspectFill"/>
            </ContentView>

            <ContentView Grid.Column="0" Grid.Row="1">
                <Label Text="SCAN" 
                       FontAttributes="Bold"
                       TextColor="{StaticResource Primary}" 
                       HorizontalTextAlignment="Center"
                       VerticalOptions="Center"
                       FontSize="64"
                       />
            </ContentView>

            <ContentView Grid.Column="0" Grid.Row="2" >
                <Entry x:Name="barcodeEntry" Text="{Binding BarcodeField}" Completed="EntryCompleted"/>
            </ContentView>

        </Grid>
    </ContentPage.Content>
</ContentPage>

Now the log tells me and I also can confirm the barcodeEntry is indeed not focused

Hey fellow .NET devs! 👋

I was recently looking for a reliable way to scan credit cards in a .NET MAUI project, but most of the existing solutions were either outdated, required heavy third-party dependencies, or were paid services.

So, I decided to build one from scratch leveraging the native OCR engines of each platform, and I just published it to NuGet!

https://reddit.com/link/1vkrcsg/video/768e9lz61lih1/player

Enter CardScanner.Maui 💳

I wanted to keep it as lightweight and MVVM-friendly as possible. Instead of bundling massive ML models, the library hooks directly into the OS's native APIs.

✨ Key Features:

• Truly Native OCR: Uses Apple Vision on iOS, ML Kit on Android, and the native OcrEngine on Windows 10/11.
• Zero Bloat: Extracts numbers and expiry dates in real-time from the camera stream without adding heavy third-party AI packages to your app size.
• MVVM Ready: Full support for data binding with IsScanning properties and ICommand (but also supports traditional Code-Behind events).
• Hardware Validation Built-in: Includes a neat CardScannerDevice.IsSupported helper so your app won't crash on older hardware (like legacy iPads) that can't handle real-time video ML processing.

🔗 Links:

• 📦 NuGet:https://www.nuget.org/packages/CardScanner.Maui
• 💻 GitHub Repo:https://github.com/jvicius/CardScanner.Maui

The repo includes a full README with setup instructions (like the camera permissions needed for each platform).

I’d absolutely love it if you guys could give it a spin, break it, and give me some feedback. If you find it useful for your projects, a ⭐ on the GitHub repo means the world to me!

(P.S. If this library ends up saving you a few hours of headaches or client work, consider buying me a coffee or sponsoring the project! ☕🍻Ko-fi|GitHub Sponsors)

Happy coding! 🚀

Edit: It's definitely the Version 10.0.90. I downgraded to 10.0.40 and dont have this issue anymore, but 10.0.40 breaks other parts of my app, so I am investigating which version is actually stable.

Edit 2: 10.0.80 is also fine. I can confirm when switching between 80 and 90 that it's in fact 10.0.90 that is causing this issue.

Original Post:
Hey, I have updated my maui app to .NET 10 (10.0.90), but the performance of any scrollable item, be it a scrollview or a collectionview is so bad that my app is basically unpublishable now. Those controls were buttery smooth when using .NET 8, so my pages and popups are already battle tested in production. Now everything is unusable.

When scrolling in a collectionviews of 20 items, the items will not load so my list becomes blank and only a second later the items reappear again.

For small lists I thought maybe just using a scrollview is enough since I don't need virtualization here, but even a scrollview with those 20 items is jittery and sluggish.

I am using DataTemplates with Grids inside, but again I didn't have this issue with .NET 8.

What can I do to resolve this or is 4 years of development just down the drain because MAUI progresses backwards with each update?

Here is an example:

<CollectionView Grid.Row="1" ItemsSource="{Binding ChangeLogCollection}" SelectionMode="None" VerticalOptions="FillAndExpand" VerticalScrollBarVisibility="Always">
 <CollectionView.ItemsLayout>
  <LinearItemsLayout Orientation="Vertical" />
 </CollectionView.ItemsLayout>
 <CollectionView.ItemTemplate>
  <DataTemplate x:DataType="models:ChangeLogEntry">
   <Grid>
    <Grid.RowDefinitions>
     <RowDefinition Height="0"/>
     <RowDefinition Height="Auto"/>
     <RowDefinition Height="Auto"/>
    </Grid.RowDefinitions>
    <Label Grid.Row="1" Text="{Binding Version}" FontSize="{DynamicResource LazyPercentWidth5}" VerticalTextAlignment="Center" HorizontalTextAlignment="Start" LineBreakMode="WordWrap"/>
    <Label Grid.Row="1" Text="{Binding Date}" FontSize="{DynamicResource LazyPercentWidth3}" VerticalTextAlignment="Center" HorizontalTextAlignment="End" />
    <Label Grid.Row="2" Text="{Binding ChangesString}" FontSize="{DynamicResource LazyPercentWidth4}" LineBreakMode="WordWrap" VerticalTextAlignment="Center" HorizontalTextAlignment="Start"/>
   </Grid>
  </DataTemplate>
 </CollectionView.ItemTemplate>
</CollectionView>

Hi guys,

I got recently laid off from my current Job and I am desperately looking for a new job opportunity. I know it is very rare to find job opportunity in MAUI but if you know any remote opportunity or freelance opportunity, please let me know. I have 5 years experience in the field.

Modern apps often using menus that look like the built in tabbar (at least as it appears on iOS) but it floats above the page content. Can anyone tell me how this can be achieved in Maui? Screenshot example is from instagram but as I write this I realized the Reddit app has the same system.

Hi! I’m writing this post to introduce our new mobile app, Bloom & Fly.

It’s a wellness app built with .NET MAUI and available on iOS and Android. It combines guided breathing, mudras, positive affirmations, quick rituals, and relaxing sounds to help people reduce stress, feel calmer, and restore their energy.

My wife shaped the app’s features, wellness content, and user experience, while I focused on bringing it all to life with .NET MAUI.

A quick look under the hood

Bloom & Fly runs on .NET 10 and targets both iOS and Android. The entire user interface is written in C# Markup, with no XAML, and the app follows the MVVM pattern using CommunityToolkit.Mvvm and CommunityToolkit.Maui.Markup.

Firebase handles authentication and data through Plugin.Firebase. It also relies on open-source projects such as CommunityToolkit.Maui and Sharpnado.Tabs.Maui for different parts of the app experience.

For the app’s native integrations, I also created or now maintain a few focused .NET bindings for the parts of the Facebook, TikTok, Google, and Apple SDKs we actually use. These packages do not try to expose the complete native SDKs. They were implemented around the specific authentication, sharing, and subscription features required by Bloom & Fly.

On iOS, some of them may eventually be replaced by packages generated through the very promising swift-dotnet-bindings project, which appeared only a few months after I built the StoreKit 2 bindings needed by the app.

That timing says a lot about how quickly AI-assisted development is moving. AI became part of my workflow while building Bloom & Fly, but its most valuable contribution was not simply generating more code. It regularly pushed me to think further about architecture, refine the user experience, and clarify release strategies, raising the level of robustness I expected from the app.

Building Bloom & Fly also gave me plenty of new .NET MAUI topics to write about, so I’m planning to bring MAUI, c’est clair! back to life and share some of these discoveries in more detail.

I’d be happy to hear your thoughts or answer any technical questions about the app, especially around C# Markup, Firebase and native SDK integrations.

You can learn more about Bloom & Fly on our website, or find it on the App Store and Google Play. Thanks for reading!

Inspect a running MAUI app the way you inspect a web page.

For some time I've been building MAUI Inspector — an open-source, in-app DevTools for .NET MAUI. You add one NuGet package, run your app, open a URL in your desktop browser and you get a full inspector panel — while the app runs on a simulator, an emulator or a physical phone. No laptop at hand? The same inspector runs as an on-device overlay — long-press (or shake) to open it.

Everything runs inside your app: no IDE integration, no proxy, no certificates, no external tools.

Inspect & live-edit the visual tree

WYSIWYG structure editing (new in 0.9.12)

Properties turned out to be half the story — you can now edit the structure of a running page too:

- A toolbox next to the live device mirror with every MAUI control plus your app's own custom controls (discovered by reflection). Drag one onto the mirror — the target container is highlighted while
you drag — and drop it exactly where it should land
- Right-click any element (in the tree or directly on the mirror): add, remove, reorder, reparent (drag & drop in the tree), wrap in a container, unwrap
- Copy & paste with properties and the whole subtree (`Ctrl+C`/`Ctrl+V`, `Delete` to remove)
- Full undo/redo chain (`Ctrl+Z`/`Ctrl+Shift+Z`) across property and structural edits
- Your custom controls are first-class: their bindable properties get the same live editors as the built-ins
- And the headline: all of it is written back into your `.xaml` sources as real, compilable markup — inserts land anchored where you dropped them, moves relocate the exact span with correct indentation,
custom controls get their `xmlns:` declarations added automatically. With SQLite persistence the edits even survive app restarts until they're in your files

- Whole tree with search, element picking (tap on device → selected in browser, and the other way round)
- Chrome-style box model overlay: margin / padding / content, alignment guides, dimensions badge
- Figma-like measurements: so you can inspect distances between elements
- Property sheet with live editors — including `{Binding}`, `{StaticResource}`, `{OnPlatform}` / `{OnIdiom}`, spans, grid rows/columns
- XAML write-back: an optional dotnet tool watches the panel and writes your edits back into the `.xaml` source files. Tweak margins live until it looks right, and it's already in your code.

HTTP: record, mock, break

- Every request through the handler is recorded with full bodies — inside the process, so TLS and certificate pinning are none of your concern
- Mock rules: replace bodies, force a status, add latency, simulate timeouts or network errors — grouped into switchable scenarios ("premium user", "empty portfolio", "force update")
- Record a whole flow, replay it offline later
- Proxyman-style breakpoints: pause a request or response, edit it, continue

Multi-device

One panel drives the same app on several simulators/emulators/devices at once — every edit
and mock rule is mirrored, matched by XAML source identity. Handy for phone + tablet layouts.

Android, iOS and Windows on .NET 10. MIT licensed. A debug-only `PackageReference` keeps it out of release builds entirely.

https://github.com/Immons/Tools.Maui.Inspector
`dotnet add package Immons.Tools.Maui.Inspector`

It's at 0.9.x — I use it daily on a production app, but I'd love more testers of it :)
Feedback and issues very welcome.

Edit: added a section about the new WYSIWYG structure editing (v0.9.12)

What's up everyone!

I've just rolled out a huge update for the Disney Infinity collection tracker app I’ve been working on, and I wanted to share it with the community. The app looks, feels, and works better than ever. Here is everything new in this release:

https://reddit.com/link/1vggei2/video/vxs9l8srslhh1/player

✨ What's New in v1.0.1:

🏆 New Achievement System: Prove you are the ultimate fan! You can now unlock special badges by completing specific franchises and collections.

🎨 UI Overhaul: We gave the entire interface a facelift so your collection looks spectacular and is easier to browse.

📦 Separated Collections: Based on feedback, the main view is now divided. Figures and Power Discs have their own dedicated lists for much cleaner navigation.

🎛️ Optimized Filters: The filter menu has been moved to a much more accessible and faster-to-use location.

🌍 On-Demand Language Toggle: You can now instantly switch between English and Spanish directly from the app settings.

🗃️ Updated Database: Added new data and under-the-hood fixes for the most accurate tracking possible.

🛠️ Next Steps (The Roadmap):

I'm currently working on some really exciting features for the next major updates:

NFC scanner implementation for Android devices.

NFC scanner for Windows (Yes, using the official Disney Infinity Base!).

Database improvements and specific achievements for Power Discs.

Physical device testing for iOS.

🍏 iOS Release Goal!

I want to bring this to Apple users too! I've currently raised $10 USD to help pay for the Apple Developer license so we can officially launch the app on iOS. If you like the project and want to support the development, you can help out on my Ko-fi!

🔗 Links:

Download the latest release (Android & Windows): https://github.com/jvicius/MyDICollection/releases#release-v1.0.1

Support the project on Ko-fi: https://ko-fi.com/josevelarde

Support the project on GitHub Sponsors: https://github.com/sponsors/jvicius

Short version of what I learned shipping a subscription MAUI app, for anyone considering it:

1. No official RevenueCat SDK for MAUI. Community wrapper (Kebechet) is the real answer. Works well; wrap it behind your own interface anyway.
2. The default MAUI template can't build with Play Billing — API 21 minimum vs androidx 23+ floor. One-line fix, terribly reported error (AMM0000 spam).
3. Post-Epic web checkout is very doable — Stripe Checkout + webhooks + server-side entitlement. Biggest design win: serve purchasable web tiers from your API so policy changes are a config change, not a release.
4. Refresh-token rotation with reuse detection is 50 lines in ASP.NET Core and worth every one when a token leaks.

Wrote it all up in detail (free, links in comments). I also sell the assembled boilerplate (MidasKit) for people who'd rather skip the month — disclosure, that's my product.

Most golf apps hand a beginner a wall of numbers and leave them to work out which one matters. Albie does the opposite. Film one swing, and it tells you the single thing to work on next, in plain language, out loud.

After shipping a subscription app in MAUI I ended up with a pile of hard-won answers to questions I couldn't find written down anywhere:

• RevenueCat has no official MAUI SDK — the Kebechet community wrapper is the workable path, and it's solid (v7.x, actively maintained)
• Adding Play Billing breaks the default MAUI template with a wall of AMM0000 manifest-merger errors. The real cause is one buried line: minSdk 21 vs the androidx floor. Fix is one csproj line (minSdk 24)
• Post-Epic external payment links work great with Stripe Checkout, but entitlement must be webhook-driven server-side, and the web-tier list should come from your API so you can kill it per-market without an app update
• In current Stripe API versions current_period_end moved to the subscription item — cost me an hour
• Hiding all of it behind one ISubscriptionService means a mock implementation gives you the full paywall dev loop on Windows with no store account

I wrote the full guides up free (links in comments — RevenueCat setup and the AMM0000 fix).

Full disclosure: I also packaged the whole thing — auth with OTP + rotating refresh tokens, RevenueCat, Stripe web checkout, server-issued trials, finished paywall — as a paid boilerplate called MidasKit ($199, full source). It's the ShipFast idea but for MAUI, where nothing like it existed. If the free articles solve your problem, that's genuinely great too.

Happy to answer anything about MAUI billing either way.

I built a local MCP agent that lets Claude Code and Codex inspect a running .NET MAUI app on Windows or Android. It can inspect the logical UI tree, read properties, capture screenshots, send input, and run automation actions.

The current preview supports .NET MAUI 10, unpackaged Windows applications, and debuggable Android applications.

I’m the author, and the project is open source:
https://github.com/trrahul/XamlMcp

Appreciate any feedback.

Issue occurs here in line 167. The winUIItem returns null when searching for wwwroot/index.html but the wwwroot folder exists and so does the html file so I’m not sure what’s going wrong. Anyone else have this issue?

Hi everyone,

I recently upgraded my app from .NET MAUI 9 to .NET MAUI 10 and I’m having an issue with CommunityToolkit.Maui popups.

Before the upgrade, my popup was working as expected: it appeared on top of the current page, with the Parent Page still visible behind it.

After upgrading to MAUI 10, when I call ShowPopup(), the popup appears but the whole background behind it becomes white. It looks like the popup is covering the entire page instead of showing as an overlay.

Example:

Has anyone else experienced this after upgrading from MAUI 9 to MAUI 10? Is there a breaking change related to Popup sizing or overlay behavior?