@@jfversluis Hi gerald...is it true the deployment method of .net maui app only via store...?...is it possible just copy the release folder then paste it into another win 10 machine then run it ?
@@jfversluis hi gerald...could you find for me about it from a valid source ???...please..🙏🙏🙏....because i have plan to create big enough project when .net maui is released....
So far I have managed to successfully develop Xamarin Forms apps without using Shell, I assumed Shell was there to abstract things away but with MAUI coming along would I be best to look into incorporating Shell into those apps and any new ones?
The thing is Shell uses all kinds of things that Xamarin.Forms provides. So if it’s not available in Forms it doesn’t work in Shell. Like you said; Shell is an abstraction, just like Forms is. If you don’t have any need for it or you don’t see the value, you certainly don’t have to use it, if you like using it and you can build your app with all it does, it can make your life easier and you should definitely use it! I think you should just have a play with it and see how it treats you :)
Does .NET MAUI include measurement and layout management for Android or does it let the Android do it's own measurement and layout management? In Xamarin.Forms this management causes a lot of performance degradation
I think the team is very aware of this and will improve that for .NET MAUI. I'm not entirely clear on the answer. Maybe you could open an issue or discussion on the repository :)
So you said 100ms and the slide says 1000ms. As someone who dropped xamarin due to slow tti, I'm curious to know which it is you're shooting for for forms. 1 full second seems a bit weak considering xam android seems to load cold in something like 100-400ms on a 5 year old phone so 100ms seems optimistic (for forms) and 1 second seems way too slow (still).
I think it's supposed to be 1000ms. And Xamarin.Android between 100-400ms, are you sure? Because this blog post seems to indicate otherwise: devblogs.microsoft.com/xamarin/faster-startup-times-with-startup-tracing-on-android/ It can't get below 1000ms with startup tracing. If personally feel below 1000ms is a pretty good target, but ultimately everyone has to decide for themselves what is the best solution for the task at hand :)
@@jfversluis Ah, ok. Maybe that's talking about xamarin forms which is slow, 2s even is optimistic for it. xamarin android starts up pretty fast, at least on fairly good hardware and a very lean minimal app (with startup tracing though i'm not sure how much that helps).
@@LostRoaming I'm pretty sure het is talking Forms here in context of .NET MAUI :) but then it's a nice aim to go sub 1 second, right? At least there is a focus on it which is good. We'll have to see by the time we can get to use this how good they've done.
I'm not entirely sure... But I know there will be big improvements in that area. Did you already also check out PancakeView and Sharpnado to use that today?
Make sure to check the repo of that issue exists and make your voice heard there. That is the thing they are looking for feedback and basing their work on!
The first thing that .Net Maui needs to do is support Data Annotations for validations instead of this complicated "behaviors" mess. That would go along way to promote code sharing across Server, Web (with Blazor), and Mobile.
Will Xamarin 5 released as part of .NET 5 already be integrated into .NET? Or will it still be using Mono? I ask because I have several .NET Core libraries that I would like to be able to use in Xamarin and the slides seem to imply that this will only become possible from Maui and .NET6 onward.
Are we going to getting rid of custom renderers for ui design ? I mean lot of effort has been put by a developer to customize a control ! Can we see some improvements for these in MAUI ? Ex: rounded entry , bordered entry, bordered picker etc , i use entry inside frame for these scenarios . Prefix and suffix icons and gestures for those in entries ..etc we need custom renderers.. can we expect any changes here. Becoz i think a dev has to learn xamarin.android and xamarin.ios before to do these stuff in xf
The renderers are going to change, but they are working to make it as backwards compatible as possible. The concept of renderers will still be there though and I'm expecting that you can still hook into that to make customizations that way.
I'm not sure about the SVG/PDF, have a look at the repo for issues and proposals: github.com/dotnet/maui for the tintable, that is in the Xamarin Community Toolkit: github.com/xamarin/XamarinCommunityToolkit/pull/516
I think at the moment it’s as simple as enough work to do as it is :) let’s first get iOS, Android, UWP and macOS up and then let’s see what might happen!
David, for having 2 adult/near-adult children you look great. You look like you could be a kid too. Great genetics or lifestyle? Please tell your secrets?
The support is there today, but it's maintained by the community. I think that won't change. There will be more focus on desktop with UWP and macOS, but I don't think Linux will be included in that yet, simply because it doesn't have that many users. I realize that it has not many users since the support isn't great, but there is only so much the team can do with all the platforms that are out there in the world today.
@@jfversluis i understand,this encourages me to become a contributor, i just want to compete with other frameworks like React native ...etc , anyways thanks man, keep developing awesome stuff :)
@@hqcart1 Ah ok, gotcha! Yeah so all the bare minimum bits to build cross-platform apps will be in .NET 5, but it won't be a pleasant experience, not at pleasant as it is today. A lot of supporting things (which he mentions) won't be in there until .NET 6 so that is why he is recommending to hold off. There is nothing stopping you from looking into it of course, but it might have some very rough edges.
I always felt the version I start the project with is more or less a commitment in order to not have compatibility problems, especially on large projects with many external dependencies. Sometimes new features are so desirable I cannot avoid updating. Keeping updated with Xamarin, 3rd party NuGet packages etc has often lead me to unbuildable projects. There are undoubtedly more pros than cons in using Xamarin and I’m a big fan of what you do!
@@maurosampietro9900 I totally understand what you mean. There are a lot of reasons why that is so but it's unfortunate. I know the team (and teams, like tooling etc.) are working hard to make this better. And while we would want you to always use the latest stuff there is nothing wrong with fixing your app to a version, at least within reasonable limits, if you are working to get a production release out. If you run into anything, please reach out, I'll be happy to help! Thank you for the kind words!
Personally I don't think this is anything like Silverlight :) but that is a choice only you can make, I hope you will find a technology that is right for you!
Please add official GNU/Linux support for GUIs with .NET MAUI. Xamarin Roots were mono and to create .NET support for Lunux. Xamarin Studio -> Linux... then fork to Visial Studio for Mac, no Linux anymore... This is methodical discrimination, I will drop .NET when that's not coming no later than .NET 7., I waited long enough. Can't develop for that platform that doesn't include my own OS. And Linux is free and open source, One Linux version, then potentially everyone in the universe could install it and use a program written for it. Please save .NET. 🙏🥺 Then it would be real cross-platform, real one platform, for everything. When supporting e.g. GTK/qt/blazor/skia and Linux, and already Mac, FreeBSD and OpenBSD support is nearly free on top. Imagine you could create one project solution, which runs a gui on ALL platforms. Linux Desktop is an important platform, our whole company uses it, it's just great, just release MS Office for it too, then unlimited money whatever OS people are using is coming.
No official support (yet) but there is mention in the Docs, the community can contribute and make it work docs.microsoft.com/dotnet/maui/supported-platforms#additional-platform-support
Custom drop down template also a good thing to add in a drop down picker apart from tabbar and navigation bar
Make sure a suggestion for this is on the .NET MAUI repo!
Dude you had me at CLI and VS code. The single project stuff is amazing. You guys are doing a great job. you should get paid well.
That is going to be good, right? Writing Xamarin from VS Code 😍
@@jfversluis Hi gerald...is it true the deployment method of .net maui app only via store...?...is it possible just copy the release folder then paste it into another win 10 machine then run it ?
Where did you hear that? Sounds like not true to me. Even if it is, that is not a restriction coming from .NET MAUI
@@jfversluis hi gerald...could you find for me about it from a valid source ???...please..🙏🙏🙏....because i have plan to create big enough project when .net maui is released....
@@wisnu7734 You're telling me you heard it somewhere, I did not, so if you can tell me I can go check. Else there is not much I can do right now :)
So far I have managed to successfully develop Xamarin Forms apps without using Shell, I assumed Shell was there to abstract things away but with MAUI coming along would I be best to look into incorporating Shell into those apps and any new ones?
The thing is Shell uses all kinds of things that Xamarin.Forms provides. So if it’s not available in Forms it doesn’t work in Shell. Like you said; Shell is an abstraction, just like Forms is.
If you don’t have any need for it or you don’t see the value, you certainly don’t have to use it, if you like using it and you can build your app with all it does, it can make your life easier and you should definitely use it! I think you should just have a play with it and see how it treats you :)
Does .NET MAUI include measurement and layout management for Android or does it let the Android do it's own measurement and layout management? In Xamarin.Forms this management causes a lot of performance degradation
I think the team is very aware of this and will improve that for .NET MAUI. I'm not entirely clear on the answer. Maybe you could open an issue or discussion on the repository :)
@@jfversluis Thanks
So you said 100ms and the slide says 1000ms. As someone who dropped xamarin due to slow tti, I'm curious to know which it is you're shooting for for forms. 1 full second seems a bit weak considering xam android seems to load cold in something like 100-400ms on a 5 year old phone so 100ms seems optimistic (for forms) and 1 second seems way too slow (still).
I think it's supposed to be 1000ms. And Xamarin.Android between 100-400ms, are you sure? Because this blog post seems to indicate otherwise: devblogs.microsoft.com/xamarin/faster-startup-times-with-startup-tracing-on-android/ It can't get below 1000ms with startup tracing. If personally feel below 1000ms is a pretty good target, but ultimately everyone has to decide for themselves what is the best solution for the task at hand :)
@@jfversluis Ah, ok. Maybe that's talking about xamarin forms which is slow, 2s even is optimistic for it. xamarin android starts up pretty fast, at least on fairly good hardware and a very lean minimal app (with startup tracing though i'm not sure how much that helps).
@@LostRoaming I'm pretty sure het is talking Forms here in context of .NET MAUI :) but then it's a nice aim to go sub 1 second, right? At least there is a focus on it which is good. We'll have to see by the time we can get to use this how good they've done.
Will we get all type of property like shadows, corners radius, border colour etc.. in all controls in MAUI
I'm not entirely sure... But I know there will be big improvements in that area. Did you already also check out PancakeView and Sharpnado to use that today?
@@jfversluis I used those controls, but the main change that I am expecting in MAUI is this one
Make sure to check the repo of that issue exists and make your voice heard there. That is the thing they are looking for feedback and basing their work on!
@@jfversluis sure
did things change a lot from whats showing in this video?
Like what things?
The first thing that .Net Maui needs to do is support Data Annotations for validations instead of this complicated "behaviors" mess. That would go along way to promote code sharing across Server, Web (with Blazor), and Mobile.
That would be a great addition indeed. Moving this to be a first-class .NET citizen is going to open up a lot of possibilities!
Will Xamarin 5 released as part of .NET 5 already be integrated into .NET? Or will it still be using Mono? I ask because I have several .NET Core libraries that I would like to be able to use in Xamarin and the slides seem to imply that this will only become possible from Maui and .NET6 onward.
Never mind, at the end this gets addressed.
Glad you found the answer! :D
Are we going to getting rid of custom renderers for ui design ? I mean lot of effort has been put by a developer to customize a control ! Can we see some improvements for these in MAUI ?
Ex: rounded entry , bordered entry, bordered picker etc , i use entry inside frame for these scenarios . Prefix and suffix icons and gestures for those in entries ..etc we need custom renderers.. can we expect any changes here.
Becoz i think a dev has to learn xamarin.android and xamarin.ios before to do these stuff in xf
The renderers are going to change, but they are working to make it as backwards compatible as possible. The concept of renderers will still be there though and I'm expecting that you can still hook into that to make customizations that way.
Will MAUI support uniform vector graphics for all plattforms? (svg/pdf)
Also will images/icons be tintable?
I'm not sure about the SVG/PDF, have a look at the repo for issues and proposals: github.com/dotnet/maui for the tintable, that is in the Xamarin Community Toolkit: github.com/xamarin/XamarinCommunityToolkit/pull/516
Might be indirectly. The there is blazor bindings in experimental. Then you could do a blazor component, that utilize svg
Will MAUI support web ?
I don’t think that will be the primary focus. Sorry :(
@@jfversluis ok thanks 🙏
What desktop framework does MAUI target on windows platform...is it UWP or WinUI 3.0?
Looking at GitHub.com/dotnet/Maui it doesn’t specify it (yet) so maybe still to be decided :)
@@jfversluis Hope UWP because of mobile smooth and fluent animation UI
@@clintersplay443 as soon as there’s news I will post a video about it here :)
is this framework fully open source?
Just like Xamarin.Forms, it is/Will be :)
Why not Linux?
I think at the moment it’s as simple as enough work to do as it is :) let’s first get iOS, Android, UWP and macOS up and then let’s see what might happen!
David, for having 2 adult/near-adult children you look great. You look like you could be a kid too. Great genetics or lifestyle? Please tell your secrets?
😄 I have wondered that a couple of times myself. I know he likes some good beers. But that doesn’t seem to help me one bit 🤷♂️
we need it on linux please
The GTK backend is there, but I don’t think it will get official support though :(
@@jfversluis why not ?
The support is there today, but it's maintained by the community. I think that won't change. There will be more focus on desktop with UWP and macOS, but I don't think Linux will be included in that yet, simply because it doesn't have that many users. I realize that it has not many users since the support isn't great, but there is only so much the team can do with all the platforms that are out there in the world today.
@@jfversluis i understand,this encourages me to become a contributor, i just want to compete with other frameworks like React native ...etc , anyways thanks man, keep developing awesome stuff :)
I understand! I will be adding more stuff on contributing to OSS and the Xamarin repos so keep your eye out for that :)
is this similar to SwiftUI?
If you’re talking about the MVU part, that is definitely inspired by SwiftUI and Flutter
All sounds good 😀
It. does, right?! Can't wait!
You said do not use .net5 for mobile development, Why?
Where is that said? And maybe because .NET MAUI won’t land until .NET 6?
@@jfversluis @47:35
@@hqcart1 Ah ok, gotcha! Yeah so all the bare minimum bits to build cross-platform apps will be in .NET 5, but it won't be a pleasant experience, not at pleasant as it is today. A lot of supporting things (which he mentions) won't be in there until .NET 6 so that is why he is recommending to hold off. There is nothing stopping you from looking into it of course, but it might have some very rough edges.
The ‘build and resolve issue’ part scares me.. a lot..
Understandable, I think there might be some (good) news incoming about that. But either case, I think it will be fine and not that hard!
I always felt the version I start the project with is more or less a commitment in order to not have compatibility problems, especially on large projects with many external dependencies. Sometimes new features are so desirable I cannot avoid updating. Keeping updated with Xamarin, 3rd party NuGet packages etc has often lead me to unbuildable projects. There are undoubtedly more pros than cons in using Xamarin and I’m a big fan of what you do!
@@maurosampietro9900 I totally understand what you mean. There are a lot of reasons why that is so but it's unfortunate. I know the team (and teams, like tooling etc.) are working hard to make this better.
And while we would want you to always use the latest stuff there is nothing wrong with fixing your app to a version, at least within reasonable limits, if you are working to get a production release out. If you run into anything, please reach out, I'll be happy to help!
Thank you for the kind words!
I Assumed you were 30 at the most!
I still suspect he is some kind of vampire that doesn't age...
Me recuerda a Silverlight.. así que no gracias luego lo van a descontinuar
Personally I don't think this is anything like Silverlight :) but that is a choice only you can make, I hope you will find a technology that is right for you!
Please add official GNU/Linux support for GUIs with .NET MAUI.
Xamarin Roots were mono and to create .NET support for Lunux.
Xamarin Studio -> Linux...
then fork to Visial Studio for Mac, no Linux anymore...
This is methodical discrimination, I will drop .NET when that's not coming no later than .NET 7., I waited long enough.
Can't develop for that platform that doesn't include my own OS.
And Linux is free and open source, One Linux version, then potentially everyone in the universe could install it and use a program written for it.
Please save .NET. 🙏🥺
Then it would be real cross-platform, real one platform, for everything.
When supporting e.g. GTK/qt/blazor/skia and Linux, and already Mac, FreeBSD and OpenBSD support is nearly free on top.
Imagine you could create one project solution, which runs a gui on ALL platforms.
Linux Desktop is an important platform, our whole company uses it, it's just great, just release MS Office for it too, then unlimited money whatever OS people are using is coming.
No official support (yet) but there is mention in the Docs, the community can contribute and make it work docs.microsoft.com/dotnet/maui/supported-platforms#additional-platform-support