MobileBlazorBindings VS gallery

It's difficult to imagine. But if the rumour has any merit, perhaps it simply means that there will be a push to consolidate on some blazor tech using stuff like https://github.com/dotnet/MobileBlazorBindings

There's Blazor Mobile Bindings but it's essentially experimental at the moment and isn't exactly active. From playing around with it though, it is pretty neat as you get the Blazor programming model but with native controls.

The benefit at least with the approach instead of embedding Avalonia inside Maui is you could potentially use non xaml frameworks for ui as long as they support Maui as a target. Stuff like Comet or Blazor mobile bindings would be possible aside from xaml. Especially if they're coming from Blazor web or code based ui frameworks like flutter which makes it appealing.

This is one reason I'd really love for them to push through on making alternatives to XAML like Blazor mobile bindings.

I'd say Blazor mobile bindings is also pretty interesting imo, unlike Hybrid it doesn't use Html and uses MAUI controls directly but still keeps the Blazor programming style and still uses razor to tie in C# and components.

Oleksandr has been contributing to the official experiment project, and singlehandedly updated it to support .NET MAUI. He even now has documentation on his fork.

I really hope Blazor Mobile Bindings takes off imo. I still care for native controls and if Mobile bindings does become a valid target, then you'll have an alternative to XAML when writing native components but using Razor syntax (which imo is less verbose). It'll be like how React does it (which is still pretty popular) where you have React web and also React Native which uses the platform's native controls underneath. Both aren't exactly the same but since the framework is similar (React, Blazor) it should be easy to swap between the two.

Yeah I really hope they'll productize Blazor Mobile Bindings (currently experimental), it's essentially using Xaml controls via Razor as the markup format instead and can use C# expressions (so less need for converters).

For example, in Android there's this file: https://github.com/dotnet/MobileBlazorBindings/blob/main/templates/BlazorHybrid-app/NewApp.Android/wwwroot/index.html

It means you can use Blazor's syntax to write MAUI apps, as an alternative to XML-like XAML syntax.

I was pessimistic about flutter 4 years ago but rechecked it recently (learning right now) and IMO it's really good user/developer proposition these days. They resolved most of issues on mobile devices and desktops - only web version still off but once wasmGC is ready (hopefully this year) probably things will improve.

Best way for developer elevator pitch just download few flutter apps and see how you like the experience:

1. wonderous - https://flutter.gskinner.com/wonderous/

2. flutterflow (low code + gui editor for flutter) - https://https://flutterflow.io/

3. appflowy (notion alternative) - https://appflowy.io/

4. flutter gallery (official flutter kitchen sink) -

Android (Google Play Store, .apk) - https://play.google.com/store/apps/details?id=io.flutter.dem...

web (gallery.flutter.dev) - https://gallery.flutter.dev/

macOS (.zip) - https://github.com/flutter/gallery/releases/latest

5. official material 3.0 demo - https://flutter.github.io/samples/web/material_3_demo/#/

I recommend to checkout and play with material 3.0 demo (just keep in mind this is web version will have even better when using native compiled version on mobile or desktop):

https://flutter.github.io/samples/web/material_3_demo/#/

4) Try web flutter gallery to see numerous app samples (more complex) and widgets

https://gallery.flutter.dev/#/

again even better to download mobile or desktop version that there is in app store:

play store: https://play.google.com/store/apps/details?id=io.flutter.dem...

macos dmg (.zip): https://github.com/flutter/gallery/releases/latest

I tried both macos flutter gallery and on iOS and surpassingly is pretty good these days and smooth and feel native - even text selection works these days, moving cursor with long press on keyboard space etc. Occasionally was more difficult to dismiss keyboard on iOS and back/next mouse keys or touchpad gestures didn't work on macOS flutter gallery. But overall I'm quite satisfied and surprised comparing how it looked 4 years ago.

I remember the first time when I looked at the Flutter Gallery and was surprised at how things felt just broken in a web browser, for example: https://gallery.flutter.dev (I think it was the Reply example in particular)

Ctrl + click or middle mouse button didn't work on links, right click didn't work, selecting and copying text didn't work, inspect element didn't work (due to how the technology is built), even attempting to zoom the page did nothing.

This article does ring true both because of that experience, as well as some of the SPA implementations I've seen even with more conventional technologies.

Google Docs. Figma. Any Flutter app like https://gallery.flutter.dev/. Short answer, they're really not handling accessibility.

Even when you did that, scrolling was completely wrong. The web simply doesn’t expose primitives from which you can build native-feel scrolling, and the best you can manage on precise touchpads (that is, all laptops now) will normally feel terrible, and lack things like inertia which are rather important. https://gallery.flutter.dev/, for example, scrolls less than half as fast as it should, and lacks inertia. (… and renders text in the wrong font, and doesn’t do links at all where it obviously should, and uses scrollbars that behave all wrong quite apart from being overlay which my native aren’t, and get typing emoji wrong, and… and… seriously, it’s just a litany of awfulness.)

Oh wow. I had thought the claim that they were not producing any semantic web elements was almost certainly exaggerated. That said, for the number of things that are on https://gallery.flutter.dev/#/reply, there are a surprisingly low number of elements. Wow.

example: https://gallery.flutter.dev (and Flutter Gallery on the playstore)

You could just need to clear your cache, but I suspect might have something going on because of how you're loading your theme. Not sure about having two runapp functions. I would suggest inspecting gallery.flutter.dev and then implementing a splash screen the way they have, as you will get the benefit of having a slash while flutter is being loaded, vs a splash screen that won't start until after, which imho, defeats the purpose.