41–50 of 107 posts
Earlier quoted context omitted.
Any plan to also support Windows 8 in Xamarin Forms ? This would allow the same level of cross platform-ness for tablets. Great work !
We don't have a firm date, but adding support for Windows tablets is on the roadmap. It will come in the form of Universal app support.
Earlier quoted context omitted.
Xamarin.Forms is designed to work with MVVM and data bindings: http://xamarin.com/forms
Thanks Nat! That's awesome news. To what extend is XAML support in Xamarin.Forms? Can I use it to create multiplatform controls/views?
Xamarin.Forms supports all of XAML 2009 and uses the XAML syntax with its own namespace and types. So, no existing XAML designer will work with Xamarin.Forms. However, the names and properties should be familiar to any experienced XAML developer.
Kind of amazing that Xamarin now seems to have better dev tools for iOS than Apple do. I was badly burnt by buying a Xamarian dev license a couple of years ago for $499 then not using it (my own fault entirely) so I've been hesitant to jump back in to Xamarin-world, but it's really only a matter of time. I'm very impressed.
I have been working with Xamarin stuff for a couple years now, released about 7 apps with them and honestly cannot imagine another approach. I mainly work with smaller startups in specific line of business scenarios and it has become a necessity to not only have viable mobile offerings, but they have to have parity across platforms and support both phone and tablets. When I go into a sales meeting and pitch the idea…
We built Xamarin.Forms because we have lots of enterprise customers building apps with a dozen or more screens doing simple things like tabular data display and data entry, but who have a native UI requirement in their app. Xamarin.Forms should make these types of apps much easier to write quickly.
Kind of amazing that Xamarin now seems to have better dev tools for iOS than Apple do. I was badly burnt by buying a Xamarian dev license a couple of years ago for $499 then not using it (my own fault entirely) so I've been hesitant to jump back in to Xamarin-world, but it's really only a matter of time. I'm very impressed.
Looks cool, but why translate to native UI elements at run-time as opposed to compile-time? Does it help with debugging? Forgive my ignorance as I have not used Xamarin.
I read this as "we allow design in our forms library, but compile to native controls for use at runtime."
It took me a couple reads to come to that conclusion, I was also confused by the wording. If that is not the case, I definitely have the same question as you. Perhaps the page could use some clarification.
Now all they have to do is make it free. Seriously though, as a student I can't shell out $299 for a license and even at the $99/year student rate (with proof of relevant course work), I can't see myself paying $99/year to write/maintain apps I've built. Especially considering the $99/year Apple app store fee. Please, Xamarin, show us young C# devs some love! update: not really sure why the down votes. I'm big fan of…
I agree. It's a great product, but $300 per year is cost prohibitive for me.
Looks great, love designer and Forms sounds epically wonderful (wonder if I can export my ios designs to forms for easier porting :-) ) First ten minutes experience: I've got a little weirdness with the differences in generated code from x-code vs new designer (an outlet name went from upper case to lower for instance). iOS designer is giving prominent error "Custom components are not being rendered because problems…