Blazor Mobile Bindings

[6Hat]

First off I just want to say that I've moved from Php a few years ago to Asp.Net MVC and have absolutely loved it. This last year I've done some experimentation with Xamarin Forms... it's good... I know it's a personal thing as I've never been a fan of Xaml... but Xamarin is very well established and I've been able to so far accomplish everything that I need so far.

In the last few months I've just recently stumbled upon Blazor. My mind is blown with the possibilities, especially for PWA's... very exciting! Then when I heard about Blazor Mobile Bindings I couldn't believe it. Unfortunately while it is great that Blazor Mobile Bindings is being implemented... for some reason I had it pictured differently as to how it would work. If my understanding is correct it seems as if it is basically a Xamarin Forms app that you can code the UI out with HTML instead of Xaml... which is great don't get me wrong as like I said I am not a fan of Xaml. I can only imagine that this was not an easy feat to accomplish either, so I do not by any means want to discount the hard work put in... I would prefer this over Xaml.

I had in mind however the thought that it would basically be a PWA that had the capability of communicating with Native API's. In other words... don't render native controls leave the UI in Html... but create a layer that can communicate directly with the API's. I know that is worlds easier said then done... and I can only imagine the requirements and rules implemented by the different OS's that probably make that impossible... but really it seems that a lot of what is on the horizons this year with .Net 5 and even Blazor would have been impossible a few years ago... So why not add one more impossibility to the list!