Blazor app happens to be new. It is so new that it is just a beta preview in the most recent .NET Core version. The initial release of Blazor has been scheduled for May this year.
However, despite this innovativeness, Microsoft is planning Blazor’s future already. Microsoft, in their latest .NET Conf event, has revealed plans which might bring Blazor to native applications. For a platform that is already taking over the whole JavaScript world, this is an optimistic plot twist. However, it could just work for devoted developers of .NET.
The Universal UI Quest
.NET developers are vying for a way of creating a cross-platform user interface for ages. This implies being able to create a single front end in a dream fantasy environment that fits with web, desktop as well as smartphone applications.
The most advanced desktop development toolkit of Microsoft and its solution for Native mobile app development are similar in design. The user interface is specified employing the XAML markup standard. Both rely on linking data and supporting the MVVM pattern. However, there are issues, despite these similarities. WPF has closely related to DirectX as well as the Windows operating system’s other core components. And even though WPF and Xamarin merged, the XAML-based user interface and the HTML markup on the site are unacceptable.
There have been attempts to fix the issues, but the official aspect of the platform funded by Microsoft is nothing. Google’s got its toolkit named Flutter. However, Microsoft has a difference between smartphones, laptops, and online environments.
A Blazor Background
Here’s a fast recap in case you’re not up to Blazor app yet: Blazor happens to be the name for a couple of different technologies that allow you to build browser-based apps running .NET code.
The initial – and a little advanced – is Blazor Server technology, which acts like an old-fashioned console. The browser is in continuous touch with the web server, which is running the .NET code.
The server just returns updated HTML bits, so that after every single event the browser is going to refresh the page. Blazor WebAssembly is the second software that smuggles a small .NET runtime into the application and that is used to run code # rather than JavaScript. This happens to be the Blazor app which has generated all the enthusiasm.
Suppose Blazor WebAssembly gets its full release and is doing everything it says on the tin — i.e., offering .NET developers a technique of running C# in their browsers. This is pretty impressive. Where should Blazor go next, however? Microsoft continues to indicate that many of its experimental ventures are no longer just trials. The first instance happens to be Blazor desktop apps.
Learn more here: https://www.rlogical.com/blog/native-apps-is-the-future-of-blazor/
Top comments (0)