Quantcast
Channel: Recent Threads — Xamarin Community Forums
Viewing all articles
Browse latest Browse all 204402

Getting Started + Question about Tasky

$
0
0

Hi guys!

I've been using Xamarin for various purposes over the last year and I loved it. Built some quick Mac apps with it and began working on an Unity3D game with it as my IDE.

Now I have one new challenge. A year ago I built an iOS app with Titanium and immediately regretted it. It's the worst development experience I had in the last 5 years to be quite honest. It felt like learning PHP3 all over again with its quirks, bugs, hacks and workarounds. So I thought, 100% Objective-C/XCode Native or Xamarin /native/? That's where my love for C# got me.

So here I am, wanting to build a small prototype for my next app but first I'd noticed something: Tasky has 2 different packages. One "paid" and one "starter", we have an Apple license to develop if it's about that. If it's about Xamarin's itself, is it about whether if I'm using the starter or paid version? What's the actual difference? I noticed paid version has more files in it like a SQLite library. What's the difference?

I was also wondering, a year ago I asked about if it was easy to use other Cocoa librairies originally built in Objective-C and someone shown me a blog post that seemed to make it very easy to deal with. Anything changed?

Anything I should know before getting started building an iOS app with Xamarin? I'm currently using the starter version just to build the prototype and justify the cost to our investors (to show them how awesome and fast development will go with Xamarin instead of XCode hehe)

Finally, I know this is kind of a dumb question but what would be one honest /downside/ about using Xamarin over the actual Objective-C/XCode standard solution? Any other suggestions or tips based on my short story? :)

Thanks a lot and have a nice day!


Viewing all articles
Browse latest Browse all 204402

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>