News for hackers. Stuff that matters.
Re:Some thoughts after (almost) a year of real Xamarin use by forcer on Saturday April 04, 2015 @01:18PM (#9321421)
Great article, we have a similar story but only used Xamarin for 1 iOS app. If I had option to go back I would not chose Xa marin, we would have used native. Main reason being that we now need to add 3 SDKs to our app and none of them are supported in Xamarin, it seems it will be cheaper and more predictable to rewrite to native than implementing SDKs. Porting libraries to Xamarin is possible in theory but in practice major effort and hard to do without access to library code.
Re:Some thoughts after (almost) a year of real Xamarin use by natfriedman on Saturday April 04, 2015 @02:58PM (#9321791)
Hi there, I'm the CEO of Xamarin. I'm really sorry to hear that you had issues with consuming third-party libraries. This is actually something we've been recently very focused on improving.

First of all, in December we released a new tool called Objective Sharpie that can automatically bind Objective-C libraries into C#:

http://forums.xamarin.com/categories/ObjectiveSharpie

If you're skilled enough to build the Objective-C library, then you'll be able to use Objective Sharpie to create a C# binding. We also have docs on doing this for Java on developer.xamarin.com.

Some of our customers don't have the time or skill to do this themselves, and so we've recently created a bindings team that wraps third-party native libraries for our customers. Many of these end up published on http://components.xamarin.com/ (there are over 300 components now). But some of them we can't immediately publish because we need to get permission from the original library author to redistribute their library. This is especially true for commercial SDKs. But if you contact us directly, we might be able to give you something.

We also do custom bindings through our support team. This is something that unfortunately we haven't made very obvious. But you can just email [email protected] and we can create a binding for you.

Like I said, this is an area we're pretty focused on. If you have any feedback, please feel free to let me know directly: [email protected].

Re:Some thoughts after (almost) a year of real Xamarin use by saosebastiao on Saturday April 04, 2015 @06:22PM (#9322429)
ObjectiveSharpie is awesome! No problems so far.

But when are you gonna let us use Xamarin Studio on Linux?

Re:Some thoughts after (almost) a year of real Xamarin use by yulaow on Saturday April 04, 2015 @10:04PM (#9322878)
I fear never. We made this question over and over on the forums or via emails but the answer is ever the same: "we have no plans to support linux". Originally the problem was about "there are too many linux distros!", then when some people suggested to at least support ubuntu as Valve did (and correctly considering the big part of used distros are ubuntu based or related) they went again on "we have no plans to support linux" without futher explainations.
Re:Some thoughts after (almost) a year of real Xamarin use by tracker1 on Sunday April 05, 2015 @12:29AM (#9323115)
+1 on this... within a year, my main desktop OS will likely be Linux.. right now, I keep an Ubuntu VM in the background and edit in windows (Sublime) via Samba shares in the VM.. running via SSH terminal windows.. mainly because a significant amount of my time was windows dev.. this is shifting as I'm using node/io.js much more. This also means, however that I'm more likely to reach for something like Cordova for apps (you can go a long way with web based apps for many use cases) or React Native.
Re:Some thoughts after (almost) a year of real Xamarin use by mwcampbell on Sunday April 05, 2015 @10:16AM (#9324074)
What would be the point of developing with the Xamarin Platform on Linux? You'd only be able to target Android, not iOS, Mac, or Windows. In that case, one might as well not use Xamarin at all.

To target the full range of mobile devices, one has to have Windows, a Mac, or both anyway. So there doesn't seem to be much advantage to supporting development on Linux.

Re:Some thoughts after (almost) a year of real Xamarin use by saosebastiao on Sunday April 05, 2015 @11:08AM (#9324218)
The point would be to develop on a platform that I like developing on. Either way, there isn't a single platform that you can use that will give you 100% of the available platforms...if you want cross-platform across Android, iOS, Mac, AND Windows, you are going to need a minimum of two computers. Why not develop as much as possible on the one you like?
Re:Some thoughts after (almost) a year of real Xamarin use by badlogic on Saturday April 04, 2015 @01:31PM (#9321462)
I think this is the key to making a great cross-platform solution. Pretty much any mobile app that's not a toy relies on native 3rd party sdks, be it ad providers or fancy Ui compinents. Whatever platform first solves the issue of making integration of pods on iOs or AARs on Android a smooth process, will win.

I don't see any options that come close to solving this. Xamarin is not native to either iOS or Android. RoboVM (the one i work on) can cheat, as we only need to solve it for iOS, Android comes for free. React Native has no clear path for accessing 3rd party libs at all yet. Whatever they can come up with will be further complicated by the fact that the JS engine is single threaded.

Re:Some thoughts after (almost) a year of real Xamarin use by peterhunt on Saturday April 04, 2015 @09:26PM (#9322779)
Re:Some thoughts after (almost) a year of real Xamarin use by badlogic on Sunday April 05, 2015 @03:20AM (#9323392)
I stand corrected, I must have overlooked that section. Callbacks (used to pass return values) are still experimental though, and it's unclear how this will port over to Android once that backend works.
Re:Some thoughts after (almost) a year of real Xamarin use by deet on Saturday April 04, 2015 @02:31PM (#9321691)
My experience with third party libraries has been quite different, for the most part.

I've often been surprised at how easy it is to create bindings to libraries written in Obj-C even if no one else has before. Usually it requires extracting the compiled library from the framework, and then translating each declaration from the library's header into the C# binding definition. In many cases it's a couple of hours work (or less).

That said, libraries that are provided as source files, with the instructions "just copy them into your project," can be incredibly frustrating. Our designer would love to use github.com/MengTo/Spring but I have yet to find a way to use it in Xamarin easily.

Re:Some thoughts after (almost) a year of real Xamarin use by ianlevesque on Saturday April 04, 2015 @01:51PM (#9321555)
Bindings are actually not that bad with Objective Sharpie. What SDKs are giving you trouble? I would agree that for a single platform it is not worthwhile though.