r/dotnetMAUI • • 3d ago

Help Request iPhone Duo support in Controls.Foldable: has anyone got it working?

2 Upvotes

The 11.0.10 release notes say “Add iPhone Duo support to Controls.Foldable”, so I tried it in my app but it doesn’t seem to be in the package. On my machine, Xcode 27.2 with the iPhone Duo simulator runs the app fine, but nothing reacts to the hinge.

From what I can tell, the Duo code only builds when the package is compiled against the iOS 27.1 SDK or newer. The official builds still use older iOS 27.0 SDKs, so it gets left out, but I could be interpreting this wrong!

Any help is appreciated!


r/dotnetMAUI • • 4d ago

Discussion Automating MAUI Windows apps

4 Upvotes

Hey guys

Do you write automation tests for your MAUI app?

What framework are you using ?

Have you considered using library Maestro for automating Windows tests ?

https://maestro.dev/

Based on my research, Windows is not supported.

But I am wondering whether this missing layer is something I could vibecode with AI, and then I would be able to use Maestro for testing Windows apps.

Thanks


r/dotnetMAUI • • 4d ago

Discussion version 11

15 Upvotes

Has anybody tried to migrate .net maui app (namely I'm interested iOS version) to version 11? Do any major issues exist?

I have a plan to prepare a new release in a couple of weeks and I don't know does it make sense to migrate to the new version now. I hope that migration to CLR can significant improve the performance on iPhones.


r/dotnetMAUI • • 7d ago

Article/Blog I'm happy to announce my first open source project Stampeded.NET

7 Upvotes

I've been working on an open-source integration called Stampeded.NET.

It's a C# wrapper around Stampeded, an existing PostgreSQL-backed job processor written in Rust.

Instead of implementing a separate job engine using Npgsql, the library calls the upstream Rust implementation through its C ABI.

The .NET side provides:

  • Strongly typed job handlers

  • Dependency injection and hosted worker integration

  • Retries and checkpoints

  • Job execution in C#

  • Native packaging for Linux x64, Windows x64, and macOS ARM64

The project targets .NET 10 and PostgreSQL 18+.

I've alredy added it on NuGet

The documented CI validation includes 29 passing .NET tests, alongside upstream ABI/database checks.

It's still a development preview, and I'm interested in technical feedback, especially around the API design, native interoperability, and developer experience.

Repository: https://github.com/Mourad-Azouga/stampeded-dotnet

pls any feedback is welcomed


r/dotnetMAUI • • 7d ago

Help Request Anyone here speaks spanish?.

Thumbnail reddit.com
2 Upvotes

r/dotnetMAUI • • 7d ago

Showcase My new .net Maui app BankHolidays UK.

Thumbnail
gallery
12 Upvotes

After what feels like forever my new app finally passed review. It failed first time as I forgot to set my In App entry to in review ( lesson learned ).

This app shows the latest UK Bank Holidays ( and past ). It has multiple themes that can be unlocked for a small purchase.

Link here :
Bank Holidays UK


r/dotnetMAUI • • 8d ago

News Shiny.NET has grown a lot: 50+ libraries and 100+ controls

56 Upvotes

Shiny.NET has had its biggest stretch of updates yet: Shiny 6, 15+ new libraries, 40+ new controls and major upgrades across AI, speech and audio. Here's the rundown. Everything is at https://shinylib.net

By the numbers

  • Libraries: 30+ → 50+

  • Controls: 40+ → 100+

  • DocumentDb backends: 11+ → 20

More new libraries

  • BluetoothLE Hubs: SignalR-style hubs between nearby devices over BLE, with no server or internet needed. Strongly typed, source-generated proxies, group and broadcast messages, and L2CAP file transfers.

  • Universal Hubs: the same hub model over Wi-Fi and BLE together. Devices are discovered over BLE and mDNS, connect over Wi-Fi first with BLE as the fallback, and resume after short drops.

  • App Functions: declare a function once in C#, and it's exposed to Siri, Spotlight, Shortcuts and Apple Intelligence as App Intents, and to Gemini as Android AppFunctions. The same functions double as AI tools for an in-app LLM.

  • Hardware: Classic Bluetooth, NFC, Biometrics, VPN, Printing, Game Center / Play Games, Region Geofencing (unlimited regions and polygons)

  • App: App Store (version checks and review prompts), Call Directory

  • Architecture and server: Actors (Orleans-style, in-process), ASP.NET Extensions, EF Core Extensions (coming in 1.0)

Big upgrades

  • AI Conversation 3: persistent sessions, streaming and interruptible replies, long-term memory, image input, push-to-talk and barge-in

  • Speech and Audio 3: full-duplex call audio, mic effects, emotion and tone across providers, offline Whisper speech-to-text

  • App Device Bridge: run Blazor or React apps inside MAUI with typed device access

New controls

  • Office Suite: Document Editor, Slide Editor and Spreadsheet for .docx, .pptx and .xlsx, plus Office Shell

  • Layout and navigation: TabbedPage, ShinyFlexLayout, YogaLayout, ZoomPanView, Page Transitions, Wizard / StateView, Foldables, NotchView, Tray Icon

  • Input: Slider, RangeSlider, Range Pickers, ButtonGroup, ChipGroup, TagEntry, MediaPickerButton, Keyboard Shortcuts

  • Data and productivity: Kanban, Timeline, Gauge, Notebook, CoverFlowView, FloatingToolbar

  • Visual: Avatar / AvatarGroup, AnimatedBackground, VideoText, BorderBeam / ShineBorder, Marquee, Confetti, Scratch Card, ShinyImage

  • Also: Gamepad and Media Service for Blazor

Try the controls in your browser: https://shinyorg.github.io/controls/

Still free, still open source. Feedback, issues and PRs are always welcome.


r/dotnetMAUI • • 9d ago

Showcase Simple3D 0.3.0 adds GPU rendering and animated characters to .NET MAUI

Thumbnail
gallery
12 Upvotes

I released Simple3D 0.3.0. It’s an MIT-licensed control for putting interactive 3D scenes in .NET 10 MAUI apps.

When I shared the first preview, someone asked why I was rendering on the CPU. With 0.3.0, SceneView uses Metal on iOS and Mac Catalyst and OpenGL ES 3 on Android. In Auto mode it can fall back to the C# software renderer, and the sample app tells you which backend it picked and why.

You can now load rigged characters from binary glTF and VRM, pose their skeletons, and drive blend shapes on the GPU. I built a sample called Mirror to try it out. Point the camera at someone and a VRM character follows their movements, head turns and expressions. Tracking runs on the device. The demo clip uses public-domain footage from NASA/JSC and the CDC.

Since the first preview I’ve also added textures, smooth shading and OBJ import. The sample gallery has a grid on phones and a sidebar on tablets and Mac. The docs cover choosing a renderer and loading and posing a character.

If you try the gallery on Android, I’d like to hear which device you used and which renderer it picked.

Source and samples · NuGet 0.3.0


r/dotnetMAUI • • 10d ago

Discussion TestFlight or Firebase alternative but for Windows apps

4 Upvotes

Hi folks

How do you release your Windows app internally / to beta testers before it goes to production?

Android and iOS apps have Firebase App Distribution or TestFlight, but I didn’t find any sensible way of doing a closed testing with Windows apps (msix installer).

Thanks.


r/dotnetMAUI • • 12d ago

Showcase Run ollama on Maui App

Thumbnail
gallery
0 Upvotes

Implemented an ollama support in one of my android app, that created in maui

https://play.google.com/store/apps/details?id=com.DevNullCraft.PatientManager

Just a showcase app currently experiemnting with things, let me know guys if you have anything in mind.

Although it's super slow even ollama's phi3:mini model but just a first step.


r/dotnetMAUI • • 14d ago

Showcase .NET MAUI is a trap

49 Upvotes

We’re a small software company selling a point-of-sale system (cyvy.online). As we grew, we became Stone partners and developed an app that runs directly on their payment terminals.

We built the first version with .NET MAUI. It seemed like a natural choice: our entire stack was already .NET, including our desktop app (MAUI), backend, and Blazor frontend with SignalR. Sticking with the same technology made sense because it was the stack we all knew.

But the experience on the terminal was frustrating. The app took almost 10 seconds to launch, and the package was around 50 MB. Imagine that at the counter with a customer waiting to pay. What was supposed to make development easier ended up causing plenty of headaches.

We’re now building version 2 with Kotlin + Jetpack Compose, keeping the .NET backend. The migration is still underway, but the results are already encouraging: the app launches in 1.4 seconds and is only around 8 MB.

I wanted to share our experience as a heads-up. After this, I honestly don’t think MAUI is ready for real-world projects yet. We couldn’t make it work well enough as a team of four developers who primarily work with .NET, even with LLM assistance.


r/dotnetMAUI • • 14d ago

Article/Blog .NET MAUI for Web

Thumbnail
shinylib.net
37 Upvotes

Sample: https://shinyorg.github.io/mauiplatforms/

Platform.Maui.Web is a new .NET MAUI backend that runs your app on WebAssembly. Every control renders as a real HTML element:

* Button → <button>, Entry → <input>, DisplayAlert → <dialog>

* Shapes and borders → SVG, GraphicsView → 2D canvas

* MAUI's own layout engine handles the positioning, so Grid, FlexLayout and your custom layouts behave the way they do on other platforms

What already works:

* Your existing XAML. It's been tested on the stock dotnet new maui template with compiled bindings, AppThemeBinding, OnPlatform/OnIdiom and VisualStateManager.

* Shell, NavigationPage, TabbedPage, FlyoutPage and modals. On phones, tabs move to the bottom and the flyout becomes an overlay.

* CollectionView, CarouselView, the pickers, gestures and light/dark theming.

* Essentials backed by browser APIs: Preferences, Geolocation, Clipboard, Share, sensors, FilePicker and more.

What you need: the .NET 10 SDK. No workload to install. dotnet publish produces static files you can host anywhere.

To add a web version of an existing app, create a small project next to it that links your shared XAML and C#, and swap UseMauiApp<App>() for UseMauiAppWeb<App>().

It's experimental and open source. CollectionView isn't virtualized yet, and there's no drag & drop or pinch yet. Try it out and tell us what breaks.

Sample: https://shinyorg.github.io/mauiplatforms/

👉 github.com/shinyorg/mauiplatforms · NuGet: Platform.Maui.Web


r/dotnetMAUI • • 15d ago

Showcase 📦 NuGet Package Manager for VS Code — manage .NET packages in the editor

7 Upvotes

r/dotnetMAUI • • 15d ago

Article/Blog 🚀 AI Workspace Manager for VS Code — stop hand-copying skills and agents into every repo

1 Upvotes

The problem Copilot, Claude Code and Reasonix only follow the skills, agents and instructions present in the repo. Getting them there is manual, and it fails predictably:

• All-or-nothing — cloning the template brings the whole catalog, including what a project will never use. No per-repo selection, no dependency closure.
• Silent drift — installed files get edited in place; the next template update overwrites that work or is skipped, and nobody can tell template-owned from locally changed or stale.
• No provenance — where an item came from, which revision, its licence, or whether upstream moved is hard to answer.
• Sources do not compose — the template catalog and awesome-copilot overlap, so duplicates and name collisions surface only after install.
• Risky updates — without a lock and content hashes, updating is a re-clone that can delete local changes.

The solution A full-page manager for the skills and agents each repo installs, over one catalog built from I-Synergy/AI and github/awesome-copilot.

• Browse, search, filter and bulk-select; apply presets with dependencies resolved.
• Only what you selected lands in the repo — one selection in .ai/ai.json, reviewable in a diff.
• Pinned refs plus per-item content hashes: updates are a diff, with local-modified / upstream-changed / conflict states.
• Nothing destructive by default — removing edits the selection; files leave disk only via an explicit prune.
• First activation sets up .ai/, AGENTS.md, Copilot/Claude config and the .claude / .github / .reasonix junctions.

Marketplace: https://marketplace.visualstudio.com/items?itemName=I-Synergy.aiworkspacemanager
Source:  https://github.com/I-Synergy/AIWorkspaceManager


r/dotnetMAUI • • 18d ago

Article/Blog My experience building mobile apps with .NET MAUI and Blazor Hybrid

31 Upvotes

Hi everyone!

I recently wrote about my experience building apps with .NET MAUI and Blazor Hybrid. It started with a Dutch dictation app for my child and turned into a few more personal apps. I also share a few lessons from using AI tools to improve the UI.

https://medium.com/@babaknia/know-c-and-javascript-youre-already-a-mobile-developer-61c81bb5d95a

I’d be more than happy to hear your feedback. Have you had similar experiences, or did you solve some of these problems differently?


r/dotnetMAUI • • 19d ago

Showcase Testing Play Age Signals + Apple Declared Age Range in .NET MAUI (and a free open-source wrapper, preview)

9 Upvotes

Recently I asked how .NET teams are handling the new app-store age laws. The recurring pain point was testing, so here's what we learned, plus the library we built along the way.

Testing on iOS (Declared Age Range)

  • The Simulator doesn't give real values; you need a real iPhone on iOS 26.2+.

  • Turn on Developer Mode, then sign in to a Sandbox Apple Account under Settings > Developer.

  • Under the sandbox account's Age Assurance settings you can pick scenarios (under 13, 13–15, 16–17, 18+, Off), and requestAgeRange returns the matching range.

  • The app needs the Declared Age Range capability on its App ID and in its provisioning profile.

Testing on Android (Play Age Signals)

  • Google ships a FakeAgeSignalsManager for tests; the real manager only returns real signals for apps installed from Google Play (a sideloaded build gets "not shared").

The library (free, Apache-2.0, preview)

  • One API over both platforms: Declared Age Range (requestAgeRange and the 26.2/26.4 calls, weak-linked so apps still run on older iOS) and Play Age Signals.

  • Fakes in a separate Ageledger.Testing package, so you can unit-test your age logic without a device.

  • An optional local decision log with exactly five fields (no birthdates or device IDs). Off by default.

NuGet: dotnet add package Ageledger --prerelease

Repo: https://github.com/ageledger/ageledger

It's a preview. It has been run on one iPhone with the sandbox account and an Android phone, and the README lists exactly what isn't verified yet. It doesn't make an app compliant with anything, and it isn't legal advice. I'd like to hear whether it fits how your apps work, and what's missing.


r/dotnetMAUI • • 19d ago

Discussion Layoff buyout impact?

12 Upvotes

What impact will Microsoft’s layoffs and early retirements have on .NET MAUI?

With all the recent layoffs and early retirements at Microsoft, I’m becoming increasingly concerned about the long-term future of .NET MAUI.

I’m about to start a significant new project, and frankly, I’m nervous about committing substantial time, money, and development resources to a platform whose future may be uncertain.

Is Microsoft still fully committed to .NET MAUI? Have key members of the development team been affected? What does this mean for future development, support, and investment?

I’m now seriously considering Flutter instead. While I’d prefer to stay within the .NET ecosystem, I don’t want to spend the next year building an application only to find Microsoft has shifted its priorities or scaled back support.

For those actively developing with .NET MAUI, would you still choose it for a major new project in late 2026, or would you go with Flutter?

I’d particularly appreciate hearing from developers who have experience with both platforms, as well as anyone with insight into Microsoft’s long-term commitment to MAUI.


r/dotnetMAUI • • 19d ago

Help Request Accessing built-in barcodescanner

4 Upvotes

Hi first time poster here.

I'm a seasoned developer in the .NET space, but never have done anthing MAUI related, although I understand the concept and read that there are ways to access platform specific hardware like e.g. cameras.

We have some of those devices in our company

https://www.newlandaidc.com/en/products/Full-touch/MT90.html

But how would you access the built-in barcodescanner in MAUI?

Thanks for any input.


r/dotnetMAUI • • 20d ago

Discussion How are you handling the new app-store age laws (Texas SB 2420 etc.) in MAUI apps?

6 Upvotes

Texas (SB 2420) is in effect (since June, while the appeal continues), and Utah, Louisiana, Alabama and California have similar app-store age laws coming in 2027. Google now has the Play Age Signals API and Apple has Declared Age Range (iOS 26), plus newer iOS 26.2/26.4 calls for regulatory features and "significant update" acknowledgments.

For those shipping .NET MAUI apps to the US stores:

  1. Are you doing anything about this yet, or waiting to see how enforcement goes?

  2. If yes: calling the platform APIs directly, using a NuGet package, or something else?

  3. Anything that's been a pain: the iOS side (Swift-only API), testing it, the newer iOS 26.2/26.4 calls, or keeping some record of what your app decided?

Not looking for legal advice, just how other teams are approaching it in practice.


r/dotnetMAUI • • 25d ago

Discussion Play Console says "you've not uploaded debug symbols". Anyone fixed this?

4 Upvotes

My .NET MAUI app (.NET 10, Android Release build with AOT and R8) gets this warning on every upload:

This App Bundle contains native code, and you've not uploaded debug symbols. We recommend you upload a symbol file to make your crashes and ANRs easier to analyze and debug.

Every native lib in the .aab comes from .NET itself (libmonosgen, libmonodroid, the libaot-*.so files) or from SQLite, and they arrive already stripped. The only unstripped file the build leaves is libxamarin-app.dbg.so in obj/. I found the open issue (https://github.com/xamarin/xamarin-android/issues/8903), but no official fix. Has anyone made the warning go away, or do you just ignore it?

Second question: this is how I catch crashes. I hook AppDomain.CurrentDomain.UnhandledException and TaskScheduler.UnobservedTaskException and send the message and stack trace to GA4 as an event (Measurement Protocol, a fire-and-forget HTTP POST). Is this a reasonable setup? Should I also use AndroidEnvironment.UnhandledExceptionRaiser, or save the crash to a file and send it on the next launch?

Thanks!


r/dotnetMAUI • • 28d ago

News TMS .NET Maps open beta: one map control for WinForms, WPF, .NET MAUI and Blazor

Post image
9 Upvotes

r/dotnetMAUI • • 29d ago

Discussion Thoughts on using AI to build native Android/iOS apps from a long time Xamarin.Forms and MAUI developer

13 Upvotes

I've been shipping apps built with Xamarin.Forms since 2021, and switched over to MAUI soon after it was generally available. I really love that I can have one codebase in C#, my primary language, to create both Android and iOS apps.

A few months ago I bought I bought a Claude Pro subscription to mess around, and more recently I figured I'd test a small proof of concept Android app using Kotlin just to see how capable it really is. I'm quite floored at how good AI has become. The technology has become SO good. Within one month I now have a fully functioning native Android app in Google Play store closed testing. The app itself performs better than any .NET MAUI app I've built and startup time is near instant. The bundle is way smaller as well. This is all understandable and expected since Kotlin is native.

This has me questioning whether I should continue to invest my time with .NET MAIU development. It's a very capable framework and I recognise that Microsoft is really trying to push it and improve on it, but I feel like it's always a step behind. There's always bugs to resolve, workarounds you need to implement, missing APIs, etc. With every release from Microsoft, we get bug fixes but also new bugs. This is not to put blame on Microsoft though, it's just the nature of such a ambitious project that MAUI is. A bug chunk of my own development time on any MAUI app is spent on battling the framework rather than coding the app features and I feel this will always be the case.

I'm curious to hear what other MAUI developers think of AI which now lowers the barriers to entry on native moble app development, and bypases all the bottlenecks of cross-platform development. I'm planning to use Claude for all my future mobile app development after seeing how good it really is.


r/dotnetMAUI • • 29d ago

Showcase NativeChannels

Post image
5 Upvotes

Hello everyone! :wave: I created NativeChannels, a NuGet package that makes native integration easier in .NET MAUI.

It connects C# with Kotlin, Swift, and Windows APIs through typed calls, event streams, and embedded native views—without needing a separate C# binding for every native method.

I also used it to build ImageCropper, a native image-cropping package for .NET MAUI. Check it out for an example of what you can build with NativeChannels!

It’s currently in preview, and I’d love to hear your feedback!

https://www.nuget.org/packages/NativeChannels.Maui

https://almis90.github.io/native-channels/

https://github.com/Almis90/native-channels

https://github.com/Almis90/image-cropper


r/dotnetMAUI • • Oct 17 '26

Discussion A few MAUI accessibility gotchas I found by scanning running apps (and the free tool I built for it)

5 Upvotes

Hi, I'm the developer of Swipewalk, a free scanner that checks running Android/iOS apps for accessibility issues. While building and testing it on MAUI apps, a few MAUI-specific things kept coming up that I think are worth sharing:

  1. Page.Title isn't an Android accessibility pane title. On Android the title shows in the toolbar, but MAUI doesn't set the pane title from it. Android also has a separate window title that TalkBack can announce, so check with TalkBack whether a screen name is announced when the page changes.

  2. Changing the font size on Android can send you back to the first screen. The default MAUI MainActivity doesn't handle font scale changes, so Android recreates the activity, and the template App.CreateWindow builds a new AppShell. A user who bumps up their text size mid-flow loses their place. Adding ConfigChanges.FontScale avoids the restart, but then the text doesn't grow until the app is relaunched, so it isn't a real fix on its own.

  3. Headings are almost never set. Unless you set SemanticProperties.HeadingLevel, nothing on the page is a heading, and screen reader users rely on headings to jump around a page.

  4. Text that looks fine at normal size can disappear at 200%. On a small phone, controls at the bottom of a page without a ScrollView get pushed off the screen at large text, and on a Pixel 4a I couldn't reach them at all. Worth wrapping long pages in a ScrollView.

These are easy to miss until the app is running, which is why I built a scanner for the running app instead of the XAML. It reports WCAG 2.2 issues with screenshots and who's affected, shows a predicted screen reader transcript (plus real TalkBack speech on Android and Accessibility Inspector data on iOS), rescans at large text, and gives MAUI fix examples. Automated checks only catch part of the issues though, so manual testing is still needed. I've only run it on Macs so far. I built it with a lot of help from AI coding assistants; I review and test what ships.

Free to use, runs locally: https://github.com/swipewalk/swipewalk/releases (what it found and missed in testing: https://github.com/swipewalk/swipewalk/blob/main/docs/testing.md)

Have you run into other MAUI accessibility quirks? I'd like to add checks for them.