UNO Development
-
I'm curious if anyone has tried or [is using UNO](https://platform.uno/)? Thoughts / comments on it as a viable development platform.
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
-
I'm curious if anyone has tried or [is using UNO](https://platform.uno/)? Thoughts / comments on it as a viable development platform.
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
Kevin Marois wrote:
I'm curious if anyone has tried or is using UNO?
Hadn't heard of it before now. I tried the sample (https://raytracer-mono-aot.platform.uno/[^]) on a VM that doesn't have much RAM and it failed. Tried it on another machine and it worked (both on latest FireFox). I'd like to see the dev environment and try developing a small android app to give better evaluation. Looks interesting though.
-
I'm curious if anyone has tried or [is using UNO](https://platform.uno/)? Thoughts / comments on it as a viable development platform.
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
It depends upon how often you play[^], no?
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein
"If you are searching for perfection in others, then you seek disappointment. If you seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010
-
I'm curious if anyone has tried or [is using UNO](https://platform.uno/)? Thoughts / comments on it as a viable development platform.
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
I had a look at the getting started tutorial and it looks nice. I've done plenty of WPF apps so the ViewModel and XAML approach are familiar concepts. I'll definitely keep it in mind if I need to do a mobile app. I've had a look at other cross-platform / native frameworks like Flutter, but what I don't like about that one is that the views and code are mixed together and I need to learn another Language (Dart). Uno looks easier to get started with, at least for me.
-
I'm curious if anyone has tried or [is using UNO](https://platform.uno/)? Thoughts / comments on it as a viable development platform.
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
There's an implementation of the Windows 10 calculator done in Uno (called *Uno Calc") that I use all the time on Android. It serves as a technology demonstrator but more to the point is a great calculator!
-
I'm curious if anyone has tried or [is using UNO](https://platform.uno/)? Thoughts / comments on it as a viable development platform.
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
I spent a little time playing with it, decided it looked interesting/good enough to suggest to my boss we look into it. We went to Unoconf in Montreal together and drank the kool aid etc. Conceptually it is exactly what we want, and we wish Xamarin Forms had been more like this. Let me also say the work done/being done by the Uno team is amazing. However, after we got back from the conference we got some of my colleagues to work with it on actual commercial projects. We had one small Xamarin iOS app that needed an Android version, and another app that was UWP and also needed an Android version. Sadly I didn't get to work on these myself, they were mostly done by junior/intermediate devs and I, along with another senior colleague, helped guide them as much as I could in between our regular work. That means I'm not familiar with all the various problems we encountered - but there seemed to be a lot. We were successful in the end, the first app now has iOS, Android and UWP versions, the second app is UWP and Android (because that's all we need) and they work well enough from the user's point of view. Unfortunately it was a longer, harder road getting there than we hoped. Without going into too much detail, my personal opinion is that Uno currently feels like it's where Xamarin Forms was 4-5 years ago. There's a lot that isn't implemented (and you often can't tell at design time), each release is prone to breaking existing projects when you update the Nuget packages, and the tooling/code generation/build chain is fragile. That is not to say it's not usable or not valuable, and I'm certain the number & degree of problems you'll have will vary depending on the scope and complexity of your projects so YMMV. I also think we probably would have had a better time if we were building something from scratch rather than trying to port existing code. That said, one of the things we tried to port was a UWP app and the promise of 'write the UWP version and it just works on Android and iOS' definitely is there yet. At this point we are still betting on Uno for future cross platform dev in .Net, over Xamarin Forms etc, and are hoping that it will continue to improve and catch up to other more mature options. Certainly the Uno team seems to be working hard and moving fast. However talking to my colleagues they seem to have similar feelings to myself, they really want to like it but the experience they've had so far left them 'on the fence'. We also just struggled with another project we looked at due to a combination of stu
-
I spent a little time playing with it, decided it looked interesting/good enough to suggest to my boss we look into it. We went to Unoconf in Montreal together and drank the kool aid etc. Conceptually it is exactly what we want, and we wish Xamarin Forms had been more like this. Let me also say the work done/being done by the Uno team is amazing. However, after we got back from the conference we got some of my colleagues to work with it on actual commercial projects. We had one small Xamarin iOS app that needed an Android version, and another app that was UWP and also needed an Android version. Sadly I didn't get to work on these myself, they were mostly done by junior/intermediate devs and I, along with another senior colleague, helped guide them as much as I could in between our regular work. That means I'm not familiar with all the various problems we encountered - but there seemed to be a lot. We were successful in the end, the first app now has iOS, Android and UWP versions, the second app is UWP and Android (because that's all we need) and they work well enough from the user's point of view. Unfortunately it was a longer, harder road getting there than we hoped. Without going into too much detail, my personal opinion is that Uno currently feels like it's where Xamarin Forms was 4-5 years ago. There's a lot that isn't implemented (and you often can't tell at design time), each release is prone to breaking existing projects when you update the Nuget packages, and the tooling/code generation/build chain is fragile. That is not to say it's not usable or not valuable, and I'm certain the number & degree of problems you'll have will vary depending on the scope and complexity of your projects so YMMV. I also think we probably would have had a better time if we were building something from scratch rather than trying to port existing code. That said, one of the things we tried to port was a UWP app and the promise of 'write the UWP version and it just works on Android and iOS' definitely is there yet. At this point we are still betting on Uno for future cross platform dev in .Net, over Xamarin Forms etc, and are hoping that it will continue to improve and catch up to other more mature options. Certainly the Uno team seems to be working hard and moving fast. However talking to my colleagues they seem to have similar feelings to myself, they really want to like it but the experience they've had so far left them 'on the fence'. We also just struggled with another project we looked at due to a combination of stu
Thanks for the info
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.