I build cross-platform mobile apps with .NET MAUI and Flutter.
8+ yrs: Xamarin → MAUI migrations, offline SQLite sync, Azure DevOps CI/CD, store releases.
Now shipping a US community-care app.
Code: https://t.co/bWnOzxWUjU
Open to remote roles & freelance work. DMs open.
@dotnetmaui Good to see LiveCharts2 getting MAUI support. The thing I'd want to know before it goes into a Release build: how it behaves with a few thousand points on a low-end Android device. Has anyone benchmarked scroll/zoom there?
@dotnetmaui AppThemeBinding covers most of it, but the one that always bites me is a page that already rendered — changing the system theme mid-session. Do you handle that with RequestedThemeChanged, or does AppThemeBinding re-evaluate on its own now?
@FlutterDev The line that's easy to skim: 'rebuild your apps.' For anyone maintaining a few client apps that's a full re-release through store review on each one. Does cert pinning cover you here, or does the compromised intermediate still get through?
Wednesday opinion: Flutter's eMudhra fix needed every app rebuilt and re-shipped. MAUI leans on the platform trust store, so Android patches it for you.
Bundling gives you consistency. Delegating gives you free security fixes. I'll take the free fixes.
Which side are you on?
@GauravBrief@rodri_shema Same path here — backend C# first, then cross-platform. The jump that took me longest was offline-first: SQLite sync and conflict handling is a different mindset from just calling an API. Happy to compare notes if you hit that stage.
@FlutterDev The part teams skip most: the API key never belongs in the client. Every "temporary" on-device key I've seen survived into production. A thin backend proxy also gives you per-user rate limits, which quotas alone can't. Solid checklist.
@dotnetmaui Looking forward to it 🙌 Hoping the startup numbers cover low-end Android too — that's where a lot of our users actually live. Happy to run RC2 vs RC1 on a physical mid-range device and share what I get, if a field data point helps.
@FlutterDev Hybrid Composition++ by default is the headline for me — platform views on Android have been the one place I'd warn clients about jank. Has anyone tested it with a heavy map or webview embed yet?
@dotnetmaui This one bit us. The scene lifecycle change is easy to miss because the app still builds fine — it only shows up at runtime on a real device. Good to see an official migration guide instead of piecing it together from GitHub issues.
MAUI 11 RC2 and Flutter 3.50 beta in the same week — both release notes about startup time and rendering.
8 years in, my honest take: the framework rarely decides the project. Your team's existing language does. Pick the one you can debug at 2am.
Which are you shipping on?
Developer here who some weeks reads more than he codes 📚
One book that changed how I work: The Pragmatic Programmer
One book that changed how I think: Atomic Habits
What's your pair?
@FlutterDev Stable 1.0 is when I start considering it for client apps. Is there a recommended pattern for keeping Gemini keys server-side when the client is a Flutter mobile app?
@FlutterDev 1 engineer, 3 legacy codebases is the real headline. Streams + bloc are a great fit for multiplexed telemetry. Backpressure is usually where these setups get tricky, would love to read how they handled it.
@dotnetmaui Does DevFlow's profiling cover startup and trimming too, or mostly runtime? `maui ai init` setting up agent skills is a nice touch, will try it this week.
@dotnetmaui 100% this. So many "slow pages" turn out fine in a Release build on a real mid-range Android. Debug + emulator lies. Release, real device, dotnet-trace, then optimize.
@FlutterDev Guard clauses made my state handling so much cleaner: case Loaded(:final items) when items.isEmpty => EmptyView() reads far better than nested ifs.
@mauiday Startup time on low-end Android is still what our users notice most. Curious if the MAUI 11 changes help apps with heavy XAML pages and SQLite on launch. Will the talk be recorded?