C # iPhone development vs iPhone object development

Which language is best for iPhone app development? Usually objective use of c to develop iPhone applications. But monotouch supports iPhone development using C #.

Before that, I had not used C # and goal c to develop any application. So I'm completely new to both languages. Give me a suggestion for developing iPhone applications ... :)

+4
source share
6 answers

Here is my personal opinion:

I have been in the .NET world for a while. When the iPhone launched the ability to create its own applications, it attracted my attention. I really tried to learn Objective-C. I read 2 books and started trying and trying like a month, and then I quit programming on the iPhone because you had to do many things that on .NET required a single line of code.

When Miguel de Icaza launched MonoTouch, I tried, and I realized that most of my previously made code was fully functional. I have always tried to separate the user interface code from the business code, and this is actually the .NET point on the iPhone. To bring most of your already done business logic to your device.

Also on Objective-C you will not find anything similar to LINQ or the var keyword. The consumption of web services on MonoTouch is just a few clicks away.

If you want to target the Android platform, there is also MonoDroid (monodroid.net). Also, if you want to target Mac OSX, there is MonoMac. So you can share the lib classes between these 3 platforms without much hassle. Not to mention, it will work on Windows and vice versa (when possible).

The only thing you will need to worry about is the interface, but most of your business logic should work.

The following is a complete list of .NET collections supported by MonoTouch: http://monotouch.net/Documentation/Assemblies . In addition, MonoTouch provides C # / CIL binding to all CocoaTouch APIs.

Also, the MonoTouch team support is awesome. You can just go to IRC, ask a question, and they will answer it right away. They also have a mailing list. :)

I really like MonoTouch. I know that no language is perfect for all tasks, and Objective-C is no exception.

+5
source

If you use C # with monotouch, the documentation is much smaller than Objective-C, simply because most iPhone apps are developed using Obj-C, not C #. If you are not familiar with both languages, I would advise Obj-C because of the sheer amount of online tutorials, sample code and documentation from Apple and the community of people. There are also many more books available for buying an iPhone for Obj-C development.

Although you also need to decide if you think that C # may be easier to find out than Obj-C, and if that is enough to go through without a huge number of samples.

At the end of the day, this is just what you prefer.

+4
source

Depending on your needs / needs. Being brand new in this, you can find the jump right in Objective-C the best solution.

However, this question is quite open, there is no real answer to it, try both and see who you like best.

+3
source

If you have never used any languages, I would advise you to use Apples XCode and learn Objective-C, since it is a supported language from Apple. Also, the cost will be lower.

+1
source

Since you have not used C # or Objective-C before, I would recommend going to your native language. In this case, following most iOS developers, it's actually a good idea:

  • Apple's documentation is really good (IMO is better than Android), and you can even use online classes (Google for CS193 - Stanford iPhone Application Development Classes);
  • there are many good books on Objective-C (Kochan classic "Programming in Objective-C" to name one) and on iPhone development (all books that I know use Objective-C);
  • There is a large community in the iOS community that wants to share knowledge (for example, here at StackOverflow), so you begin to learn the curve at the beginning, but you will learn useful things faster than trying to solve some problems with C # my assumption);

Please note: I have never tried the monotouch / C # combination, but I still think that using native with Obj-C is a wiser choice.

+1
source

Go to your native language or don’t worry. Apple supports Objective-C and does not support C #.

-3
source

Source: https://habr.com/ru/post/1338403/


All Articles