J
Joshin95
Guest
I need to design an android and iOS app that at some point will need to be ported to a web page format. With this in mind I would like to ask what you guys think should be the right choice when it comes to the selection of tools that should be used. The project will be developed by a single developer, so code re-usability is a strong point here.
I have a long term experience with .NET platform from ASP do Xamarin, however I was not able to follow the latest updates of the platform for the last 2 years. With this in mind my first idea was to use Xamarin.Forms as a base for the app, and then Blazor for the web page while sharing the view models between the projects. Everything done in a MVVM architecture.
1- But then the question that comes to my mind is if there is some way to share as well the view part? After doing some research I saw that there is a possibility to define views in Xamarin.Forms, using Razor syntax. Does that mean that writing an Xamarin.Forms app with views defined in HTML, I can just recompile the resources with Blazor, and have a web page? Of course only in mobile mode, but still executed in navigator. The only work that would need to be done is to create a view representations that would suit the normal full size navigators?
2- Another question that comes to my mind is the fact of implementing everything in MVVM architecture, is there any solution that would help me to separate views and logic (like MVVMCross), and as well be compatible with both Xamarin.Forms and Blazor? Is the support of bindings the same in HTML as in XAML?
3- As well I would like to have some opinions about implementing the Backend of the app, I'm familiar with the ASP.NET Web API 2 but I saw that there are some products created for .NET environment like the Azure App Service which seems like a bundle created specifically for this purpose.
I would be glad to know your opinion about this questions.
Thanks,
Continue reading...
I have a long term experience with .NET platform from ASP do Xamarin, however I was not able to follow the latest updates of the platform for the last 2 years. With this in mind my first idea was to use Xamarin.Forms as a base for the app, and then Blazor for the web page while sharing the view models between the projects. Everything done in a MVVM architecture.
1- But then the question that comes to my mind is if there is some way to share as well the view part? After doing some research I saw that there is a possibility to define views in Xamarin.Forms, using Razor syntax. Does that mean that writing an Xamarin.Forms app with views defined in HTML, I can just recompile the resources with Blazor, and have a web page? Of course only in mobile mode, but still executed in navigator. The only work that would need to be done is to create a view representations that would suit the normal full size navigators?
2- Another question that comes to my mind is the fact of implementing everything in MVVM architecture, is there any solution that would help me to separate views and logic (like MVVMCross), and as well be compatible with both Xamarin.Forms and Blazor? Is the support of bindings the same in HTML as in XAML?
3- As well I would like to have some opinions about implementing the Backend of the app, I'm familiar with the ASP.NET Web API 2 but I saw that there are some products created for .NET environment like the Azure App Service which seems like a bundle created specifically for this purpose.
I would be glad to know your opinion about this questions.
Thanks,
Continue reading...