2 ms·
I have built a lot of apps with Xamarin (and others like Intel XDK and it's predecessors); Xamarin has been the best experience for me so far. I don't mind Obje
by tluyben2 13y ago
I have built a lot of apps with Xamarin (and others like Intel XDK and it's predecessors); Xamarin has been the best experience for me so far. I don't mind Objective-C, but compared to C#/F# (yep F#! Nice!) it's not very nice for my taste. Xamarin fixes that with 2 very nice languages and a solidly written small layer on the native API.
I have produced apps for iOS and Android with it after having written many native apps for both, so the transition was very easy as you use the same API's. You just reuse a lot of non-UI code.
Note that I don't use visual tools for either platforms; not in Xamarin nor native; all UI is handcoded which, for me, has been proven to be a lot faster indeed. Reuse, refactoring and reasoning with UI code are easy that way while these visual aids don't really do anything beyond "Hello World".
QT Creator is nice but when I tried it 6 months ago it was not ready for prime time mobile wise and it is an abstraction over the gui/api meaning it is farther away from the API/device than you would sometimes want.
Intel XDK to me was a horrible experience, but after making so many HTML5 mobile / hybrid apps, I learned to hate the process. It's not ready; just forget about it for now. Make web stuff (responsive, web apps) in HTML5, make apps in something else.
I would suggest learning native (Java/Objective-C) first, getting some good experience with that in, then moving away from the visual tooling like storyboards etc (It's a matter of taste but > 100 apps later I would never use it again unless it improves a lot somehow... and I don't see that happening) and then maybe use something like Xamarin if you don't like the original native languages or want to reuse a lot of code. A more painful way of reuse which is used in games a lot is to write the common code in C++ and only the UI in the native tech. This is not a nice process at the moment IMHO esp as Android requires you to do that via the NDK and I have had issues with that.