[pjmlp]

I guess it depends on how they see themselves.

For example I am not a C# developer, rather a developer.

I use whatever technology stack our customers require us to do. I change project almost every year.

So I can imagine some customers would have iOS only projects and in those cases I would try to push for Swift instead of Objective-C.

[UK-AL]

Most customers would want a solution where code can be shared with ios/android/Mac/PC. Xamarin allows that.

[pjmlp]

I am not speaking against it, just how I can see it happening.

On my case, enterprise customers actually went with Cordova for mobile multi-platform. On the few projects I took part on.

For my hobby projects so far I went with C++, as they tend to be small multimedia stuff and I don't feel like paying Xamarin for hobby projects I do with months interval and sometimes are left unfinished when life takes over.

So Native UI + C++ (now C++14) suits me better, although the NDK is a big pain to use and quite limited, but at least Windows Phone and iOS are nicer to use.

If I had to do it professionally on my own company, maybe Xamarin would be an option, specially since Qt seems to be way behind Xamarin in terms of device support.